Skip to content

fix(deps): update backstage monorepo - #165

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/backstage-monorepo
Open

fix(deps): update backstage monorepo#165
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/backstage-monorepo

Conversation

@renovate

@renovaterenovateBot commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

PackageChangeAgeConfidence
@backstage/backend-defaults (source)0.17.6 → 0.17.7ageconfidence
@backstage/backend-plugin-api (source)1.9.3 → 1.10.0ageconfidence
@backstage/backend-test-utils (source)1.11.5 → 1.11.6ageconfidence
@backstage/catalog-model (source)1.9.0 → 1.10.0ageconfidence
@backstage/cli (source)0.36.4 → 0.36.5ageconfidence
@backstage/cli-defaults (source)0.1.4 → 0.1.5ageconfidence
@backstage/core-components (source)0.18.12 → 0.18.13ageconfidence
@backstage/core-plugin-api (source)1.12.8 → 1.12.9ageconfidence
@backstage/frontend-defaults (source)0.5.4 → 0.5.5ageconfidence
@backstage/frontend-plugin-api (source)^0.17.3 → ^0.18.0ageconfidence
@backstage/plugin-app-backend (source)0.5.16 → 0.5.17ageconfidence
@backstage/plugin-app-react (source)0.2.5 → 0.2.6ageconfidence
@backstage/plugin-auth-backend (source)^0.29.2 → ^0.30.0ageconfidence
@backstage/plugin-auth-backend-module-guest-provider (source)0.2.21 → 0.2.22ageconfidence
@backstage/plugin-auth-node (source)0.7.3 → 0.7.4ageconfidence
@backstage/plugin-catalog (source)2.0.7 → 2.0.8ageconfidence
@backstage/plugin-catalog-backend (source)3.8.1 → 3.9.0ageconfidence
@backstage/plugin-catalog-backend-module-scaffolder-entity-model (source)0.2.22 → 0.2.23ageconfidence
@backstage/plugin-catalog-node (source)2.2.3 → 2.2.4ageconfidence
@backstage/plugin-catalog-react (source)3.2.0 → 3.2.1ageconfidence
@backstage/plugin-notifications (source)0.5.19 → 0.5.20ageconfidence
@backstage/plugin-notifications-backend (source)0.6.7 → 0.6.8ageconfidence
@backstage/plugin-notifications-node (source)0.2.28 → 0.2.29ageconfidence
@backstage/plugin-permission-backend (source)0.7.14 → 0.7.15ageconfidence
@backstage/plugin-permission-backend-module-allow-all-policy (source)0.2.21 → 0.2.22ageconfidence
@backstage/plugin-permission-common (source)0.9.9 → 0.9.10ageconfidence
@backstage/plugin-permission-node (source)0.11.2 → 0.11.3ageconfidence
@backstage/plugin-search (source)1.7.6 → 1.7.7ageconfidence
@backstage/plugin-search-backend (source)2.1.4 → 2.1.5ageconfidence
@backstage/plugin-search-backend-module-catalog (source)0.3.17 → 0.3.18ageconfidence
@backstage/plugin-search-backend-node (source)1.4.6 → 1.4.7ageconfidence
@backstage/plugin-search-react (source)1.11.6 → 1.11.7ageconfidence
@backstage/plugin-signals (source)^0.0.33 → ^0.0.34ageconfidence
@backstage/plugin-signals-backend (source)0.3.17 → 0.3.18ageconfidence
@backstage/plugin-user-settings (source)0.9.5 → 0.9.6ageconfidence
@backstage/test-utils (source)1.7.20 → 1.7.21ageconfidence
@backstage/ui (source)0.17.0 → 0.17.1ageconfidence

Release Notes

backstage/backstage (@​backstage/backend-defaults)

v0.17.7

Compare Source

Patch Changes
backstage/backstage (@​backstage/backend-plugin-api)

v1.10.0

Compare Source

Minor Changes
  • 74d8cbf: Added coreServices.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 standard coreServices namespace.
Patch Changes
backstage/backstage (@​backstage/backend-test-utils)

v1.11.6

Compare Source

