fix(deps): update backstage core#1091
Open
secustors-renovate[bot] wants to merge 1 commit into
Open
Conversation
9363c64 to
f2b226c
Compare
f2b226c to
aa2ca60
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.17.0→0.17.10.36.1→0.36.20.36.1→0.36.20.1.1→0.1.21.3.7→1.3.80.5.10→0.5.110.18.9→0.18.101.12.5→1.12.60.5.1→0.5.2^0.16.0→^0.17.00.5.2→0.6.01.2.17→1.2.180.5.13→0.5.140.2.2→0.2.30.2.3→0.2.4^0.28.0→^0.29.00.5.2→0.5.30.2.18→0.2.190.7.0→0.7.12.0.4→2.0.53.6.1→3.7.00.1.21→0.1.220.2.19→0.2.20^2.0.0→^3.0.00.21.3→0.21.40.5.16→0.5.170.6.4→0.6.50.7.3→0.7.40.7.11→0.7.120.2.18→0.2.190.9.8→0.9.9^0.10.7→^0.11.01.36.2→1.37.01.7.3→1.7.42.1.1→2.1.20.3.14→0.3.150.5.54→0.5.551.4.3→1.4.4^0.0.30→^0.0.310.3.14→0.3.150.9.2→0.9.3^0.14.0→^0.15.01.50.4→1.51.0Release Notes
backstage/backstage (@backstage/backend-defaults)
v0.17.1Compare Source
Patch Changes
90b572e: Adds an alphaTracingServiceto provide a unified interface for emitting trace spans across Backstage plugins.97d3bd4: Fixed a race condition inCachedUserInfoServicewhere a failed request could incorrectly evict a newer cache entry for the same token. The error handler now verifies the map entry is still the same promise before deleting it.3595c97: ExporteddefaultServiceFactoriesto allow use withcreateSpecializedBackendfor advanced configuration likeextensionPointFactoryMiddleware.89d3248: Fixed schedulersleepfiring immediately for durations longer than ~24.8 days, caused by Node.jssetTimeoutoverflowing its 32-bit millisecond limit.d00a44b: Fixed Valkey cluster mode to useiovalkey'sClusterclass instead ofcreateClusterfrom@keyv/redis. The previous implementation passed a@redis/clientRedisClusterinstance to@keyv/valkey, which expects aniovalkeyClusterinstance. This caused the cluster client to not berecognized correctly, as the two libraries have incompatible object models.
2f0519c: Added a newCachedUserInfoServicedecorator that wrapsDefaultUserInfoServicewith a 5-second TTL cache and in-flight request coalescing. The decorator is wired in viauserInfoServiceFactoryusing a shared root-level cache. RepeatedgetUserInfo()calls for the same user token within the TTL window return the cached result without making an HTTP call to the auth backend. Note that customUserInfoServiceimplementations registered via their own factory will not benefit from this cache automatically.744fa1f: Removed duplicated entries that appeared in bothdependenciesanddevDependencies.e9b78e9: Removed theuuiddependency and replaced usage with the built-incrypto.randomUUID().6209065: Addedcontextandpropagationto the alphaTracingService. Plugins can bridge OpenTelemetry context across async boundaries viatracing.propagation.extract(tracing.context.active(), carrier)followed bytracing.context.with(ctx, fn), and read propagated baggage viatracing.propagation.getActiveBaggage()ortracing.propagation.getBaggage(ctx).backstage/backstage (@backstage/cli)
v0.36.2Compare Source
Patch Changes
744fa1f: Removed duplicated entries that appeared in bothdependenciesanddevDependencies.backstage/backstage (@backstage/cli-defaults)
v0.1.2Compare Source
Patch Changes
backstage/backstage (@backstage/config)
v1.3.8Compare Source
Patch Changes
backstage/backstage (@backstage/core-compat-api)
v0.5.11Compare Source
Patch Changes
744fa1f: Removed duplicated entries that appeared in bothdependenciesanddevDependencies.backstage/backstage (@backstage/core-components)
v0.18.10Compare Source
Patch Changes
3846774: Added missing dependencies that were previously only available transitively.021b368: Added stable DOM markers to the legacy Page and Header so adjacent layout components can coordinate spacing without relying on generated class names.0c5e41f: Removed unused dependencies that had no imports in source code.backstage/backstage (@backstage/core-plugin-api)
v1.12.6Compare Source
Patch Changes
ab1cdbb: Removed a handful of internal imports that referenced the package by its own name. Value imports were switched to relative paths, and type-only imports toimport type. These self-referential imports could trigger circular initialization errors in bundled ESM and when the package was loaded viajest.requireActual— most visiblyCannot access '_AppRootElementBlueprintesm' before initializationfrom@backstage/frontend-plugin-api. There are no user-facing API changes.backstage/backstage (@backstage/frontend-defaults)
v0.5.2Compare Source
Patch Changes
482cc59: Invalid feature flag declarations are now treated as warnings rather than errors, letting the app load normally.backstage/backstage (@backstage/frontend-plugin-api)
v0.17.0Compare Source
Minor Changes
44d77e9: BREAKING: Removed the deprecatedNavItemBlueprint. Navigation items are now discovered fromPageBlueprintextensions based on theirtitleandiconparams.If you were still using
NavItemBlueprint, migrate by movingtitleandiconto yourPageBlueprintinstead:PageBlueprintexpects anIconElementrather than a Material UIIconComponent, so this is also a good time to switch to Remix Icon if you were using Material UI icons only for the nav item:8738203: BREAKING: Removed the deprecated property form ofPortableSchema.schema. Theschemamember is now a plain method that must be called asschema()— direct property access likeschema.typeorschema.propertiesis no longer supported.Patch Changes
ab1cdbb: Removed a handful of internal imports that referenced the package by its own name. Value imports were switched to relative paths, and type-only imports toimport type. These self-referential imports could trigger circular initialization errors in bundled ESM and when the package was loaded viajest.requireActual— most visiblyCannot access '_AppRootElementBlueprintesm' before initializationfrom@backstage/frontend-plugin-api. There are no user-facing API changes.cad156e: Replaced old config schema values from existing extensions and blueprints.72a552f: Updated error messages and deprecation warnings to clarify that thezod/v4subpath export from the Zod v3 package is not supported byconfigSchema, since it does not include JSON Schema conversion. Thezoddependency has been bumped to^4.0.0.backstage/backstage (@backstage/frontend-test-utils)
v0.6.0Compare Source
Minor Changes
44d77e9: BREAKING:renderInTestAppno longer renders a sidebar or legacynav-itemextensions. The app nav extension is now disabled in the minimal test app shell, along with the layout and routes extensions.If your tests passed
featurescontainingnav-itemextensions and asserted on links or labels in that stub sidebar, switch torenderTestAppinstead — it uses the real app shell and discovers nav items from page extensions.If you only use
renderInTestAppto mount a component with APIs or route refs, there is no change.Patch Changes
0c298f7: Removed internalmockWithApiFactoryhelper in favor of usingattachMockApiFactorydirectly.fa363f9: Added support forExternalRouteRefin themountedRoutesoption ofrenderInTestAppandrenderTestApp.9279ea8: Added explicit type annotations to.map()callback parameters inrenderInTestAppto avoid implicitanyerrors with newer TypeScript versions.backstage/backstage (@backstage/integration-react)
v1.2.18Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-app-backend)
v0.5.14Compare Source
Patch Changes
744fa1f: Removed duplicated entries that appeared in bothdependenciesanddevDependencies.0c5e41f: Removed unused dependencies that had no imports in source code.backstage/backstage (@backstage/plugin-app-react)
v0.2.3Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-app-visualizer)
v0.2.4Compare Source
Patch Changes
e2d9831: Tightened React Aria dependency version ranges from^to~to prevent unintended minor version upgrades.f635139: Limited@remixicon/reactdependency to versions below 4.9.0 due to a license change in that release.44d77e9: Removed separate nav item extensions. Sidebar entries are now provided viatitleandiconon each plugin's page extension.backstage/backstage (@backstage/plugin-auth-backend)
v0.29.0Compare Source
Minor Changes
29d398b: BREAKING: Hardened the default allowed patterns for CIMD and DCR to replace the previous permissive['*']wildcards with specific defaults for known MCP clients. If you previously relied on the default['*']patterns, you will need to explicitly configure the patterns you need in yourapp-config.yaml.CIMD (
experimentalClientIdMetadataDocuments):allowedClientIdPatternsnow defaults to Claude, VS Code, and the built-in Backstage CLI instead of['*']allowedRedirectUriPatternsnow defaults to loopback addresses (localhost, 127.0.0.1, [::1]) instead of['*']DCR (
experimentalDynamicClientRegistration):allowedRedirectUriPatternsnow defaults to Cursor and loopback addresses instead of['*']If you need to allow additional clients or redirect URIs, you can override these defaults in your
app-config.yaml:Patch Changes
9f269d7: Limit the size of fetched client ID metadata documents to prevent oversized responses from being accepted.3f5e7ec: Improved OIDC error messages to include the rejected redirect URI or client ID, making it easier to debug client registration failures.e9b78e9: Removed theuuiddependency and replaced usage with the built-incrypto.randomUUID().27f24a9: Refresh token usage now verifies that the user's catalog entity still exists before issuing a new access token. If the user has been removed from the catalog, the refresh is rejected and the session is revoked. Transient catalog errors reject the refresh but preserve the session for retry. This check can be disabled by settingauth.experimentalRefreshToken.dangerouslyDisableCatalogPresenceChecktotrue.4f62755: Improved the OAuth consent dialog for MCP authorization by showing more client details, including the client metadata host for CIMD clients, the metadata URL, callback URL, and requested scopes.backstage/backstage (@backstage/plugin-auth-backend-module-github-provider)
v0.5.3Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-auth-backend-module-guest-provider)
v0.2.19Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-auth-node)
v0.7.1Compare Source
Patch Changes
744fa1f: Removed duplicated entries that appeared in bothdependenciesanddevDependencies.e9b78e9: Removed theuuiddependency and replaced usage with the built-incrypto.randomUUID().backstage/backstage (@backstage/plugin-catalog)
v2.0.5Compare Source
Patch Changes
728629c: Fixed an issue where navigating to an unknown sub-path on an entity page (for example/catalog/default/component/foo/blob) would silently render the first available route. Unknown paths now show the standard not-found page instead.44d77e9: Removed separate nav item extensions. Sidebar entries are now provided viatitleandiconon each plugin's page extension.0c5e41f: Removed unused dependencies that had no imports in source code.cad156e: Replaced old config schema values from existing extensions and blueprints.085133f: Thezoddependency has been bumped from^3.25.76 || ^4.0.0to^4.0.0, sinceconfigSchemarequires the full Zod v4 package for JSON Schema support.backstage/backstage (@backstage/plugin-catalog-backend)
v3.7.0Compare Source
Minor Changes
c2de113: BREAKING: When paginating entities with an order field via/entities/by-query, entities that lack the order field are now excluded from both the result set and thetotalItemscount. Previously these entities appeared at the end of the sorted result viaNULLS LAST, but cursor-based pagination could not actually reach them past the first page — the count over-reported the number of navigable entities. The new behavior aligns the count with what is actually returned.This also removes the
DISTINCTdeduplication from the sort-field CTE, which is a prerequisite for the planner toConfiguration
📅 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.