Skip to content

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Aug 15, 2025

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

Release notes

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

v1.42.0-next.3

See docs/releases/v1.42.0-next.3-changelog.md for more information.

v1.42.0-next.2

See docs/releases/v1.42.0-next.2-changelog.md for more information.

v1.42.0-next.1

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

v1.42.0-next.0

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

v1.41.2

This release fixes an issue where the logger would log both redacted and non redacted secrets if used as input into fetch:template.

v1.41.1

This release fixes an issue where the new @backstage/ui package was empty.

v1.41.0

These are the release notes for the v1.41.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: Catalog Backend 3.0 - New Defaults

This major release of the catalog plugin backend switches the default value of a number of different flags that affect the behavior of the catalog. backstage/backstage#30546

catalog.orphanStrategy is now delete by default

This switches the default orphan strategy to eagerly delete entities that are no longer referenced within the catalog.

This flag has been suggested many times as a way to clean up entities that have been moved or deleted, and we’re feeling that it’s a good time to turn this on by default.

You can opt back into the previous behavior by supplying orphanStrategy: keep in config.

catalog.orphanProviderStrategy is now delete by default

This switches the default provider installation strategy to no longer keep around entities from providers that are no longer present.

If you have had providers installed in the past that ingested entities into the catalog that you want to keep, the recommendation is to add the provider back to the catalog. If you don’t want the provider to run, you can schedule it with a very large interval.

catalog.disableRelationsCompatibility enabled by default

Relations compatibility is now disabled by default. It can be re-enabled with the new enableRelationsCompatibility flag, but be aware that this significantly reduces overall performance of the catalog.

Relations compatibility ensures that catalog responses contain both targetRef and target within the relations objects, while if it is disabled, only targetRef will be present. The target has not been needed within the Backstage ecosystem for a long time, as the move to targetRef was rolled out many years ago. Therefore, only bespoke external consumers of the catalog should be affected by this change.

... (truncated)

Changelog

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

@​backstage/plugin-scaffolder-backend

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

2.2.0-next.0

Minor Changes

  • c08cbc4: Move Scaffolder API to OpenAPI
  • 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
  • Updated dependencies
    • @​backstage/backend-defaults@​0.11.2-next.0
    • @​backstage/backend-openapi-utils@​0.6.0-next.0
    • @​backstage/plugin-scaffolder-common@​1.7.0-next.0
    • @​backstage/plugin-scaffolder-node@​0.11.0-next.0
    • @​backstage/plugin-scaffolder-backend-module-gitlab@​0.9.4-next.0
    • @​backstage/plugin-catalog-node@​1.18.0-next.0
    • @​backstage/plugin-auth-node@​0.6.6-next.0
    • @​backstage/plugin-permission-node@​0.10.3-next.0
    • @​backstage/plugin-catalog-backend-module-scaffolder-entity-model@​0.2.11-next.0
    • @​backstage/plugin-scaffolder-backend-module-azure@​0.2.12-next.0
    • @​backstage/plugin-scaffolder-backend-module-bitbucket@​0.3.13-next.0
    • @​backstage/plugin-scaffolder-backend-module-bitbucket-cloud@​0.2.12-next.0
    • @​backstage/plugin-scaffolder-backend-module-bitbucket-server@​0.2.12-next.0
    • @​backstage/plugin-scaffolder-backend-module-gerrit@​0.2.12-next.0
    • @​backstage/plugin-scaffolder-backend-module-gitea@​0.2.12-next.0
    • @​backstage/plugin-scaffolder-backend-module-github@​0.8.2-next.0
    • @​backstage/backend-plugin-api@​1.4.2-next.0
    • @​backstage/plugin-events-node@​0.4.14-next.0
    • @​backstage/catalog-model@​1.7.5
    • @​backstage/config@​1.3.3
    • @​backstage/errors@​1.2.7
    • @​backstage/integration@​1.17.1
    • @​backstage/types@​1.2.1

... (truncated)

Commits

Dependabot compatibility score

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.

Bumps [@backstage/plugin-scaffolder-backend](https://github.com/backstage/backstage/tree/HEAD/plugins/scaffolder-backend) from 1.26.2 to 2.1.1.
- [Release notes](https://github.com/backstage/backstage/releases)
- [Changelog](https://github.com/backstage/backstage/blob/master/plugins/scaffolder-backend/CHANGELOG.md)
- [Commits](https://github.com/backstage/backstage/commits/HEAD/plugins/scaffolder-backend)

---
updated-dependencies:
- dependency-name: "@backstage/plugin-scaffolder-backend"
  dependency-version: 2.1.1
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Aug 15, 2025

Labels

The following labels could not be found: kind/cleanup, ok-to-test, release-note-none. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants