Bump the npm_and_yarn group across 1 directory with 2 updates

[dependabot]

Bumps the npm_and_yarn group with 2 updates in the /packages/backend directory: @backstage/plugin-auth-backend and @backstage/plugin-scaffolder-backend.

Updates @backstage/plugin-auth-backend from 0.24.5 to 0.29.0

Changelog

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

0.29.0

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 your app-config.yaml.

  CIMD (experimentalClientIdMetadataDocuments):

  • allowedClientIdPatterns now defaults to Claude, VS Code, and the built-in Backstage CLI instead of ['*']
  • allowedRedirectUriPatterns now defaults to loopback addresses (localhost, 127.0.0.1, [::1]) instead of ['*']

  DCR (experimentalDynamicClientRegistration):

  • allowedRedirectUriPatterns now 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:

  auth:
    experimentalClientIdMetadataDocuments:
      enabled: true
      allowedClientIdPatterns:
        - 'https://claude.ai/*'
        - 'https://vscode.dev/*'
        - 'https://my-custom-client.example.com/*'
      allowedRedirectUriPatterns:
        - 'http://localhost:*'
        - 'http://127.0.0.1:*'
        - 'https://my-app.example.com/callback'
    experimentalDynamicClientRegistration:
      enabled: true
      allowedRedirectUriPatterns:
        - 'cursor://*'
        - 'http://localhost:*'
        - 'http://127.0.0.1:*'
        - 'myapp://*'

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 the uuid dependency and replaced usage with the built-in crypto.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 setting auth.experimentalRefreshToken.dangerouslyDisableCatalogPresenceCheck to true.
• 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.
• Updated dependencies
  • @​backstage/catalog-model@​1.9.0
  • @​backstage/errors@​1.3.1
  • @​backstage/backend-plugin-api@​1.9.1
  • @​backstage/plugin-catalog-node@​2.2.1

... (truncated)

Commits

• See full diff in compare view

Updates @backstage/plugin-scaffolder-backend from 1.33.0 to 4.0.0

Release notes

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

v1.51.0

These are the release notes for the v1.51.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: Removed deprecated NavItemBlueprint

The deprecated NavItemBlueprint has been removed from @backstage/frontend-plugin-api. Navigation items are now discovered from PageBlueprint extensions based on their title and icon params. If you were still using NavItemBlueprint, migrate by setting title and icon on the page extension instead. All built-in plugins have been updated accordingly.

Additionally, renderInTestApp from @backstage/frontend-test-utils no longer renders a sidebar or legacy nav-item extensions. The app nav extension is now disabled in the minimal test app shell.

BREAKING: Removed deprecated PortableSchema.schema property form

The deprecated property form of PortableSchema.schema has been removed from @backstage/frontend-plugin-api. The schema member is now a plain method that must be called as schema() — direct property access like schema.type or schema.properties is no longer supported.

BREAKING: Hardened OIDC default patterns

The default allowed patterns for CIMD and DCR in @backstage/plugin-auth-backend have been hardened. The previous permissive ['*'] wildcards have been replaced with specific defaults for known MCP clients. If you previously relied on the permissive defaults and have custom MCP clients, you will need to explicitly add their patterns to the allow list.

BREAKING: Cleaned up PolicyQueryUser type

The token and expiresInSeconds fields have been removed from PolicyQueryUser in @backstage/plugin-permission-node. These were previously deprecated in favor of credentials with coreServices.auth. The identity field has been deprecated. A new CachedUserInfoService with a 5-second TTL cache and in-flight request coalescing has been added to reduce repeated user info lookups.

BREAKING: Catalog entity pagination excludes entities without sort field

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 the totalItems count. Previously these entities appeared at the end via NULLS LAST, but cursor-based pagination could not actually reach them past the first page — the count over-reported the number of navigable entities.

BREAKING: Microsoft Graph disabled users filtered by default

The @backstage/plugin-catalog-backend-module-msgraph and @backstage/plugin-catalog-backend-module-msgraph-incremental providers now filter out disabled user accounts by default. The provider automatically applies an accountEnabled eq true filter, combining it with any custom user.filter you provide. If you need to ingest disabled accounts, set the filter to explicitly include them.

Contributed by @​mtlewis in #34165

BREAKING: Backstage UI updates

There are several new additions in Backstage UI:

New components: A Combobox component pairs a text input with a filterable dropdown, supporting sectioned options, icons, sizes, and custom typed values. New DatePicker and DateRangePicker components provide accessible date selection with calendar popovers built on React Aria. Flex item props (grow, shrink, basis) have been added to Box, Card, Grid, and Flex.

Header improvements: A sticky prop has been added to the Header component that keeps the title-and-actions bar fixed at the top of its scroll container. New description, tags, and metadata props provide richer header content. The breadcrumbs prop has been deprecated.

Other additions: Grouped options in Select, isPending prop replacing loading across components, searchDebounceMs and filterDebounceMs options for useTable, PasswordField visual alignment with TextField, a public --bui-bg-inherit CSS variable, and keyboard focus indicators on Card links.

Breaking changes:

• Header: Removed the main header class from the Header component. Custom styles targeting this class should be updated.
• @remixicon/react dependency limited to versions below 4.9.0 due to a license change.

... (truncated)

Changelog

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

4.0.0

Minor Changes

• 77bee9f: Updated the list-scaffolder-tasks action to support the new "status" filter parameter, allowing the action to return tasks matching a specific status.
• 07e08be: Added always() and failure() status check functions for scaffolder steps. These functions can be used in the if field of a step to control execution after failures. always() ensures a step runs regardless of previous step outcomes, while failure() runs a step only when a previous step has failed.
• 8006acf: The template parameter schema response now exposes a formDecorators field instead of EXPERIMENTAL_formDecorators. Templates that still declare spec.EXPERIMENTAL_formDecorators are read transparently and surfaced under the new field.

Patch Changes

• c78b3b6: Add explicit memory management to SecureTemplater usage
• 1ecc3ca: Fixed spelling mistakes in internal code
• e9b78e9: Removed the uuid dependency and replaced usage with the built-in crypto.randomUUID().
• Updated dependencies
  • @​backstage/catalog-model@​1.9.0
  • @​backstage/errors@​1.3.1
  • @​backstage/backend-plugin-api@​1.9.1
  • @​backstage/plugin-catalog-node@​2.2.1
  • @​backstage/integration@​2.0.2
  • @​backstage/plugin-scaffolder-node@​0.13.3
  • @​backstage/plugin-permission-node@​0.11.0
  • @​backstage/plugin-permission-common@​0.9.9
  • @​backstage/plugin-scaffolder-common@​2.2.0
  • @​backstage/backend-openapi-utils@​0.6.9
  • @​backstage/config@​1.3.8
  • @​backstage/plugin-events-node@​0.4.22

4.0.0-next.2

Major Changes

• c78b3b6: Add explicit memory management to SecureTemplater usage

Minor Changes

• 8006acf: The template parameter schema response now exposes a formDecorators field instead of EXPERIMENTAL_formDecorators. Templates that still declare spec.EXPERIMENTAL_formDecorators are read transparently and surfaced under the new field.

Patch Changes

• 1ecc3ca: Fixed spelling mistakes in internal code
• Updated dependencies
  • @​backstage/backend-plugin-api@​1.9.1-next.1
  • @​backstage/plugin-scaffolder-common@​2.2.0-next.1
  • @​backstage/plugin-scaffolder-node@​0.13.3-next.2

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
  You can disable automated security fix PRs for this repo from the Security Alerts page.