Patch Changes
backstage/backstage (@​backstage/catalog-model)

v1.10.0

Compare Source

Minor Changes
  • ad18743: Added marketplace spec type to the @alpha AiResource kind, representing a curated registry of plugins for discovery and distribution. Marketplaces reference their contained plugins via spec.plugins entity references, generating hasPart catalog relations.
  • f501302: Added plugin spec type to the @alpha AiResource kind, representing a packaged collection of skills distributed as a unit. Plugins reference their contained skills via spec.skills entity references, generating hasPart catalog relations.
  • 0b9b3bf: Added optional allowedTools, license, and compatibility fields to the @alpha AiResource 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 existing AiResource fields.
backstage/backstage (@​backstage/cli)

v0.36.5

Compare Source

Patch Changes
backstage/backstage (@​backstage/cli-defaults)

v0.1.5

Compare Source

Patch Changes
backstage/backstage (@​backstage/core-components)

v0.18.13

Compare Source

Patch Changes

  • 226817d: chore(deps): bump js-yaml from 4.2.0 to 4.3.0

  • a4759e6: Migrated tests from MSW v1 to MSW v2.

  • 96cd953: Fixed the DependencyGraph component 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 containerRef recreation 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.9

Compare 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.
  • Updated dependencies
backstage/backstage (@​backstage/frontend-defaults)

v0.5.5

Compare Source

Patch Changes
backstage/backstage (@​backstage/frontend-plugin-api)

v0.18.0

Compare Source

Minor Changes
  • 907793c: BREAKING: Removed the deprecated config.schema option for extensions and extension blueprints. Use the top-level configSchema option with Standard Schema-compatible schema values, such as Zod v4.
Patch Changes
  • e156f1e: Added support for using a SubRouteRef as the parent of another SubRouteRef. Child paths are combined with ancestor paths at creation, and nested sub-routes inherit parameters from their complete ancestor chain.
backstage/backstage (@​backstage/plugin-app-backend)

v0.5.17

Compare Source

Patch Changes
backstage/backstage (@​backstage/plugin-app-react)

v0.2.6

Compare Source

Patch Changes
backstage/backstage (@​backstage/plugin-auth-backend)

v0.30.0

Compare Source

Minor Changes

  • 274acc5: BREAKING: The OAuth redirect URI and client ID metadata document allowlists now match patterns against each URL component separately instead of against the full URL string. Wildcards no longer match across the host and path boundary, patterns must include an explicit protocol and are otherwise rejected as invalid configuration instead of being silently ignored, and redirect URIs that contain embedded credentials are always rejected.

    A wildcard port also no longer implicitly matches every path: a pattern such as http://localhost:* now only matches the root path. Use http://localhost:*/* to allow any port and any path. The built-in loopback defaults have been updated accordingly, so this only affects explicitly configured patterns.

Patch Changes
  • 4e884d2: Skip SSRF protection for CIMD metadata fetches when the client_id matches an exact (non-wildcard) entry in allowedClientIdPatterns. Exact patterns mean the administrator explicitly listed a specific URL, so the DNS resolution is trusted. Wildcard patterns still enforce the SSRF check to protect against attacker-controlled subdomains resolving to internal addresses.
  • a995892: Allow ChatGPT Codex clients to use Client ID Metadata Documents by default.
  • 827989d: Fixed the built-in CLI client being rejected when allowedClientIdPatterns is configured for Client ID Metadata Documents.
  • Updated dependencies
backstage/backstage (@​backstage/plugin-auth-backend-module-guest-provider)

v0.2.22

Compare Source

Patch Changes
backstage/backstage (@​backstage/plugin-auth-node)

v0.7.4

Compare Source

Patch Changes
backstage/backstage (@​backstage/plugin-catalog)

v2.0.8

Compare Source

Patch Changes
backstage/backstage (@​backstage/plugin-catalog-backend)

v3.9.0

Compare Source

Minor Changes
  • c7c0ec3: Added a refresh-catalog-entity action so agents and MCP clients can re-queue a single entity for processing after creating or updating it — useful for reading back fresh data immediately after a scaffolder run without waiting for the next scheduled processing loop.
Patch Changes
  • aa318d0: Migrated internal query filter handling from EntityFilter to FilterPredicate, simplifying the filter parsing and query application pipeline.
  • 10f0713: Replaced the delete-all and reinsert pattern for the relations table with a diff-based sync that only touches rows that actually changed. In steady state (the common case), zero writes occur, eliminating write churn, dead tuples, and WAL traffic from the processing path. Stitching is now also skipped for relation neighbors that did not change.
  • ee40136: Fixed a missing promise return in a database migration rollback function.
  • eb6dff2: Fixed an issue where PostgreSQL deadlock errors during entity provider mutations were silently swallowed, causing entities to be dropped until the next full refresh. Transactions are now automatically retried on deadlock with exponential back-off.
  • dd562f0: Fixed a potential MySQL deadlock during concurrent entity processing by retrying the updateProcessedEntity transaction on deadlock errors.
  • b031a48: Fixed an issue where SCM location.moved events would generate new locations in the database for files that were not actively tracked.
  • b7650ad: Simplified internal router setup by removing unnecessary conditional guards around route registrations.
  • Updated dependencies
backstage/backstage (@​backstage/plugin-catalog-backend-module-scaffolder-entity-model)

v0.2.23

Compare Source

Patch Changes
backstage/backstage (@​backstage/plugin-catalog-node)

v2.2.4

Compare Source

Patch Changes
backstage/backstage (@​backstage/plugin-catalog-react)

v3.2.1

Compare Source

Patch Changes

  • 9fcfbc9: Fixed a performance issue where all components reading the entity context on an entity page would rerender unnecessarily whenever the page rendered again without the entity data having changed, for example when a URL query parameter changed. This was particularly noticeable when switching tabs in the entity inspector dialog, which caused the entire underlying page to rerender.

  • e766061: Fixed an issue where the "Owned" count in UserListPicker would display the total number of catalog entities instead of 0 when the logged-in user has no ownership entity refs. The empty relations.ownedBy filter was being silently dropped by the catalog client, causing the backend to return all entities with no ownership filter applied.

    This was a regression introduced in #​22131, which removed an explicit ownershipEntityRefs?.length === 0 guard that had been present since #​20339.

  • ed462ad: Fixed EntityOwnerPicker in owners-only mode to display human-readable entity titles (from metadata.title or spec.profile.displayName) instead of opaque internal names, both in the dropdown list and in the selected owner chips. The owner list is now virtualized, keeping the picker responsive for catalogs with large numbers of owner entities.

  • Updated dependencies

backstage/backstage (@​backstage/plugin-notifications)

v0.5.20

Compare Source

Patch Changes
backstage/backstage (@​backstage/plugin-notifications-backend)

v0.6.8

Compare Source

Patch Changes
backstage/backstage (@​backstage/plugin-notifications-node)

v0.2.29

Compare Source

Patch Changes
backstage/backstage (@​backstage/plugin-permission-backend)

v0.7.15

Compare Source

Patch Changes
backstage/backstage (@​backstage/plugin-permission-backend-module-allow-all-policy)

v0.2.22

Compare Source

Patch Changes
backstage/backstage (@​backstage/plugin-permission-common)

v0.9.10

Compare Source

Patch Changes
  • b754e32: Migrated tests from MSW v1 to MSW v2.
backstage/backstage (@​backstage/plugin-permission-node)

v0.11.3

Compare Source

Patch Changes
backstage/backstage (@​backstage/plugin-search)

v1.7.7

Compare Source

Patch Changes
backstage/backstage (@​backstage/plugin-search-backend)

v2.1.5

Compare Source

Patch Changes

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 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.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate

renovateBot commented Aug 18, 2026

Copy link
Copy Markdown
ContributorAuthor

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: yarn.lock
➤ YN0000: · Yarn 4.18.0
➤ YN0000: ┌ Resolution step
➤ YN0016: │ @backstage/frontend-plugin-api@npm:^0.18.0: All versions satisfying "^0.18.0" are quarantined
➤ YN0000: └ Completed in 0s 977ms
➤ YN0000: · Failed with errors in 0s 995ms

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants