chore(deps): Bump the npm_and_yarn group across 2 directories with 7 updates

[dependabot]

Bumps the npm_and_yarn group with 7 updates in the / directory:

Package	From	To
@backstage/plugin-scaffolder-backend	1.33.0	2.1.1
cipher-base	1.0.4	1.0.7
js-yaml	3.14.1	3.14.2
node-forge	1.3.1	1.3.2
pbkdf2	3.1.2	3.1.5
sha.js	2.4.11	2.4.12
webpack-dev-server	5.1.0	5.2.2

Bumps the npm_and_yarn group with 1 update in the /packages/backend directory: @backstage/plugin-scaffolder-backend.

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

Release notes

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

v1.46.0-next.0

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

v1.45.2

This patch release fixes the following issues:

• Fixed an issue where the useTable hook from @backstage/ui did not use the provided rowCount
• Fix table row with href still being rendered with routing context in @backstage/ui
• Fix incorrectly applying className to three elements internally in ButtonIcon in @backstage/ui.
• Fix unselected Checkboxes subtly appearing selected in @backstage/ui.

v1.45.1

This release fixes an issue where multiple versions of @backstage/frontend-plugin-api could lead to a .withContext is not a function crash.

v1.45.0

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

Backstage UI: Breaking Changes + New Components

Multiple components migrated from Base UI to React Aria Components including Avatar, Checkbox, and removal of the Collapsible component in favour of Accordion.

Check the CHANGELOG.md for more migration guides on any breaking changes that come with these latest updates.

BREAKING: ldapjs -> ldapts

Moved from deprecated ldapjs dependency to ldapts, with breaking changes to custom transformer types and search options.

Contributed by @​ganives in #30594

Check the CHANGELOG.md for more migration guides on any breaking changes that come with these latest updates.

NFS: Plugin-Relative Extension Attachments

Added support for plugin-relative attachTo declarations for extension definitions, allowing extensions to attach to other extensions of a particular kind in the same plugin rather than requiring exact extension IDs.

NFS: Forwards Compatibility for Route Refs

It is now possible to use route references from the old frontend system directly in the new one. That means there's no longer a need to use convertLegacyRouteRef or convertLegacyRouteRefs to re-use route refs in implementations for the new system. This both simplifies migration, and reduces risk for cross system issues while partially migrated.

This requires no immediate action on your part. As long as a plugin intends to support the old system, it can still keep defining its route refs using the old system without issues. And calling convertLegacyRouteRef or convertLegacyRouteRefs does not cause problems.

Configurable Dynamic Client Registration Token Expiration

Allow configuring dynamic client registration token expiration with config auth.experimentalDynamicClientRegistration.tokenExpiration. Maximum expiration for the DCR token is 24 hours. Default expiration is 1 hour. Contributed by @​drodil in #31278

Support for Bitbucket Cloud API tokens

... (truncated)

Changelog

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

@​backstage/plugin-scaffolder-backend

3.1.0-next.0

Minor Changes

• a4cd405: Add defaultEnvironment config to scaffolder to enable more flexible and custom templates. Now it's possible enable access to default parameters and secrets in templates, improving security and reducing complexity.

Patch Changes

• 8f4aded: Fixing OpenAPI definition
• Updated dependencies
  • @​backstage/plugin-auth-node@​0.6.10-next.0
  • @​backstage/backend-defaults@​0.14.0-next.0
  • @​backstage/backend-plugin-api@​1.5.1-next.0
  • @​backstage/integration@​1.18.3-next.0
  • @​backstage/plugin-permission-node@​0.10.7-next.0
  • @​backstage/backend-openapi-utils@​0.6.4-next.0
  • @​backstage/plugin-catalog-backend-module-scaffolder-entity-model@​0.2.15-next.0
  • @​backstage/plugin-catalog-node@​1.20.1-next.0
  • @​backstage/plugin-events-node@​0.4.18-next.0
  • @​backstage/plugin-scaffolder-backend-module-azure@​0.2.16-next.0
  • @​backstage/plugin-scaffolder-backend-module-bitbucket@​0.3.17-next.0
  • @​backstage/plugin-scaffolder-backend-module-bitbucket-cloud@​0.2.16-next.0
  • @​backstage/plugin-scaffolder-backend-module-bitbucket-server@​0.2.16-next.0
  • @​backstage/plugin-scaffolder-backend-module-gerrit@​0.2.16-next.0
  • @​backstage/plugin-scaffolder-backend-module-gitea@​0.2.16-next.0
  • @​backstage/plugin-scaffolder-backend-module-github@​0.9.3-next.0
  • @​backstage/plugin-scaffolder-backend-module-gitlab@​0.10.1-next.0
  • @​backstage/plugin-scaffolder-node@​0.12.2-next.0
  • @​backstage/plugin-bitbucket-cloud-common@​0.3.5-next.0
  • @​backstage/plugin-scaffolder-common@​1.7.4-next.0
  • @​backstage/config@​1.3.6
  • @​backstage/catalog-model@​1.7.6
  • @​backstage/errors@​1.2.7
  • @​backstage/types@​1.2.2
  • @​backstage/plugin-permission-common@​0.9.3

