[dependabot]

Bumps @backstage/plugin-catalog-backend from 1.26.0 to 3.9.2.

Release notes

Sourced from @​backstage/plugin-catalog-backend's releases.

v1.57.0-next.1

See docs/releases/v1.57.0-next.1-changelog.md for more information.

v1.57.0-next.0

See docs/releases/v1.57.0-next.0-changelog.md for more information.

v1.56.3

Hey, I just made a Pull Request!

This release adds the experimental Zensical engine for TechDocs, giving adopters a migration path ahead of Material for MkDocs shutting down on November 5th. It includes the new @backstage/plugin-techdocs-backend-module-zensical module, Zensical support in @techdocs/cli, and new alpha building blocks in @backstage/plugin-techdocs-node. Patches #36159.

✔️ Checklist

• A changeset describing the change and affected packages. (more info)
• Added or updated documentation
• Tests for new functionality and regression tests for bug fixes
• Screenshots attached (for UI changes)
• All your commits have a Signed-off-by line in the message. (more info)

🤖 Generated with Claude Code

v1.56.2

This patch release fixes the following issues:

• Made the @yarnpkg/* dependencies of @​backstage/cli-module-package-manager-yarn optional peers, to work around @​yarnpkg/core@​4.9.2 breaking installation

v1.56.1

This patch release contains the following commits:

• fix(catalog): match URL locations in catalog rules in canonical form
• fix: improve placeholder repository validation

v1.56.0

These are the release notes for the v1.56.0 release of Backstage.

A huge thanks to the whole team of maintainers and contributors as well as the amazing Backstage Community for the hard work in getting this release developed and done.

Highlights

BREAKING: Filter predicates must be objects at the root

The FilterPredicate type, its zod schemas, and parseFilterPredicate in @backstage/filter-predicates now only accept objects at the root of a predicate. Primitive values such as "component" or true were previously accepted at the root, but no API that accepts filter predicates could match them in a meaningful way. Primitive values are still allowed as values to match against properties, and as the operand of $contains to match arrays of primitive values, for example { "metadata.tags": { "$contains": "java" } }.

A new AnyFilterPredicate type describes predicates that may also be primitive values at the root, equivalent to the previous FilterPredicate type. The catalog backend now rejects entity and location queries with a primitive root value with an "Invalid query" error.

BREAKING: Removed the Atlassian usernameMatchingUserEntityName sign-in resolver

The usernameMatchingUserEntityName sign-in resolver has been removed from @backstage/plugin-auth-backend-module-atlassian-provider, along with the atlassianSignInResolvers export that only contained it. Atlassian user profiles do not contain a username, so the resolver could never work. Use the emailMatchingUserEntityProfileEmail or emailLocalPartMatchingUserEntityName resolvers instead.

BREAKING PRODUCERS: Backend instance IDs

... (truncated)

Changelog

Sourced from @​backstage/plugin-catalog-backend's changelog.

@​backstage/plugin-catalog-backend

4.0.3-next.1

Patch Changes

• 9c76a81: Documented that the entities/by-query endpoint currently applies only the first orderField; any additional order fields are ignored. Updated the OpenAPI spec parameter description and the Software Catalog API docs accordingly. No behavior change. Refs #17560.
• 3b97016: Improved the performance of entity facets and total item counts on PostgreSQL when the filter contains $any or $not conditions, such as those produced by conditional permission policies for catalog entity reads.
• 3b97016: Entity filter predicates that combine $all, $any or $not with other keys in the same object, or that give $all or $any a non-array value, are now rejected with a 400 error. Previously the extra keys were silently ignored.
• f7ce914: Fixed an issue where /validate-entity would not return after sending a 400 response on invalid entity validation, causing an unhandled ERR_HTTP_HEADERS_SENT error and triggering duplicate success/fail audit events.
• Updated dependencies
  • @​backstage/catalog-client@​1.16.4-next.0
  • @​backstage/plugin-events-node@​0.5.0-next.1
  • @​backstage/plugin-catalog-node@​2.2.7-next.1

4.0.3-next.0

Patch Changes

• 7d765b6: Improved repository validation for catalog entity placeholders. Placeholder-driven reads, including $openapi and $asyncapi document references, are now restricted to the entity's own repository on SCM hosts; cross-repository references are rejected.

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

• Updated dependencies

  • @​backstage/plugin-permission-node@​0.11.6-next.0
  • @​backstage/backend-plugin-api@​1.11.1-next.0
  • @​backstage/plugin-catalog-node@​2.2.7-next.0
  • @​backstage/plugin-events-node@​0.4.28-next.0
  • @​backstage/backend-openapi-utils@​0.7.4-next.0

4.0.2

Patch Changes

• Bumped version to account for a patch release.

4.0.1

Patch Changes

• 589dcef: Fixed an issue where successfully processed entities could remain unavailable if stitch scheduling was interrupted.

• a08e746: Improved large entity provider mutations by yielding to the event loop while preparing database changes.

• aa6e7c6: Reduce repeated work for entities that fail stitching by gradually increasing retry delays with jitter. Failed entities remain eligible for recovery, and new stitching requests reset their failure count.

• d7cc6e5: Reject non-positive stitching polling intervals and lease durations at startup to prevent continuous polling and immediate lease expiry. Configuration errors identify the setting that needs correction.

• 727d53f: Improve responsiveness to other requests while reading large sets of entities with field selection, without reducing page sizes.

  Like full-entity responses, projected list responses may now be streamed without a Content-Length or automatically generated ETag header.

• 11f608b: Entity and location queries with a primitive value at the root of the filter predicate are now rejected with an "Invalid query" error, rather than "Query must be an object".

... (truncated)

Commits

• See full diff in compare view

[github-actions]

I'm not approving this PR because it includes a major update of a dependency used in production

[github-actions]

I'm not approving this PR because it includes a major update of a dependency used in production