chore(deps): bump @backstage/plugin-scaffolder-backend from 1.33.0 to 2.1.1

[dependabot]

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

Release notes

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

v1.42.0

These are the release notes for the v1.42.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

The new Frontend System is Adoption Ready! 🎉

We've been hard at work over the last few months stabilizing the APIs for the New Frontend System, and we're excited to announce that they're ready for prime time! With the release of version 1.42.0, we're officially encouraging all developers to start migrating their apps to the new system, along with all their plugins.

The New Frontend System is a major leap forward, offering a more powerful, flexible, and overall better development experience. By migrating, you’ll be able to take advantage of declarative integration of plugins and removing a large amount of code that’s used to configure your Backstage App. With plugins also migrating, there’s new extensibility patterns on the horizon that will allow you to customize Backstage even further than before.

We know that migrating can be a big undertaking, so we've made it as easy as possible. You can choose to migrate gradually, using a hybrid approach that combines the new and old systems, or you can start fresh with a brand new app using the --next flag.

Whatever path you choose, we've got you covered. Check out our comprehensive migration guide for step-by-step instructions, and don't hesitate to reach out to us on our repository or Discord if you need help.

Default bundler switched to Rspack

The Backstage CLI has been updated to use Rspack as the bundler for frontend apps. It has been available behind the EXPERIMENTAL_RSPACK flag since the 1.32 release, but has now been switched to the default. The use of WebPack can be restored using the LEGACY_WEBPACK_BUILD flag, along with installing the necessary dependencies. See the changelog for @backstage/cli for more information.

Kubernetes Legacy Backend System Removal

We’ve removed support for the legacy backend system, as well all of the deprecated exports for the last plugin in the main repository. With this cleanup, we say goodbye to the last occurrence of the old @backstage/backend-common in the repository!

There’s extensive documentation in the changelog for migrating to the latest version.

Please reach out if you have any issues!

Scaffolder is now powered by OpenAPI + more deprecations!

The Scaffolder router and client are now generated by the OpenAPI tooling. One of the oldest PR’s that we had in the repository has been merged after a lot of hard work. Thanks to @​solimant and @​aramissennyeydd for their continued support throughout!

Also with this, there’s been a lot of types moved into @backstage/plugin-scaffolder-common which means that their original exports from -react have now been deprecated. Please check out the CHANGELOG for more details on the affected types.

Contributed by @​solimant in #27771

Catalog performance improvements

The catalog sometimes did more work than necessary because it was not taking into account that in some places, order doesn’t matter. So that got fixed! The upshot is that you may see in your monitoring that it performs less useless stitching after the upgrade. To achieve this it will have to do a short period of more work right after the upgrade before it converges. Just so you are aware.

Contributed by @​drodil in #30859

Security Fixes

This release also fixes the possibility of the scaffolder logging both redacted and plain text secrets when used as input to the fetch:template action.

Upgrade path

... (truncated)

Changelog

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

@​backstage/plugin-scaffolder-backend

2.2.0

Minor Changes

• c08cbc4: Move Scaffolder API to OpenAPI
• 2032660: Fixed fs:readdir action example
• 11dc90f: Implement max length for scaffolder auditor audit logging with default of 256
• 812485c: Add step info to scaffolder action context to access the step id and name.

Patch Changes

• caee2eb: Fixed WinstonLogger throwing when redactions were null or undefined
• 4ae87f5: add getResources method to permissionIntegrationRouter for frontend task permission checks
• b817c1d: Stop logging of SPLAT twice in logs
• Updated dependencies
  • @​backstage/backend-openapi-utils@​0.6.0
  • @​backstage/backend-defaults@​0.12.0
  • @​backstage/plugin-scaffolder-common@​1.7.0
  • @​backstage/plugin-scaffolder-node@​0.11.0
  • @​backstage/plugin-scaffolder-backend-module-gitlab@​0.9.4
  • @​backstage/plugin-catalog-node@​1.18.0
  • @​backstage/plugin-scaffolder-backend-module-github@​0.8.2
  • @​backstage/plugin-auth-node@​0.6.6
  • @​backstage/plugin-permission-node@​0.10.3
  • @​backstage/backend-plugin-api@​1.4.2
  • @​backstage/plugin-catalog-backend-module-scaffolder-entity-model@​0.2.11
  • @​backstage/plugin-events-node@​0.4.14
  • @​backstage/plugin-scaffolder-backend-module-azure@​0.2.12
  • @​backstage/plugin-scaffolder-backend-module-bitbucket@​0.3.13
  • @​backstage/plugin-scaffolder-backend-module-bitbucket-cloud@​0.2.12
  • @​backstage/plugin-scaffolder-backend-module-bitbucket-server@​0.2.12
  • @​backstage/plugin-scaffolder-backend-module-gerrit@​0.2.12
  • @​backstage/plugin-scaffolder-backend-module-gitea@​0.2.12

2.2.0-next.1

Minor Changes

• 2032660: Fixed fs:readdir action example
• 11dc90f: Implement max length for scaffolder auditor audit logging with default of 256

Patch Changes

• Updated dependencies
  • @​backstage/backend-openapi-utils@​0.6.0-next.1
  • @​backstage/plugin-scaffolder-backend-module-gitlab@​0.9.4-next.1
  • @​backstage/plugin-scaffolder-backend-module-github@​0.8.2-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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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.

[openshift-ci]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a redhat-developer member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[github-actions]

The image is available at:

• quay.io/rhdh-community/rhdh:pr-3305 or
• quay.io/rhdh-community/rhdh:pr-3305-adbffaac

[github-actions]

This PR is stale because it has been open 7 days with no activity. Remove stale label or comment or this will be closed in 21 days.

[github-actions]

The image is available at:

• quay.io/rhdh-community/rhdh:pr-3305
• quay.io/rhdh-community/rhdh:pr-3305-6aa5967f

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign zaperex for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[github-actions]

The image is available at:

• quay.io/rhdh-community/rhdh:pr-3305
• quay.io/rhdh-community/rhdh:pr-3305-2dde69c0

[kim-tsao]

closing as this will require updating to the latest backstage

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.