3.0.1

Patch Changes

• 05f60e1: Refactored constructor parameter properties to explicit property declarations for compatibility with TypeScript's erasableSyntaxOnly setting. This internal refactoring maintains all existing functionality while ensuring TypeScript compilation compatibility.
• Updated dependencies
  • @​backstage/backend-defaults@​0.13.1
  • @​backstage/plugin-catalog-node@​1.20.0
  • @​backstage/plugin-scaffolder-backend-module-bitbucket-cloud@​0.2.15
  • @​backstage/plugin-scaffolder-backend-module-bitbucket@​0.3.16
  • @​backstage/plugin-bitbucket-cloud-common@​0.3.4
  • @​backstage/integration@​1.18.2

... (truncated)

Commits

• See full diff in compare view

Updates cipher-base from 1.0.4 to 1.0.7

Changelog

Sourced from cipher-base's changelog.

v1.0.7 - 2025-09-24

Commits

• [Refactor] use to-buffer fd1e5ee
• [Dev Deps] update @ljharb/eslint-config 08ba803

v1.0.6 - 2024-11-26

Commits

• [Fix] io.js 3.0 - Node.js 5.3 typed array support b7ddd2a

v1.0.5 - 2024-11-17

Commits

• [Tests] standard -> eslint, make test dir, etc ae02fd6
• [Tests] migrate from travis to GHA 66387d7
• [meta] fix package.json indentation 5c02918
• [Fix] return valid values on multi-byte-wide TypedArray input 8fd1364
• [meta] add auto-changelog 88dc806
• [meta] add npmignore and safe-publish-latest 7a137d7
• Only apps should have lockfiles 42528f2
• [Deps] update inherits, safe-buffer 0e7a2d9
• [meta] add missing engines.node f2dc13e

Commits

• 0056718 v1.0.7
• fd1e5ee [Refactor] use to-buffer
• 08ba803 [Dev Deps] update @ljharb/eslint-config
• f5249f9 v1.0.6
• b7ddd2a [Fix] io.js 3.0 - Node.js 5.3 typed array support
• f03cebf v1.0.5
• 88dc806 [meta] add auto-changelog
• 7a137d7 [meta] add npmignore and safe-publish-latest
• 5c02918 [meta] fix package.json indentation
• 8fd1364 [Fix] return valid values on multi-byte-wide TypedArray input
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by ljharb, a new releaser for cipher-base since your current version.

Updates js-yaml from 3.14.1 to 3.14.2

Changelog

Sourced from js-yaml's changelog.

[3.14.2] - 2025-11-15

Security

• Backported v4.1.1 fix to v3

[4.1.1] - 2025-11-12

Security

• Fix prototype pollution issue in yaml merge (<<) operator.

[4.1.0] - 2021-04-15

Added

• Types are now exported as yaml.types.XXX.
• Every type now has options property with original arguments kept as they were (see yaml.types.int.options as an example).

Changed

• Schema.extend() now keeps old type order in case of conflicts (e.g. Schema.extend([ a, b, c ]).extend([ b, a, d ]) is now ordered as abcd instead of cbad).

[4.0.0] - 2021-01-03

Changed

• Check migration guide to see details for all breaking changes.
• Breaking: "unsafe" tags !!js/function, !!js/regexp, !!js/undefined are moved to js-yaml-js-types package.
• Breaking: removed safe* functions. Use load, loadAll, dump instead which are all now safe by default.
• yaml.DEFAULT_SAFE_SCHEMA and yaml.DEFAULT_FULL_SCHEMA are removed, use yaml.DEFAULT_SCHEMA instead.
• yaml.Schema.create(schema, tags) is removed, use schema.extend(tags) instead.
• !!binary now always mapped to Uint8Array on load.
• Reduced nesting of /lib folder.
• Parse numbers according to YAML 1.2 instead of YAML 1.1 (01234 is now decimal, 0o1234 is octal, 1:23 is parsed as string instead of base60).
• dump() no longer quotes :, [, ], (, ) except when necessary, #470, #557.
• Line and column in exceptions are now formatted as (X:Y) instead of at line X, column Y (also present in compact format), #332.
• Code snippet created in exceptions now contains multiple lines with line numbers.
• dump() now serializes undefined as null in collections and removes keys with undefined in mappings, #571.
• dump() with skipInvalid=true now serializes invalid items in collections as null.
• Custom tags starting with ! are now dumped as !tag instead of !<!tag>, #576.
• Custom tags starting with tag:yaml.org,2002: are now shorthanded using !!, #258.

Added

• Added .mjs (es modules) support.
• Added quotingType and forceQuotes options for dumper to configure string literal style, #290, #529.
• Added styles: { '!!null': 'empty' } option for dumper (serializes { foo: null } as "foo: "), #570.

... (truncated)

Commits

• 9963d36 3.14.2 released
• 10d3c8e dist rebuild
• 5278870 fix prototype pollution in merge (<<) (#731)
• See full diff in compare view

Updates node-forge from 1.3.1 to 1.3.2

Changelog

Sourced from node-forge's changelog.

1.3.2 - 2025-11-25

Security

• HIGH: ASN.1 Validator Desynchronization
  • An Interpretation Conflict (CWE-436) vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft ASN.1 structures to desynchronize schema validations, yielding a semantic divergence that may bypass downstream cryptographic verifications and security decisions.
  • Reported by Hunter Wodzenski.
  • CVE ID: CVE-2025-12816
  • GHSA ID: GHSA-5gfm-wpxj-wjgq
• HIGH: ASN.1 Unbounded Recursion
  • An Uncontrolled Recursion (CWE-674) vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft deep ASN.1 structures that trigger unbounded recursive parsing. This leads to a Denial-of-Service (DoS) via stack exhaustion when parsing untrusted DER inputs.
  • Reported by Hunter Wodzenski.
  • CVE ID: CVE-2025-66031
  • GHSA ID: GHSA-554w-wpv2-vw27
• MODERATE: ASN.1 OID Integer Truncation
  • An Integer Overflow (CWE-190) vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft ASN.1 structures containing OIDs with oversized arcs. These arcs may be decoded as smaller, trusted OIDs due to 32-bit bitwise truncation, enabling the bypass of downstream OID-based security decisions.
  • Reported by Hunter Wodzenski.
  • CVE ID: CVE-2025-66030
  • GHSA ID: GHSA-65ch-62r8-g69g

Fixed

• [asn1] Fix for vulnerability identified by CVE-2025-12816 PKCS#12 MAC verification bypass due to missing macData enforcement and improper asn1.validate routine.
• [asn1] Add fromDer() max recursion depth check.
  • Add a asn1.maxDepth global configurable maximum depth of 256.
  • Add a asn1.fromDer() per-call maxDepth option.
  • NOTE: The default maximum is assumed to be higher than needed for valid data. If this assumption is false then this could be a breaking change. Please file an issue if there are use cases that need a higher maximum.
  • NOTE: The per-call maxDepth parameter has not been exposed up through all of the API stack due to the complexities involved. Please file an issue if there are use cases that require this instead of changing the default maximum.
• [asn1] Improve OID handling.
  • Error on parsed OID values larger than 2**32 - 1.
  • Error on DER OID values larger than 2**53 - 1 .

Commits

• 235ad3e Release 1.3.2.
• 2598244 Update changelog.
• 0032dd0 Fix typos.
• d75e08d Run new security test.
• a5ce91d Update changelog formatting.
• 4652de6 Cleanups.
• eb932d9 Fix typo.
• db6954b Fix style.
• afbf7d8 Align error message style.
• 6607445 Revert minor changes.
• Additional commits viewable in compare view

Updates pbkdf2 from 3.1.2 to 3.1.5

Changelog

Sourced from pbkdf2's changelog.

v3.1.5 - 2025-09-23

Commits

• [Fix] only allow finite iterations 67bd94d
• [Fix] restore node 0.10 support 8f59d96
• [Fix] check parameters before the "no Promise" bailout d2dc5f0

v3.1.4 - 2025-09-22

Commits

• [Deps] update create-hash, ripemd160, sha.js, to-buffer 8dbf49b
• [meta] update repo URLs d15bc35
• [Dev Deps] update @ljharb/eslint-config aaf870b

v3.1.3 - 2025-06-20

Commits

• Only apps should have lockfiles 8b06730
• [lint] fix whitespace 9a76e2f
• [lint] fix parens/curlies/semis/etc 6fd84bf
• [meta] add auto-changelog 796c38d
• [Tests] fix tests in node 17 3661fb0
• Revert "[Tests] fix tests in node < 3" 7431b57
• [Tests] fix tests in node < 3 eb9f97a
• [Fix] ensure unknown algorithms throw + known ones match node 26d4fd3
• [Tests] add GHA, always run nyc 513906a
• [lint] fix a few more rules ab04da8
• [lint] switch to eslint 89694cf
• [Tests] add coverage d0d534b
• [Refactor] use to-buffer e3102a8
• [readme] improve badges fca0c9d
• [Tests] remove unused travis file a2c7d93
• [meta] switch from files to npmignore 7f31fbc
• [Tests] use .nycrc 8d628e8
• [Refactor] minor tweaks fc61005
• [Deps] update create-hmac, safe-buffer, sha.js ae2a7d0
• [Fix] pin create-hash, ripemd160 due to breaking changes e079968
• [Tests] fix tests in node 3 45fbcf3
• [meta] skip publishing benchmarks 19ea57b
• [Dev Deps] add missing peer dep 645e252

Commits

• 3687905 v3.1.5
• 67bd94d [Fix] only allow finite iterations
• 8f59d96 [Fix] restore node 0.10 support
• d2dc5f0 [Fix] check parameters before the "no Promise" bailout
• b2ad615 v3.1.4
• 8dbf49b [Deps] update create-hash, ripemd160, sha.js, to-buffer
• aaf870b [Dev Deps] update @ljharb/eslint-config
• d15bc35 [meta] update repo URLs
• 3e40827 v3.1.3
• e3102a8 [Refactor] use to-buffer
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by ljharb, a new releaser for pbkdf2 since your current version.

Updates sha.js from 2.4.11 to 2.4.12

Changelog

Sourced from sha.js's changelog.

v2.4.12 - 2025-07-01

Commits

• [eslint] switch to eslint 7acadfb
• [meta] add auto-changelog b46e711
• [eslint] fix package.json indentation df9d521
• [Tests] migrate from travis to GHA c43c64a
• [Fix] support multi-byte wide typed arrays f2a258e
• [meta] reorder package.json d8d77c0
• [meta] add npmignore 35aec35
• [Tests] avoid console logs 73e33ae
• [Tests] fix tests run in batch 2629130
• [Tests] drop node requirement to 0.10 00c7f23
• [Dev Deps] update buffer, hash-test-vectors, standard, tape, typedarray 92b5de5
• [Tests] drop node requirement to v3 9b5eca8
• [meta] set engines to >= 4 807084c
• Only apps should have lockfiles c72789c
• [Deps] update inherits, safe-buffer 5428cfc
• [Dev Deps] update @ljharb/eslint-config 2dbe0aa
• update README to reflect LICENSE 8938256
• [Dev Deps] add missing peer dep d528896
• [Dev Deps] remove unused buffer dep 94ca724

Commits

• eb4ea2f v2.4.12
• d8d77c0 [meta] reorder package.json
• df9d521 [eslint] fix package.json indentation
• 35aec35 [meta] add npmignore
• d528896 [Dev Deps] add missing peer dep
• b46e711 [meta] add auto-changelog
• 94ca724 [Dev Deps] remove unused buffer dep
• 2dbe0aa [Dev Deps] update @ljharb/eslint-config
• 73e33ae [Tests] avoid console logs
• f2a258e [Fix] support multi-byte wide typed arrays
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by ljharb, a new releaser for sha.js since your current version.

Updates webpack-dev-server from 5.1.0 to 5.2.2

Release notes

Sourced from webpack-dev-server's releases.

v5.2.2

5.2.2 (2025-06-03)

Bug Fixes

• "Overlay enabled" false positive (18e72ee)
• do not crush when error is null for runtime errors (#5447) (309991f)
• remove unnecessary header X_TEST (#5451) (64a6124)
• respect the allowedHosts option for cross-origin header check (#5510) (03d1214)

v5.2.1

5.2.1 (2025-03-26)

Security

• cross-origin requests are not allowed unless allowed by Access-Control-Allow-Origin header
• requests with an IP addresses in the Origin header are not allowed to connect to WebSocket server unless configured by allowedHosts or it different from the Host header

The above changes may make the dev server not work if you relied on such behavior, but unfortunately they carry security risks, so they were considered as fixes.

Bug Fixes

• prevent overlay for errors caught by React error boundaries (#5431) (8c1abc9)
• take the first network found instead of the last one, this restores the same behavior as 5.0.4 (#5411) (ffd0b86)

v5.2.0

5.2.0 (2024-12-11)

Features

• added getClientEntry and getClientHotEntry methods to get clients entries (dc642a8)

Bug Fixes

• speed up initial client bundling (145b5d0)

Changelog

Sourced from webpack-dev-server's changelog.

5.2.2 (2025-06-03)

Bug Fixes

• "Overlay enabled" false positive (18e72ee)
• do not crush when error is null for runtime errors (#5447) (309991f)
• remove unnecessary header X_TEST (#5451) (64a6124)
• respect the allowedHosts option for cross-origin header check (#5510) (03d1214)

5.2.1 (2025-03-26)

Security

• cross-origin requests are not allowed unless allowed by Access-Control-Allow-Origin header
• requests with an IP addresses in the Origin header are not allowed to connect to WebSocket server unless configured by allowedHosts or it different from the Host header

The above changes may make the dev server not work if you relied on such behavior, but unfortunately they carry security risks, so they were considered as fixes.

Bug Fixes

• prevent overlay for errors caught by React error boundaries (#5431) (8c1abc9)
• take the first network found instead of the last one, this restores the same behavior as 5.0.4 (#5411) (ffd0b86)

5.2.0 (2024-12-11)

Features

• added getClientEntry and getClientHotEntry methods to get clients entries (dc642a8)

Bug Fixes

• speed up initial client bundling (145b5d0)

Commits

• 195a7e6 chore(release): 5.2.2
• 620bef1 chore(deps): update (#5511)
• 03d1214 fix: respect the allowedHosts option for cross-origin header check (#5510)
• 5ba862e chore(deps-dev): bump the dependencies group across 1 directory with 7 update...
• f7fec94 chore: fix typo (#5508)
• 6ee8cd0 ci: add Node.js v24 (#5492)
• d30f963 chore: update http-proxy-middleware to ^2.0.9 (#5503)
• 66cf033 chore(deps-dev): bump the dependencies group with 2 updates (#5504)
• 4367a5c refactor: use 'String#startsWith' & replace if-then-else (#5501)
• 8e6604f chore(deps): bump the dependencies group across 1 directory with 4 updates (#...
• Additional commits viewable in compare view

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

Release notes

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

v1.46.0-next.0

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

v1.45.2

This patch release fixes the following issues:

• Fixed an issue where the useTable hook from @backstage/ui did not use the provided rowCount
• Fix table row with href still being rendered with routing context in @backstage/ui
• Fix incorrectly applying className to three elements internally in ButtonIcon in @backstage/ui.
• Fix unselected Checkboxes subtly appearing selected in @backstage/ui.

v1.45.1

This release fixes an issue where multiple versions of @backstage/frontend-plugin-api could lead to a .withContext is not a function crash.

v1.45.0

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

Backstage UI: Breaking Changes + New Components

Multiple components migrated from Base UI to React Aria Components including Avatar, Checkbox, and removal of the Collapsible component in favour of Accordion.

Check the CHANGELOG.md for more migration guides on any breaking changes that come with these latest updates.

BREAKING: ldapjs -> ldapts

Moved from deprecated ldapjs dependency to ldapts, with breaking changes to custom transformer types and search options.

Contributed by @​ganives in #30594

Check the CHANGELOG.md for more migration guides on any breaking changes that come with these latest updates.

NFS: Plugin-Relative Extension Attachments

Added support for plugin-relative attachTo declarations for extension definitions, allowing extensions to attach to other extensions of a particular kind in the same plugin rather than requiring exact extension IDs.

NFS: Forwards Compatibility for Route Refs

It is now possible to use route references from the old frontend system directly in the new one. That means there's no longer a need to use convertLegacyRouteRef or convertLegacyRouteRefs to re-use route refs in implementations for the new system. This both simplifies migration, and reduces risk for cross system issues while partially migrated.

This requires no immediate action on your part. As long as a plugin intends to support the old system, it can still keep defining its route refs using the old system without issues. And calling convertLegacyRouteRef or convertLegacyRouteRefs does not cause problems.

Configurable Dynamic Client Registration Token Expiration

Allow configuring dynamic client registration token expiration with config auth.experimentalDynamicClientRegistration.tokenExpiration. Maximum expiration for the DCR token is 24 hours. Default expiration is 1 hour. Contributed by @​drodil in #31278

Support for Bitbucket Cloud API tokens

... (truncated)

Changelog

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

@​backstage/plugin-scaffolder-backend

3.1.0-next.0

Minor Changes

• a4cd405: Add defaultEnvironment config to scaffolder to enable more flexible and custom templates. Now it's possible enable access to default parameters and secrets in templates, improving security and reducing complexity.

Patch Changes

• 8f4aded: Fixing OpenAPI definition
• Updated dependencies
  • @​backstage/plugin-auth-node@​0.6.10-next.0
  • @​backstage/backend-defaults@​0.14.0-next.0
  • @​backstage/backend-plugin-api@​1.5.1-next.0
  • @​backstage/integration@​1.18.3-next.0
  • @​backstage/plugin-permission-node@​0.10.7-next.0
  • @​backstage/backend-openapi-utils@​0.6.4-next.0
  • @​backstage/plugin-catalog-backend-module-scaffolder-entity-model@​0.2.15-next.0
  • @​backstage/plugin-catalog-node@​1.20.1-next.0
  • @​backstage/plugin-events-node@​0.4.18-next.0
  • @​backstage/plugin-scaffolder-backend-module-azure@​0.2.16-next.0
  • @​backstage/plugin-scaffolder-backend-module-bitbucket@​0.3.17-next.0
  • @​backstage/plugin-scaffolder-backend-module-bitbucket-cloud@​0.2.16-next.0
  • @​backstage/plugin-scaffolder-backend-module-bitbucket-server@​0.2.16-next.0
  • @​backstage/plugin-scaffolder-backend-module-gerrit@​0.2.16-next.0
  • @​backstage/plugin-scaffolder-backend-module-gitea@​0.2.16-next.0
  • @​backstage/plugin-scaffolder-backend-module-github@​0.9.3-next.0
  • @​backstage/plugin-scaffolder-backend-module-gitlab@​0.10.1-next.0
  • @​backstage/plugin-scaffolder-node@​0.12.2-next.0
  • @​backstage/plugin-bitbucket-cloud-common@​0.3.5-next.0
  • @​backstage/plugin-scaffolder-common@​1.7.4-next.0
  • @​backstage/config@​1.3.6
  • @​backstage/catalog-model@​1.7.6
  • @​backstage/errors@​1.2.7
  • @​backstage/types@​1.2.2
  • @​backstage/plugin-permission-common@​0.9.3

3.0.1

Patch Changes

• 05f60e1: Refactored constructor parameter properties to explicit property declarations for compatibility with TypeScript's erasableSyntaxOnly setting. This internal refactoring maintains all existing functionality while ensuring TypeScript compilation compatibility.
• Updated dependencies
  • @​backstage/backend-defaults@​0.13.1
  • @​backstage/plugin-catalog-node@​1.20.0
  • @​backstage/plugin-scaffolder-backend-module-bitbucket-cloud@​0.2.15
  • @​backstage/plugin-scaffolder-backend-module-bitbucket@​0.3.16
  • @​backstage/plugin-bitbucket-cloud-common@​0.3.4
  • @​backstage/integration@​1.18.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 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 <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.

[johnnyhuy]

@copilot update lock file

[Copilot]

@johnnyhuy I've opened a new pull request, #63, to work on those changes. Once the pull request is ready, I'll request review from you.

[johnnyhuy]

@copilot The job failed due to a TypeScript error in packages/backend/src/index.ts at line 7. The error message indicates an issue with '$$type' being declared, most likely due to an incorrect import or usage of the alpha version of the plugin.

To resolve the error:

1. Check that the import path for '@backstage/plugin-scaffolder-backend/alpha' is correct and corresponds to a valid export. If possible, use the stable version of the package instead.
2. If the alpha version is necessary, ensure your TypeScript configuration allows for the plugin’s types, and that any related dependencies are updated to compatible versions.

Suggested fix:
Replace:

backend.add(import('@backstage/plugin-scaffolder-backend/alpha'));

with:

backend.add(import('@backstage/plugin-scaffolder-backend'));

Or, verify the correct usage according to the latest documentation for the alpha module.

See the problematic code and context in your repository at this revision:
https://github.com/echohello-dev/backstage/blob/8ba482b411cd6a30719769c079009400308b3d3c/packages/backend/src/index.ts

After this change, rebuild your project to confirm the issue is resolved.

[Copilot]

@johnnyhuy I've opened a new pull request, #64, to work on those changes. Once the pull request is ready, I'll request review from you.