chore(deps): bump @backstage/plugin-scaffolder-backend from 1.33.0 to 2.2.2 in /workspaces/dcm

[dependabot]

Bumps @backstage/plugin-scaffolder-backend from 1.33.0 to 2.2.2.

Release notes

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

v1.48.2

This patch release includes the following fixes:

• Updated @microsoft/api-extractor to 7.57.3 (#32950)
• Add back formFieldsApiRef and ScaffolderFormFieldsApi alpha exports from @backstage/plugin-scaffolder (#32969)
• Perform search on first navigate (#32973)

v1.48.1

This patch release fixes the following issues:

• Add missing sharing extensions sidebar item in frontend system architecture docs
• Fix type compatibility for older plugins in FrontendFeature type

v1.48.0

These are the release notes for the v1.48.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 ALPHA: Catalog extension points graduated

If you are providing custom processors and entity providers into the catalog, you will now note that several (but not quite all!) of those extension points have graduated out of alpha and into the regular stable exports.

Thus, if you are importing for example catalogProcessingExtensionPoint from @backstage/plugin-catalog-node/alpha, you now want to remove that /alpha suffix.

BREAKING: API restrictions in New Frontend System

In the 1.47 release a new behavior was introduced to the New Frontend System that limits the ability for plugins and modules to provide APIs to plugins other than themselves. For example, the scaffolder plugin could no longer install a custom CatalogApi implementation. This also applies to modules, where you now need to use a module explicitly targeting the 'app' plugin to for example override the ErrorApi.

In 1.47 this new behavior simply triggered a warning, but in this release the API overrides are instead rejected with an error.

Experimental Client ID Metadata Documents

With the latest MCP specification published in November, it outlined a new authorization method that’s going to take over from Dynamic Client Registration called Client ID Metadata Documents.

This can be enabled in the auth-backend plugin by using the auth.experimentalClientIdMetadataDocuments.enabled flag in config.

Be sure to head over to the changelog for additional configuration and security considerations.

Experimental Refresh Token Support

Clients can now request the offline_access scope to receive refresh tokens when auth.experimentalRefreshToken.enabled is set, allowing new access tokens without re-authentication. This can be highly useful when using experimentalDynamicClientRegistration so that the tokens don’t expire every 1h by default, which then triggers another auth session approval request.

This also means that auth.experimentalDynamicClientRegistration.tokenExpiration has been removed in favor of using this method as a BREAKING EXPERIMENTAL change.

New Frontend System: Testing utilities

The testing utilities for the new frontend system have gotten an overhaul in this release, with all new features documented in the plugin testing section. Some highlights include that mountedRoutes and apis options are available for all harnesses where applicable. The selection of mockApis has been increased to support more of the core APIs and have both Jest and minimal implementation mocks. The mockApis now also produces values that can be passed directly to the various testing apis options, without the need to wrap [ref, impl] tuples.

... (truncated)

Changelog

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

@​backstage/plugin-scaffolder-backend

3.1.3

Patch Changes

• 7455dae: Use node prefix on native imports
• 4fc7bf0: Removed unused dependency
• 0ce78b0: Support if conditions inside each loops for scaffolder steps
• 5e3ef57: Added peerModules metadata declaring recommended modules for cross-plugin integrations.
• 8148621: Moved @backstage/backend-defaults from dependencies to devDependencies.
• 1e669cc: Migrate audit events reference docs to http://backstage.io/docs.
• 69d880e: Bump to latest zod to ensure it has the latest features
• Updated dependencies
  • @​backstage/plugin-scaffolder-backend-module-gitlab@​0.11.3
  • @​backstage/integration@​1.20.0
  • @​backstage/plugin-catalog-backend-module-scaffolder-entity-model@​0.2.17
  • @​backstage/plugin-catalog-node@​2.0.0
  • @​backstage/plugin-scaffolder-backend-module-bitbucket-cloud@​0.3.3
  • @​backstage/plugin-scaffolder-backend-module-bitbucket@​0.3.19
  • @​backstage/plugin-scaffolder-backend-module-gerrit@​0.2.18
  • @​backstage/plugin-scaffolder-backend-module-github@​0.9.6
  • @​backstage/plugin-scaffolder-backend-module-gitea@​0.2.18
  • @​backstage/backend-openapi-utils@​0.6.6
  • @​backstage/plugin-bitbucket-cloud-common@​0.3.7
  • @​backstage/backend-plugin-api@​1.7.0
  • @​backstage/plugin-scaffolder-node@​0.12.5
  • @​backstage/plugin-auth-node@​0.6.13
  • @​backstage/plugin-permission-common@​0.9.6
  • @​backstage/plugin-permission-node@​0.10.10
  • @​backstage/plugin-events-node@​0.4.19
  • @​backstage/plugin-scaffolder-backend-module-azure@​0.2.18
  • @​backstage/plugin-scaffolder-backend-module-bitbucket-server@​0.2.18
  • @​backstage/plugin-scaffolder-common@​1.7.6

3.1.3-next.2

Patch Changes

• 8148621: Moved @backstage/backend-defaults from dependencies to devDependencies.
• Updated dependencies
  • @​backstage/plugin-scaffolder-backend-module-gitlab@​0.11.3-next.2
  • @​backstage/integration@​1.20.0-next.2
  • @​backstage/plugin-catalog-node@​2.0.0-next.1
  • @​backstage/backend-plugin-api@​1.7.0-next.1
  • @​backstage/plugin-auth-node@​0.6.13-next.1
  • @​backstage/plugin-catalog-backend-module-scaffolder-entity-model@​0.2.17-next.1
  • @​backstage/plugin-events-node@​0.4.19-next.0
  • @​backstage/plugin-permission-node@​0.10.10-next.0
  • @​backstage/plugin-scaffolder-backend-module-bitbucket@​0.3.19-next.1

... (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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[rhdh-gh-app]

Changed Packages

Package Name	Package Path	Changeset Bump	Current Version
backend	workspaces/dcm/packages/backend	none	v0.0.1

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud