chore: upgrade @backstage/backend-plugin-api and @backstage/plugin-scaffolder-node

[heinzburgstaller]

Introduction

Upgrade

• @backstage/plugin-scaffolder-node
• @backstage/backend-plugin-api

[Copilot]

Pull request overview

This pull request upgrades two Backstage dependencies: @backstage/backend-plugin-api from ^1.4.2 to 1.6.1 and adds @backstage/plugin-scaffolder-node at version 0.12.3 to the resolutions field.

Changes:

• Upgraded @backstage/backend-plugin-api to version 1.6.1 in the backend package
• Added @backstage/[email protected] to yarn resolutions
• Updated yarn.lock with new package versions and their transitive dependencies

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated 2 comments.

File	Description
packages/backend/package.json	Updated @backstage/backend-plugin-api version from ^1.4.2 to 1.6.1
package.json	Added @backstage/[email protected] to resolutions field
yarn.lock	Added new package versions including @backstage/[email protected], @backstage/[email protected], and related transitive dependencies

[Copilot]

Adding @backstage/plugin-scaffolder-node to the resolutions field forces version 0.12.3 across the entire monorepo. However, @backstage/[email protected] (used in packages/backend/package.json) depends on "^0.11.2". This resolution forces a minor version upgrade from 0.11.x to 0.12.3, which could introduce breaking changes. Verify that this forced upgrade is intentional and that @backstage/[email protected] is compatible with @backstage/[email protected], or consider upgrading @backstage/plugin-scaffolder-backend to a version that officially supports 0.12.x.

Suggested change

	"@backstage/plugin-scaffolder-node": "0.12.3"
	"@backstage/plugin-scaffolder-node": "0.11.2"

[Copilot]

Pull request overview

Copilot reviewed 2 out of 3 changed files in this pull request and generated 2 comments.

[Copilot]

The addition of these resolutions with exact versions needs careful consideration. The resolution for @backstage/plugin-scaffolder-node to version 0.12.3 forces all transitive dependencies to use this exact version, but @backstage/plugin-scaffolder-backend@^2.2.0 (a direct dependency in packages/backend) requires ^0.11.2, which is a major version behind. While Yarn will force the resolution, this creates a potential incompatibility risk.

Similarly, @backstage/backend-plugin-api is being forced to 1.6.1, but @backstage/backend-tasks@^0.6.1 (a direct dependency) requires ^0.8.1. This is a breaking change from 0.x to 1.x and could introduce runtime issues.

Consider whether these packages should be upgraded in their direct dependencies first, or if the resolutions are intentionally forcing newer versions to address specific issues. If forcing versions is intentional (e.g., for security fixes), this should be documented and thoroughly tested.