fix(deps): update dependencies (non-major) - autoclosed #12
No reviewers
Labels
No labels
automerge
bug
dependencies
duplicate
help wanted
invalid
lang
rust
migrations
opencode
question
security
type
documentation
type
enhancement
type
maintenance
type
refactor
vulnerability
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Personal/backstage!12
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/dependencies-(non-major)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
^0.18.1→^0.19.00.36.7→0.36.80.1.7→0.1.81.3.10→1.3.110.18.15→0.18.161.12.11→1.13.00.5.7→0.5.81.2.23→1.3.00.14.6→0.14.90.5.19→0.5.200.1.3→0.1.4^0.2.8→^0.3.00.2.9→0.2.100.1.13→0.1.14^0.30.2→^0.31.00.5.8→0.5.90.2.24→0.2.250.7.7→0.7.82.0.10→2.1.04.0.2→4.0.50.1.17→0.1.180.1.27→0.1.280.2.25→0.2.260.6.9→0.6.100.13.19→0.13.200.9.11→0.9.120.1.43→0.1.440.12.24→0.12.250.21.12→0.21.150.2.3→0.2.40.6.1→0.6.20.6.10→0.6.110.8.0→0.8.10.7.17→0.7.180.2.24→0.2.250.9.12→0.9.130.11.5→0.11.60.6.19→0.6.201.40.0→1.41.04.2.3→4.3.00.10.1→0.10.40.1.27→0.1.281.7.9→1.8.02.1.8→2.1.90.3.20→0.3.210.5.60→0.5.610.4.19→0.4.201.4.9→1.4.10^0.0.36→^0.0.370.3.20→0.3.211.19.0→1.20.02.4.2→2.4.31.1.41→1.2.00.9.8→0.9.90.4.8→0.4.9^0.19.0→^0.20.014.6.7→14.6.13Release Notes
backstage/backstage (@backstage/backend-defaults)
v0.19.0Compare Source
Minor Changes
250e4c3: Add support for the new WebSocket routing APIs.Existing server upgrade listeners can coexist during migration and receive unmatched upgrades. Multiple listeners produce a warning; migrate custom upgrade handling to the router API to avoid handling the same socket twice. Installing a plugin that registers a WebSocket route, such as signals, activates the server-level upgrade listener. Upgrades handled only through Express, such as the Kubernetes proxy, must migrate to this API; otherwise, unmatched upgrades receive 404 responses when this is the only server-level listener.
3beb656: BREAKING: Request logs from the root HTTP router no longer include adatefield, and no longer repeat the date at the start of the message. JSON logs, used whenNODE_ENVisproduction, now include atimestampfield on every log line instead. Update any log pipelines or dashboards that readdateor parse the date out of the message to usetimestamp.If you override the root logger with a custom JSON format, use
format.combine(format.timestamp(), format.json())to keep thetimestampfield.Patch Changes
f81ca4e: The AWS S3 URL reader no longer assumes the configuredroleArna second time when the matching account underaws.accountsalready provides credentials for that exact role, for example through a web identity token file. Previously the role had to trust itself for this setup to work. The role is still assumed explicitly when the integration sets anexternalId.392710f: The Azure DevOps URL reader now warns at startup when a personal access token is configured for Azure DevOps Services. Global personal access tokens stop working on January 27, 2027, and organization-scoped tokens are now deprecated in favor of Microsoft Entra ID credentials. Errors from rejected credentials are also clearer.80cc892: Removed the runtime dependency on@backstage/cli-node, which was only used for types. Backends no longer install the CLI tooling packages through@backstage/backend-defaults.5eb2381: Updated a documentation link forDefaultRootHttpRouterto point to thecoreServices.rootHttpRouterservice reference.1892d2f: chore(deps): bumpminimatchfrom 10.2.6 to 11.0.1fbd2535: Fixed a connection and memory leak in the GitHub URL reader, where every failed request with a large error response body, such as the error pages served during a GitHub Enterprise outage, left its connection open indefinitely.da22423: Ensures that the limited user cookie issued for a request always represents the user authenticated on that request. A previously issued cookie belonging to a different user is now replaced during the cookie refresh, instead of being reused.918ca98: Updated dependencyjoseto^6.1.0. Existing ES256 token issuance and verification are unchanged. ML-DSA algorithms can be used when the runtime supports them.9fc68ae: Fixed thevalkeycache store sharing keys between plugins. Two plugins that cached a value under the same key could read and overwrite each other's entries. Keys are now stored under the plugin namespace, the same way theredisstore does it. Cache entries now use new key names, so existing entries are no longer read and are rebuilt as plugins write new values. Old entries stay in Valkey until their TTL expires. Entries without a TTL, and the per-plugin key index sets that the old layout created, stay until you remove them manually.backstage/backstage (@backstage/cli)
v0.36.8Compare Source
Patch Changes
04a54e2: Switched the compilation target to ES2024, which all supported Node.js versions fully support. Package builds, app bundles, and the backend development server now compile code for ES2024, and the TypeScripttargetandliboptions in@backstage/cli/config/tsconfig.jsonare set toES2024. This requires TypeScript 5.9 or later, which is now the oldest supported version according to the versioning policy.The
libchange allows code to use ES2024 built-in APIs such asObject.groupByandPromise.withResolvers. Backstage doesn't include polyfills, so frontend code that uses these APIs needs at least Chrome or Edge 119, Firefox 121, or Safari 17.4.9120c46: Updated dependencyglobto^14.0.0.Updated dependencies
backstage/backstage (@backstage/cli-defaults)
v0.1.8Compare Source
Patch Changes
backstage/backstage (@backstage/config)
v1.3.11Compare Source
Patch Changes
backstage/backstage (@backstage/core-components)
v0.18.16Compare Source
Patch Changes
1c75912: Deprecated components with Backstage UI replacements or compositions:Avatar,Link,LinkButton,Select,Content,BottomLink,HeaderActionMenu,HeaderLabel,HeaderTabs,ItemCardGrid,ItemCardHeader,TabbedCard,CardTab,SubvalueCell,CreateButton,ContentHeader,FavoriteToggle,FavoriteToggleIcon,HeaderIconLinkRow,IconLinkVertical, andOverflowTooltip, along with their associated public types.Use the replacements from
@backstage/uidescribed in each component's deprecation notice. These migrations require adapting props and composition, including external-link presentation, selection callbacks, document titles, and error boundaries where applicable. Existing exports and runtime behavior are unchanged.cac9654:MarkdownContentnow loadsreact-markdownand itsremarkandrehypeplugins the first time it renders, instead of with the app. This keeps them out of the app's startup bundle. Markdown appears once the renderer has loaded, so tests that look for rendered markdown right after a synchronousrendermay need to usefindBy*queries instead.7890ec2: Deprecated legacy page shells (Page,PageWithHeader,Header), routed tabs (TabbedLayout,TabbedLayout.Route,RoutedTabs),AlertDisplay,AppIcon, the named icon wrappers, and their associated public types for new frontend development. Existing exports and behavior remain available, including in migrated plugins.Use page and sub-page extensions and
PageLayoutfrom@backstage/frontend-plugin-apifor framework-managed pages, or compose@backstage/uiheaders and tabs with explicit routing for standalone layouts. Legacy themes, arbitrary header content, document titles, and focus behavior need deliberate migration. Rely on the new frontend app's existing alert/toast display. For app-customizable icons, useuseApi(coreApis.icons).icon(key)from@backstage/frontend-plugin-apiand render the returned element, handling missing icons as needed.Updated dependencies
backstage/backstage (@backstage/core-plugin-api)
v1.13.0Compare Source
Minor Changes
558c076: Exported the alphaTranslationRefTupletype for messages selected by calling a translation ref. Refs are now callable functions; treat them as opaque values.BREAKING PRODUCERS: Translation snapshots require
teven whenreadyis false. Custom translation APIs must provide a translator using available messages and language fallbacks.Patch Changes
ca02018: API reference IDs now use plugin ID validation for each dot-separated component.This accepts numeric dash groups and mixed case, including IDs such as
plugin.example-2.todos.6540a44: Preserved the legacyuseApihook's direct-value behavior when the frontendsystem's hook unwraps promise-valued APIs. The legacy hook continues returning
promises unchanged.
e55a4a8: Updated compatibility with theFrontendPlugininterface after removal of its deprecatedidproperty, retaining support for older plugin instances.315f7bc: Made the legacy icon component andwithApiscompatibility APIs independent of@backstage/frontend-plugin-apiso that they remain available to legacy frontend apps.Deprecated
withApis. Wrap class components in a function component that usesuseApiinstead.e3d50c4: UpdateduseAppto support the new icons API. ItsgetSystemIconandgetSystemIconsmethods continue to return icon components.Updated dependencies
backstage/backstage (@backstage/frontend-defaults)
v0.5.8Compare Source
Patch Changes
d514e4d: Updated app options to use theExtensionFactoryMiddlewaretype from@backstage/frontend-app-apiinstead of the deprecated export from@backstage/frontend-plugin-api. Middleware behavior is unchanged.f747f16: Removed the outdated warning that the frontend system is in alpha. This package remains on 0.x.4bbc7a9: Removed explicit support for React 17: the peer dependency range forreact,react-domand@types/reactis now^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.2aa14e3: Apps now release their browser history listener when the React root is removed or a hot refresh replaces the app within the existing root. See the 1.57 migration notes for background on app-owned history.backstage/backstage (@backstage/integration-react)
v1.3.0Compare Source
Minor Changes
4bbc7a9: Removed explicit support for React 17: the peer dependency range forreact,react-domand@types/reactis now^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.Patch Changes
4c662c9: Removed this package's direct Material UI v4 dependencies. SCM integrations without a registered system icon now use a Remix code icon as the fallback.backstage/backstage (@backstage/plugin-api-docs)
v0.14.9Compare Source
v0.14.8Compare Source
v0.14.7Compare Source
Patch Changes
a44c5eb: The AsyncAPI definition widget no longer resolves external references by default. References to whole external documents still render, with a placeholder naming the document that was not loaded; references that point into an external document (using a#fragment) fail to render with an error naming the reference. To resolve external references — for example to reach internal schema registries that require authentication — provide theresolversprop to enable external reference resolution.4bbc7a9: Removed explicit support for React 17: the peer dependency range forreact,react-domand@types/reactis now^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.backstage/backstage (@backstage/plugin-app-backend)
v0.5.20Compare Source
Patch Changes
11f4455: Documented that if your package manager doesn't hoist workspace packages, for example pnpm withhoistWorkspacePackages: false, you need to add the app package to thedependenciesof the rootpackage.json.6a0de59: Backend plugins now locate their database migrations relative to their own package directory, without requiring the package to be resolvable by name.2fea3e2: Reduced startup database traffic and memory usage when checking for previously cached static assets.backstage/backstage (@backstage/plugin-app-module-user-settings)
v0.1.4Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-app-react)
v0.3.0Compare Source
Minor Changes
f9f794b: BREAKING: Icon bundles created withIconBundleBlueprintnow accept only icon elements. Replace component values such asicons: { user: MyIcon }withicons: { user: <MyIcon /> }. For Material UI icons, use<MyIcon fontSize="inherit" />. Icons supplied throughconvertLegacyAppOptionscontinue to accept components and are converted automatically.5c29a89: BREAKING: Removed the deprecated flatitemsprop from custom navigation components. Use thenavItemscollection instead.Use
navItems.rest()instead of iterating overitems. Replaceitem.towithitem.hrefanditem.textwithitem.title. Theitem.iconvalue is a React element, so render it directly instead of using it as a component type.df2bcee: BREAKING: RemovedRouterBlueprint; remove overrides that only installBrowserRouter, move global providers toAppRootWrapperBlueprint, and render routing adapters inside lazily loaded page components. For custom navigation, provideAppHistoryApithrough anApiBlueprintfactory forcoreApis.appHistorythat is available during initialization without anifpredicate. See the 1.57 migration notes for detailed migration steps.Patch Changes
77c1622: Added theAnalyticsImplementationtype, moved from@backstage/frontend-plugin-api, alongsideAnalyticsImplementationBlueprintandAnalyticsImplementationFactory.4bbc7a9: Removed explicit support for React 17: the peer dependency range forreact,react-domand@types/reactis now^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.backstage/backstage (@backstage/plugin-app-visualizer)
v0.2.10Compare Source
Patch Changes
4bbc7a9: Removed explicit support for React 17: the peer dependency range forreact,react-domand@types/reactis now^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.backstage/backstage (@backstage/plugin-auth)
v0.1.14Compare Source
Patch Changes
4bbc7a9: Removed explicit support for React 17: the peer dependency range forreact,react-domand@types/reactis now^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.backstage/backstage (@backstage/plugin-auth-backend)
v0.31.0Compare Source
Minor Changes
352ad44: BREAKING: The deprecated experimental Dynamic Client Registration (DCR) support has been removed. Use Client ID Metadata Documents (CIMD) instead and removeauth.experimentalDynamicClientRegistrationfrom your configuration. The database migration deletes registered clients and their authorization and offline sessions, invalidating existing DCR authorization codes and refresh tokens. Users must sign in again through a CIMD client. Already-issued user tokens remain valid until they expire. See the migration guide.9e22c4b: Added support for pre-registered OAuth clients through the newauth.staticClientsconfiguration. This allows integrations that support neither Client ID Metadata Documents nor Dynamic Client Registration to act on behalf of signed-in users using a fixed client ID, an optional client secret, and exact redirect URIs. All clients must use PKCE. Clients with a secret must also authenticate at the token endpoint.The token endpoint verifies client credentials for both authorization code and refresh token grants. Missing or incorrect credentials for confidential clients return
invalid_clientwith HTTP 401. Public clients can identify themselves using HTTP Basic with an empty secret. Codes issued to a different client are rejected.Removing a configured client rejects its outstanding authorization codes and refresh tokens. HTTP Basic authentication supports form-encoded client IDs and secrets.
PKCE now requires the
S256challenge method for all clients, including existing CIMD clients. Theplainmethod is no longer accepted or advertised. Update clients that useplainto generate SHA-256 challenges.Patch Changes
5fc15b7: Fixed authorization-code exchanges to reject supplied client IDs that do not match the client that obtained the code. These requests returninvalid_grantwithout consuming the code. Exchanges that omitclient_idremain supported for older clients but now log a deprecation warning; a future release will require it.97ee785: Allow Cursor clients to use Client ID Metadata Documents by default.8965c27: User tokens issued by sign-in resolvers now always have the entity refs in theirsubandentclaims in canonical form, for exampleuser:default/jane.doerather thanUser:default/Jane.Doe, and duplicateentrefs are removed. Previously, a custom sign-in resolver could issue valid but non-canonical refs, which then failed to match stored user info and offline sessions on case-sensitive databases.1892d2f: chore(deps): bumpminimatchfrom 10.2.6 to 11.0.16a0de59: Backend plugins now locate their database migrations relative to their own package directory, without requiring the package to be resolvable by name.7db7c52: Respect theauth.backstageTokenExpirationconfiguration when issuing OAuth access and ID tokens from the OIDC service, instead of hard-coding a 1-hour expiry.fa0eb7a: Added aPOST /v1/offline-sessions/revokeendpoint that lets other backend services revoke all offline sessions (refresh tokens) of a user. The endpoint only accepts service credentials, records an audit event, and is only available whenauth.experimentalRefreshToken.enabledis set.918ca98: Updated dependencyjoseto^6.1.0. Existing ES256 token issuance and verification are unchanged. ML-DSA algorithms can be used when the runtime supports them.backstage/backstage (@backstage/plugin-auth-backend-module-github-provider)
v0.5.9Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-auth-backend-module-guest-provider)
v0.2.25Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-auth-node)
v0.7.8Compare Source
Patch Changes
918ca98: Updated dependencyjoseto^6.1.0. Existing ES256 token issuance and verification are unchanged. ML-DSA algorithms can be used when the runtime supports them.backstage/backstage (@backstage/plugin-catalog)
v2.1.0Compare Source
Minor Changes
d4f458e: Added support for translated entity content titles throughEntityContentBlueprint.4bbc7a9: Removed explicit support for React 17: the peer dependency range forreact,react-domand@types/reactis now^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.Patch Changes
0da6298: Entity page tabs now generate app-absolute links from the entity route, so they work correctly when navigation comes from outside the page router.57111dc: Migrated theEntityNotFoundcomponent from Material UI to Backstage UI.9d0a31b: Removed an unuseduse-sync-external-storedependency, which is no longer needed now that React 18 is the minimum supported version.118d84a: Updated catalog tabs to render icon elements through the current frontend icon API.backstage/backstage (@backstage/plugin-catalog-backend)
v4.0.5Compare Source
v4.0.4Compare Source
v4.0.3Compare Source
Patch Changes
9c76a81: Documented that theentities/by-queryendpoint currently applies only the firstorderField; any additional order fields are ignored. Updated the OpenAPI spec parameter description and the Software Catalog API docs accordingly. No behavior change. Refs #17560.7d765b6: Improved repository validation for catalog entity placeholders. Placeholder-driven reads, including$openapiand$asyncapidocument references, are now restricted to the entity's own repository on SCM hosts; cross-repository references are rejected.2c223ee: Fixed aItem of type "refresh" was emitted after processing had completedwarning that could appear when one of several placeholders in an entity failed to resolve. Processing now waits for all placeholders to finish before reporting the first failure.c4b7cb1: Theentities/by-refsendpoint now resolves entity references case-insensitively, matchingentities/by-nameand the documented entity reference contract where receivers treat refs case-insensitively. Previously, a ref whose casing differed from the stored lowercased ref returnednull. Fixes #36743.3b97016: Improved the performance of entity facets and total item counts on PostgreSQL when the filter contains$anyor$notconditions, such as those produced by conditional permission policies for catalog entity reads.3b97016: Entity filter predicates that combine$all,$anyor$notwith other keys in the same object, or that give$allor$anya non-array value, are now rejected with a 400 error. Previously the extra keys were silently ignored.cd5fa5f: Improved the performance of entity queries on PostgreSQL when a filter matches a field against a long list of values, such as the ownership claims used by conditional permission policies for catalog entity reads.eb5875d: Improved repository validation for catalog entity placeholders on Azure DevOps. Placeholder-driven reads on a configured Azure DevOps integration are now restricted to the entity's own repository on every Azure DevOps host shape, including legacy{org}.visualstudio.comhosts and Azure DevOps Server hosts, and targets that cannot be attributed to a repository are rejected as well.32e6642: Adds internal publication bookkeeping as groundwork for future catalog change tracking. Existing catalog APIs and deletion behavior are unchanged.The PostgreSQL upgrade builds an index concurrently without rewriting existing entities, but still scans the catalog table. Large installations may need to prepare this index out of band before upgrading; see Upgrading large installations.
2a9f08b: Match URL locations in catalog rules in canonical form.URL locations are now matched against catalog rules in a canonical form of the URL, so that rule decisions agree with how the location target is resolved when its content is fetched. URL patterns that relied on percent-encoded characters being matched as written, or on default ports being kept, no longer match and should be updated.
1892d2f: chore(deps): bumpminimatchfrom 10.2.6 to 11.0.1f7ce914: Fixed an issue where/validate-entitywould not return after sending a 400 response on invalid entity validation, causing an unhandledERR_HTTP_HEADERS_SENTerror and triggering duplicate success/fail audit events.6a0de59: Backend plugins now locate their database migrations relative to their own package directory, without requiring the package to be resolvable by name.9120c46: Updated dependencyglobto^14.0.0.20746bc: Location annotations on entities submitted to the validate-entity endpoint can no longer override the location of the request.Updated dependencies
backstage/backstage (@backstage/plugin-catalog-backend-module-gitea)
v0.1.18Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-catalog-backend-module-logs)
v0.1.28Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-catalog-backend-module-scaffolder-entity-model)
v0.2.26Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-catalog-graph)
v0.6.10Compare Source
Patch Changes
4bbc7a9: Removed explicit support for React 17: the peer dependency range forreact,react-domand@types/reactis now^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.backstage/backstage (@backstage/plugin-catalog-import)
v0.13.20Compare Source
Patch Changes
63d6533: The pull request preview card in the import flow now uses Backstage UI components.4bbc7a9: Removed explicit support for React 17: the peer dependency range forreact,react-domand@types/reactis now^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.backstage/backstage (@backstage/plugin-home)
v0.9.12Compare Source
Patch Changes
0f93c60: The World Clock home page widget now uses Backstage UI components and styles instead of Material UI.4bbc7a9: Removed explicit support for React 17: the peer dependency range forreact,react-domand@types/reactis now^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.backstage/backstage (@backstage/plugin-home-react)
v0.1.44Compare Source
Patch Changes
4bbc7a9: Removed explicit support for React 17: the peer dependency range forreact,react-domand@types/reactis now^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.backstage/backstage (@backstage/plugin-kubernetes)
v0.12.25Compare Source
Patch Changes
4bbc7a9: Removed explicit support for React 17: the peer dependency range forreact,react-domand@types/reactis now^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.backstage/backstage (@backstage/plugin-kubernetes-backend)
v0.21.15Compare Source
v0.21.14Compare Source
v0.21.13Compare Source
Patch Changes
68abde4: Allow AWS Kubernetes clusters to select credentials from a configured AWS account without assuming another role. Setkubernetes.io/aws-account-idin the cluster's auth metadata to use that account's credentials directly, including credentials obtained through web identity federation.0915584: Kubernetes proxy: stop forwarding the caller'sAuthorizationandCookieheaders to the target cluster. Upstream requests now carry only credentials from the configured auth strategy or theBackstage-Kubernetes-Authorizationheader.backstage/backstage (@backstage/plugin-mcp-actions-backend)
v0.2.4Compare Source
Patch Changes
1892d2f: chore(deps): bumpminimatchfrom 10.2.6 to 11.0.19e22c4b: OAuth discovery metadata is now also served when pre-registered clients are configured withauth.staticClients.backstage/backstage (@backstage/plugin-notifications)
v0.6.2Compare Source
Patch Changes
4bbc7a9: Removed explicit support for React 17: the peer dependency range forreact,react-domand@types/reactis now^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.555d6ff: Updated custom notification icons to use the element-based icons API. Missing icons still fall back to the notification severity icon.backstage/backstage (@backstage/plugin-notifications-backend)
v0.6.11Compare Source
Patch Changes
c0ea056: Fixed broadcast notifications losing their saved status when marked as read or unread, and losing their read status when saved or unsaved.6a0de59: Backend plugins now locate their database migrations relative to their own package directory, without requiring the package to be resolvable by name.backstage/backstage (@backstage/plugin-org)
v0.8.1Compare Source
Patch Changes
4bbc7a9: Removed explicit support for React 17: the peer dependency range forreact,react-domand@types/reactis now^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.backstage/backstage (@backstage/plugin-permission-backend)
v0.7.18Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-permission-backend-module-allow-all-policy)
v0.2.25Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-permission-common)
v0.9.13Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-permission-node)
v0.11.6Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-proxy-backend)
v0.6.20Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-scaffolder)
v1.41.0Compare Source
Minor Changes
3fe82f6: Added aScaffolderTemplateFilterBlueprintthat lets apps filter the new frontend system's template list using identity, catalog, or other viewer-specific state.ae86338: Added GitLab branch autocompletion to RepoBranchPicker using user SCM credentials.4bbc7a9: Removed explicit support for React 17: the peer dependency range forreact,react-domand@types/reactis now^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.Patch Changes
111c6ce: Keep the task button bar at the user's chosen visibility when a task completes, so log visibility and start-over controls remain accessible. Action availability continues to depend on task state and permissions.backstage/backstage (@backstage/plugin-scaffolder-backend)
v4.3.0Compare Source
Minor Changes
ff0ef74: Added support forwhenconditions on parameter steps. Steps whose condition evaluates to false are skipped during validation, and their values are removed before the task runs. Also updated Nunjitsu to 0.7.0, with no change to existing templating behavior.Patch Changes
6a0de59: Backend plugins now locate their database migrations relative to their own package directory, without requiring the package to be resolvable by name.2fac95b: Group the Software Templates API documentation by functionality instead of placing all endpoints under "Untagged".eda8ede: Check the host that relative fetch URLs resolve to when user credentials are required.When
scaffolder.requireScmUserCredentialsis enabled, the fetch actions now apply the user-credential requirement to the host that the fetch URL resolves to, rather than the host of the template location. This makes the requirement effective also for fetch URLs that are not parseable as absolute URLs on their own.e318672: Fixed matching of action input values in scaffolder permission policies, including identifiers that are provided either as numbers or as strings.be5074c: Preserve public task log values when rendering without secrets omits an earlier object field, while continuing to redact secret-derived keys and values.62eaba9: Fixed custom task permission rules registered by backend modules being ignored when authorizing task access and filtering task lists.Updated dependencies
v4.2.5Compare Source
v4.2.4Compare Source
backstage/backstage (@backstage/plugin-scaffolder-backend-module-github)
v0.10.4Compare Source
v0.10.3Compare Source
v0.10.2Compare Source
Patch Changes
1368ad3: Added agithub:repo:rulesets:createaction that creates a ruleset in a GitHub repository. Rules and bypass actors are written in the same format as the GitHub REST API, so any rule type that GitHub supports can be used in templates.6c43d4f: Validates thetargetPathinput of thegitlab:repo:push,publish:gitlab:merge-requestandpublish:github:pull-requestscaffolder actions, and thefilesToDeleteentries ofpublish:github:pull-request. The values must be relative paths within the target repository; absolute paths and paths containing..segments are now rejected, so changes are only applied inside the intended subdirectory of the repository.backstage/backstage (@backstage/plugin-scaffolder-backend-module-notifications)
v0.1.28Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-search)
v1.8.0Compare Source
Minor Changes
4bbc7a9: Removed explicit support for React 17: the peer dependency range forreact,react-domand@types/reactis now^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.Patch Changes
backstage/backstage (@backstage/plugin-search-backend)
v2.1.9Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-search-backend-module-catalog)
v0.3.21Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-search-backend-module-pg)
v0.5.61Compare Source
Patch Changes
6a0de59: Backend plugins now locate their database migrations relative to their own package directory, without requiring the package to be resolvable by name.39cda0c: Avoid recomputing full-text searchtsvectordata for unchanged documents during indexing.backstage/backstage (@backstage/plugin-search-backend-module-techdocs)
v0.4.20Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-search-backend-node)
v1.4.10Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-signals)
v0.0.37Compare Source
Patch Changes
4bbc7a9: Removed explicit support for React 17: the peer dependency range forreact,react-domand@types/reactis now^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.backstage/backstage (@backstage/plugin-signals-backend)
v0.3.21Compare Source
Patch Changes
bcb1697: Register WebSocket upgrades through the framework router so the first connection works without a prior HTTP request. Preserve user-only authentication and existing token-as-protocol clients, while keeping only the health endpoint public over HTTP.backstage/backstage (@backstage/plugin-techdocs)
v1.20.0Compare Source
Minor Changes
4bbc7a9: Removed explicit support for React 17: the peer dependency range forreact,react-domand@types/reactis now^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.Patch Changes
9a1d5cf: Fixed the TechDocs table of contents drifting to the right on wide screens. It now stays aligned with the right edge of the documentation content.backstage/backstage (@backstage/plugin-techdocs-backend)
v2.4.3Compare Source
Patch Changes
4d7a3fe: Clarified in the config schema whichtechdocs.generator.mkdocssettings also apply to the Zensical engine:legacyCopyReadmeMdToIndexMd,dangerouslyAllowAdditionalKeysanddangerouslyAllowAdditionalPlugins.bc73976: Restrictsmarkdown_extensionsinmkdocs.ymlto known extension names before documentation generation, in both the MkDocs and Zensical engines. Extension names outside the permitted set are removed from the configuration with a warning. Allow additional extensions, for example from a custom build image, with the newtechdocs.generator.mkdocs.dangerouslyAllowAdditionalExtensionsconfiguration, or the--dangerouslyAllowAdditionalExtensionsflag when using the TechDocs CLI.backstage/backstage (@backstage/plugin-techdocs-module-addons-contrib)
v1.2.0Compare Source
Minor Changes
4bbc7a9: Removed explicit support for React 17: the peer dependency range forreact,react-domand@types/reactis now^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.Patch Changes
backstage/backstage (@backstage/plugin-user-settings)
v0.9.9Compare Source
Patch Changes
4bbc7a9: Removed explicit support for React 17: the peer dependency range forreact,react-domand@types/reactis now^18.0.0. React 17 is no longer tested or guaranteed to work, although it may continue to work in some cases. See the migration guide.backstage/backstage (@backstage/plugin-user-settings-backend)
v0.4.9Compare Source
Patch Changes
6a0de59: Backend plugins now locate their database migrations relative to their own package directory, without requiring the package to be resolvable by name.backstage/backstage (@backstage/ui)
v0.20.0Compare Source
Minor Changes
f4d8adf: BREAKING: Backstage UI now uses explicit routing integration and React Aria's native link behavior: standalone apps that relied on automatic React Router integration must supplyBUIProviderwith auseNavigationhook, React Router is no longer a peer dependency, androuterOptionsnow supports only the router-neutralreplaceandstatefields. BREAKING: Link targets usingjavascript:,data:, orvbscript:become inertabout:blanklinks with a console warning. See the 1.57 migration notes for detailed migration steps and the BUI routing migration guide for integration requirements.Affected components: BUIProvider, ButtonLink, Card, Combobox, Header, Link, List, Menu, PluginHeader, SearchAutocomplete, Select, Table, Tabs, TagGroup
Patch Changes
9d0a31b: Removed an unuseduse-sync-external-storedependency, which is no longer needed now that React 18 is the minimum supported version.9120c46: Updated dependencyglobto^14.0.0.724657a:Headertabs no longer make the page scroll horizontally when they do not fit. The tabs now stay in a single row that scrolls on its own, with a visible scrollbar. When more tabs are hidden on a side, that edge of the row fades out. The fade is removed while a tab has keyboard focus. The row scrolls to show the active tab when the page loads and whenever the active tab changes. With a mouse or other precise pointer, a scroll button also appears on each side that has hidden tabs. Small touch screens show only the fade. The buttons respect the reduced motion setting. Screen readers do not announce them, because every tab is still reachable with the keyboard.Affected components: Header
065d1e3: FixeduseTablein complete mode showing an empty page labelled "NaN - NaN of N" whenpaginationOptionsswitched fromtype: 'none'to paged pagination after mount.Affected components:
useTableUpdated dependencies
testing-library/user-event (@testing-library/user-event)
v14.6.13Compare Source
Bug Fixes
v14.6.12Compare Source
Bug Fixes
v14.6.11Compare Source
Bug Fixes
v14.6.10Compare Source
Bug Fixes
v14.6.9Compare Source
Bug Fixes
v14.6.8Compare Source
Bug Fixes
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate CLI.
e8d2e034ccae2dadc8fbae2dadc8fbfa31b1946bfa31b1946b183a60d7aa183a60d7aa9bf701decd9bf701decd6e701cd95b6e701cd95be87503bf70e87503bf70fe62715141fe62715141b3a8848b97b3a8848b97ea4f5cbb83ea4f5cbb83e6e5533a42e6e5533a42to45934bad4745934bad47f227aa9c34fix(deps): update dependencies (non-major)to chore(deps): update dependency @testing-library/user-event to v14.6.12I'll review the attached diff. First, let me read the rest of it since it was truncated.
The diff is large; let me finish reading it and check the actual workspace state for context.
{
"summary": "# Review Summary\n\nThis diff is not the small
@testing-library/user-eventpatch bump the PR title/description advertise. The package.json changes and the bulk ofyarn.lockimplement a broad Backstage platform refresh: direct bumps of@backstage/plugin-app-react→ ^0.3.0,@backstage/plugin-signals→ ^0.0.37,@backstage/ui→ ^0.20.0 (app) and@backstage/backend-defaults→ ^0.19.0,@backstage/plugin-auth-backend→ ^0.31.0 (backend), plus dozens of transitive Backstage updates including several major jumps (@backstage/frontend-plugin-api→ 1.0.0,@backstage/plugin-catalog-react→ 4.0.0,@backstage/plugin-scaffolder-node→ 1.0.0,@backstage/plugin-catalog-node→ 3.0.0,jose5.x → 6.x). React peer ranges tighten from^17 || ^18to^18only across many packages — consistent with this app's React 18.3.1, but worth noting.\n\nFindings:\n\n1. PR scope/title mismatch (needs attention): The description claims only@testing-library/user-event14.6.7 → 14.6.12. The attached diff changes Backstage deps in both package.json files and resolves user-event only to 14.6.10 (not 14.6.12), so the 14.6.11/14.6.12 fixes are not delivered. A prior review characterized this diff as user-event-only; that no longer matches the current diff, which is primarily a Backstage upgrade. Retitle/redescribe the PR (or split scopes) before merge.\n\n2. Security-sensitive major:jose5.10.0 → 6.2.17 lands in@backstage/plugin-auth-backend/plugin-auth-node. Major JWT-library bumps should be validated against auth flows, not just merged via lockfile churn.\n\n3. Bundle/perf: The lockfile now carries two React Aria stacks (react-aria-components1.17.0 withreact-aria3.48.0 /react-stately3.46.0 alongside the existing 1.22.0 / 3.53.1 / 3.51.0), because@backstage/plugin-appandcore-app-apipin~1.17.0while@backstage/uiuses~1.22.0. Expect larger client bundles and possible UI behavior drift between plugins.\n\n4. Positives: No application source changes; lockfile checksums/ranges appear internally consistent; workspace entries correctly reflect the package.json bumps.\n\nRecommendation: Fix the PR title/description to match the actual Backstage refresh (or split the user-event bump out), reconcile user-event to 14.6.12 if that is still intended, then runyarn tsc,yarn build:backend,yarn test, and e2e (yarn test:e2e) given the frontend-plugin-api 1.0 and auth-related majors. Verify auth login/logout paths after the jose major.","verdict": "changes",
"comments": [
{
"file": "packages/app/package.json",
"line": 25,
"side": "new",
"severity": "bug",
"message": "PR title/description claim a @testing-library/user-event 14.6.7→14.6.12 bump only, but this PR changes Backstage dependencies here (plugin-app-react ^0.3.0, plugin-signals ^0.0.37, @backstage/ui ^0.20.0) and in packages/backend (backend-defaults ^0.19.0, plugin-auth-backend ^0.31.0), with a large yarn.lock refresh. Please retitle/redescribe the PR to match the actual scope (or split the user-event change into its own PR) so reviewers and release notes are not misleading."
},
{
"file": "yarn.lock",
"line": 11271,
"side": "new",
"severity": "bug",
"message": "@testing-library/user-event resolves to 14.6.10 in this lockfile, but the PR description targets 14.6.12. The 14.6.11 (shadow DOM) and 14.6.12 (tel maxlength) fixes are therefore not delivered. If the user-event bump is still intended, regenerate the lockfile so it lands on 14.6.12; otherwise drop it from the PR description."
},
{
"file": "yarn.lock",
"line": 21064,
"side": "new",
"severity": "security",
"message": "jose major bump 5.10.0 → 6.2.17 is pulled in by @backstage/plugin-auth-backend and @backstage/plugin-auth-node (JWT/JWKS handling). Major version changes in auth crypto libraries warrant explicit validation: run auth-related tests and manually verify login/logout and token refresh paths before merge."
},
{
"file": "yarn.lock",
"line": 26038,
"side": "new",
"severity": "performance",
"message": "Lockfile now contains duplicate React Aria stacks: react-aria-components 1.17.0 (with react-aria 3.48.0 / react-stately 3.46.0) alongside the existing ~1.22.0 / 3.53.1 / 3.51.0 set, because @backstage/plugin-app and core-app-api pin ~1.17.0 while @backstage/ui uses ~1.22.0. This increases client bundle size and risks inconsistent component behavior across plugins; consider whether an upstream alignment is available."
}
]
}
*🤖 Review by opencode (opencode/mimo-v2.6-flash-free) — verdict: comment
Code review findings from opencode.
f227aa9c34b37518944fchore(deps): update dependency @testing-library/user-event to v14.6.12to fix(deps): update dependencies (non-major)b37518944f56f84f719f56f84f719fcc4b420b58cc4b420b5886c2de4715fix(deps): update dependencies (non-major)to fix(deps): update dependencies (non-major) - autoclosedPull request closed