Repository navigation
fix(deps): update backstage monorepo - #165
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/backstage-monorepo
branch
2 times, most recently
from
August 25, 2026 21:56
a7596b6 to
b275ae3
Compare
renovate
Bot
force-pushed
the
renovate/backstage-monorepo
branch
2 times, most recently
from
August 29, 2026 10:37
8b29273 to
25efef0
Compare
renovate
Bot
force-pushed
the
renovate/backstage-monorepo
branch
2 times, most recently
from
September 15, 2026 20:15
12f4a82 to
8f3f6cc
Compare
renovate
Bot
force-pushed
the
renovate/backstage-monorepo
branch
2 times, most recently
from
October 1, 2026 13:47
33bfc39 to
04fa634
Compare
renovate
Bot
force-pushed
the
renovate/backstage-monorepo
branch
2 times, most recently
from
October 20, 2026 20:27
3272ab4 to
de1eca0
Compare
renovate
Bot
force-pushed
the
renovate/backstage-monorepo
branch
2 times, most recently
from
October 22, 2026 22:27
7256542 to
dc8366b
Compare
renovate
Bot
force-pushed
the
renovate/backstage-monorepo
branch
from
October 26, 2026 23:11
dc8366b to
53cf378
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.
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
1.9.3→1.11.01.11.5→1.11.81.16.1→1.16.31.9.0→1.10.20.36.4→0.36.70.1.4→0.1.71.3.8→1.3.100.18.12→0.18.151.12.8→1.12.111.3.1→1.3.20.5.4→0.5.7^0.17.3→^0.18.00.5.16→0.5.190.2.5→0.2.8^0.29.2→^0.30.00.2.21→0.2.242.0.7→2.0.100.2.22→0.2.251.1.10→1.2.12.2.3→2.2.63.2.0→3.3.0^0.5.19→^0.6.00.6.7→0.6.100.2.28→0.2.310.7.14→0.7.170.2.21→0.2.240.9.9→0.9.120.11.2→0.11.51.7.6→1.7.90.3.17→0.3.201.4.6→1.4.91.2.24→1.2.261.11.6→1.11.9^0.0.33→^0.0.360.3.17→0.3.200.9.5→0.9.81.7.20→1.7.23^0.17.0→^0.19.0Release Notes
backstage/backstage (@backstage/backend-plugin-api)
v1.11.0Compare Source
Minor Changes
e956084: BREAKING PRODUCERS: Added an instance ID to the root instance metadata service. Custom implementations and mocks must now provide a globally unique ID that remains stable for the lifetime of the running backend instance.f6054ac: Added experimentaldeclareConnectionandconnectionsServiceRefexports to@backstage/backend-plugin-api/alpha. Plugins and modules can declare connection dependencies and request the connections service without importing private packages.Patch Changes
v1.10.1Compare Source
Patch Changes
v1.10.0Compare Source
Minor Changes
74d8cbf: AddedcoreServices.rootSystemMetadata, a new stable public service for reading metadata about the running Backstage system, including a list of installed plugins. Previously only available as an alpha API, it is now part of the standardcoreServicesnamespace.Patch Changes
b1b6c80: Documented the default destructive and read-only action attribute values.backstage/backstage (@backstage/backend-test-utils)
v1.11.8Compare Source
Patch Changes
f6054ac: Test backends now provide the default experimental connections service for plugins and modules that declare connection dependencies.7728fcd: Improved test database cleanup reliability by shutting down independent database engines and removing their logical databases concurrently.e956084: Updated the root instance metadata service mock to provide an instance ID.v1.11.7Compare Source
Patch Changes
05d03ee: Increased the test database cleanup timeout to 60 seconds to reduce timeout failures when using Docker.v1.11.6Compare Source
Patch Changes
b1b6c80: Aligned mocked action attributes so read-only actions default to non-destructive.5ae46fc: AddedmockServices.rootSystemMetadatamock implementation to support the new stablecoreServices.rootSystemMetadataservice in tests.backstage/backstage (@backstage/catalog-client)
v1.16.3Compare Source
Patch Changes
6c74f3f: Fixed the conversion of legacy filters that happens when a request has both afilterand aquery, so that it matches the semantics of the legacy filter query parameter. Empty filters no longer turn into a predicate that matches nothing, empty records no longer match everything, and string values take precedence overCATALOG_FILTER_EXISTSfor the same key.aeb9393: TheInMemoryCatalogClienttest utility now matches entities the same way as the catalog backend. Bothfilterandqueryare evaluated against the same search rows that the backend builds for its search table, instead ofquerybeing evaluated against raw entity JSON. This affectsgetEntities,getEntitiesByRefs,queryEntities,streamEntities, andgetEntityFacets.This fixes several cases where the fake returned different results than a real catalog, which may change the outcome of existing tests:
{ 'relations.hasMember': 'user:default/alice' }now works inquery, including with$in,$hasPrefix,$exists,$contains, and logical operators.filterandquery. For example,{ 'spec.dependsOn': ... }previously never matched infilter, and{ 'METADATA.NAME': ... }never matched inquery.metadata.namespacenow match{ 'metadata.namespace': 'default' }inquery.$exists: true, as in the backend.metadata.name,metadata.namespace, andmetadata.uidalways satisfy$exists: true, even when the entity has no value for them.InputError, even when no entities would be evaluated. For example, an object$containson any field other thanrelations, or arelations$containswithout atype.spec.fooandspec.Foo, now cause anInputErrorwhen matched, since the backend refuses to store such entities.e844921:streamEntitiesno longer asks the catalog backend to compute the total number of matching items, since that count is never part of the streamed result. This also applies to the catalog service in@backstage/plugin-catalog-node, which delegates to the client. ThetotalItemsoption ofStreamEntitiesRequestis now deprecated and ignored.Updated dependencies
v1.16.2Compare Source
Patch Changes
736d84e: Use locale-insensitive Unicode casing for consistent string handling across environments.backstage/backstage (@backstage/catalog-model)
v1.10.2Compare Source
Patch Changes
f487744: Switched to version 4 ofzodfor internal validation. Error messages for invalid catalog model layer operations now use the updatedzodwording.This package no longer pulls in version 3 of
zod. If your own packages usezodwithout declaring it as a dependency, they may now get version 4 instead, so make sure to add it to theirpackage.jsonexplicitly.Updated dependencies
v1.10.1Compare Source
Patch Changes
736d84e: Use locale-insensitive Unicode casing for consistent string handling across environments.61809fe: Allow independently registered catalog model sources to share identical layers, while reporting a clear error for conflicting layers with the same ID.78656f8: Fixed several issues in the alpha catalog model layer system. Schema updates now preserve sibling field validation when changing a property namedtype, support deleting inherited fields and constraints, and retain literal JSON values inconstanddefault. Kind schemas without an explicit root type retain their fields, and invalid combined schemas are rejected during model compilation. Empty kind descriptions and reverse relation titles are now applied correctly.v1.10.0Compare Source
Minor Changes
ad18743: Addedmarketplacespec type to the@alphaAiResource kind, representing a curated registry of plugins for discovery and distribution. Marketplaces reference their contained plugins viaspec.pluginsentity references, generatinghasPartcatalog relations.f501302: Addedpluginspec type to the@alphaAiResource kind, representing a packaged collection of skills distributed as a unit. Plugins reference their contained skills viaspec.skillsentity references, generatinghasPartcatalog relations.0b9b3bf: Added optionalallowedTools,license, andcompatibilityfields to the@alphaAiResource skill spec, aligned with the agentskills.io specification.Patch Changes
9a6955c: Corrected catalog relation generation to honor declared kind combinations, and completed reverse relations for existingAiResourcefields.backstage/backstage (@backstage/cli)
v0.36.7Compare Source
Patch Changes
933e50e: The ESLint configuration for packages with thecommon-libraryrole now reports named imports fromlodash, such asimport { trimEnd } from 'lodash'. Common libraries are published with an ESM build, and these imports cause that build to fail when imported from ESM projects in Node.js. Useimport lodash from 'lodash'instead.36e3f24: Updated the test runner to use the latest Jest 30 releases.v0.36.6Compare Source
Patch Changes
89743dc: Replaced the deprecated dependency used byrepo list-deprecationswith the equivalent TypeScript ESLint rule.v0.36.5Compare Source
Patch Changes
backstage/backstage (@backstage/cli-defaults)
v0.1.7Compare Source
Patch Changes
v0.1.6Compare Source
Patch Changes
de957f6: Added@backstage/cli-module-package-manager-yarnwithbackstage-cli pm verify-patchesto validate Yarn patch references, local patch files,lockfile consistency, and patched Backstage package versions against the
selected Backstage release. The command is included in
@backstage/cli-defaults.v0.1.5Compare Source
Patch Changes
backstage/backstage (@backstage/config)
v1.3.10Compare Source
Patch Changes
e156078: Reading a number from a configuration value that is an empty or whitespace-only string now fails with a clear conversion error, instead of silently returning0. Numeric strings, including ones with surrounding whitespace such as' 42 ', continue to be parsed as expected.v1.3.9Compare Source
Patch Changes
1134d4b: Fixed reading a duration from configuration so that an all-zero ISO 8601 duration (such asPT0S) now yields a consistent zero value instead of an empty result.backstage/backstage (@backstage/core-components)
v0.18.15Compare Source
Patch Changes
e415488: Stop clearing the selected provider fromlocalStoragewhen a sign-in loader is cancelled. Only clear it when the loader actually fails. MemoizegetSignInProvidersso it does not recreate the providers object on every render.76ac6ed: Updated dependencyjs-yamlto^5.0.0.e859c29: AddeddefaultCloseDelayMsoption toSubmenuOptionsto configure a delay before a submenu closes.v0.18.14Compare Source
Patch Changes
b80a9f3: Added anonCopyLogprop to theLogViewercomponent that renders a copy button in the toolbar, allowing users to copy all log content to the clipboard.736d84e: Use locale-insensitive Unicode casing for consistent string handling across environments.a15bac8: Added an optionalvariantprop toCopyTextButtonto allow configuring its visual style (primary,secondary, ortertiary).c0ebaa7: chore(deps): bumpjs-yamlfrom 4.3.1 to 4.3.2bfb6497: FixedCopyTextButtonshowing its tooltip on hover/focus instead of only after the user clicks to copy the text.279fdf6: Declared the DOM Testing Library dependency required by React Testing Library.f2b5407: Updated dependencyreact-idle-timerto5.7.3.d9a949e: Added support for rendering custom link elements insideHeaderIconLinkRow.v0.18.13Compare Source
Patch Changes
226817d: chore(deps): bumpjs-yamlfrom 4.2.0 to 4.3.0a4759e6: Migrated tests from MSW v1 to MSW v2.96cd953: Fixed theDependencyGraphcomponent to avoid a jarring initial render where nodes briefly pile up at overlapping positions before animating into place. The graph content is now hidden until node measurements are complete and the layout has fully settled, then revealed at the correct positions with transitions suppressed for the first frame.Also fixed a
containerRefrecreation chain where every graph dimension change caused the container measurement callback to be recreated and re-triggered, producing unnecessary re-renders during initial layout.Updated dependencies
backstage/backstage (@backstage/core-plugin-api)
v1.12.11Compare Source
Patch Changes
v1.12.10Compare Source
Patch Changes
v1.12.9Compare Source
Patch Changes
9fcfbc9: Fixed a performance issue where all components using analytics, including every link, would rerender unnecessarily whenever a surrounding analytics context rendered again without its attributes having changed, for example when a URL query parameter changed on an entity page.backstage/backstage (@backstage/errors)
v1.3.2Compare Source
Patch Changes
603898f: FixedserializeErrorso that stack traces are stripped from all nested error causes when stacks are not requested, not just the first-level cause.backstage/backstage (@backstage/frontend-defaults)
v0.5.7Compare Source
Patch Changes
v0.5.6Compare Source
Patch Changes
v0.5.5Compare Source
Patch Changes
backstage/backstage (@backstage/frontend-plugin-api)
v0.18.2Compare Source
Patch Changes
a650c4f: AddedAppLifecycleApiandappLifecycleApiRef, which let you check whether the app has been finalized and subscribe to changes in its lifecycle.a650c4f: TheuseRouteRefhook now resolves the route again once the app has been finalized, so that elements rendered before finalization, such asapp/root.elementsextensions, can link to pages instead of gettingundefined.v0.18.1Compare Source
Patch Changes
024c0ef: Updated internal type imports to avoid circular declaration chunks in package builds.bd6cf43: Fixed a bug where overriding a plugin extension withwithOverridesmoved the overridden extension to the end of the plugin's extension list. This caused overridden extensions to lose their original position, for example making an overridden sub page tab move to the end of the tabs on its page. Overridden extensions now keep their original order, while extensions that don't override an existing one are appended at the end.v0.18.0Compare Source
Minor Changes
907793c: BREAKING: Removed the deprecatedconfig.schemaoption for extensions and extension blueprints. Use the top-levelconfigSchemaoption with Standard Schema-compatible schema values, such as Zod v4.Patch Changes
e156f1e](https://redirect.githuConfiguration
📅 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 was generated by Mend Renovate. View the repository job log.