Unable to upgrade to a specific release using Yarn Backstage Plugin

[awanlin]

📜 Issue Labels

• [x] Please familiarize yourself with the issue labels used in this project: LABELS.md

🔎 Search Terms

specific release, upgrade version, yarn plugin

🗃️ Project Area

CLI Tooling

🔗 External Integration

N/A

📝 Description & Context

Not all adopters are able to or wanting to stay on the bleeding edge of Backstage releases. You might be 2-3 versions behind. When using the Backstage Yarn Plugin you aren't able to upgrade to a specific release as it will bring in newer packages due to its use of the ^ in the backstage:^.

Note: I believe this is also true if you are not using the Backstage Yarn Plugin as seen in https://github.com/backstage/backstage/issues/28925

👍 Expected Behavior

When using the Backstage Yarn Plugin and running a version bump like yarn backstage-cli versions:bump --release 1.42.5 I should not get any packages from a newer release like from 1.43.0

📦 Reproduction Repo

No response

🥾 Reproduction steps

This is a bit tricky to repo, these steps might not work, but should give you a rough idea:

1. Create a new Backstage instance on an older version, say 1.41.0
2. Add the Backstage Yarn Plugin
3. Run yarn backstage-cli versions:bump --release 1.42.5
4. Start the instance

Notice: you'll might get errors but you'll also get newer package versions then the ones in the 1.42.5 release manifest: https://github.com/backstage/versions/blob/main/v1/releases/1.42.5/manifest.json

Have you read the Code of Conduct?

• [x] I have read the Code of Conduct

Are you willing to submit PR?

No, but I'm happy to collaborate on a PR with someone else

[awanlin]

@aramissennyeydd we talked about this a few weeks ago, is this the rough experience you are seeing?

[awanlin]

@mtlewis, as the author of the Backstage Yarn Plugin would be great to get your thoughts on this as well 👍

[awanlin]

This Discord thread prompted me to create this issue: https://discord.com/channels/687207715902193673/1364916163183644702

[vinzscam]

I think one option is to add support for backstage:* and perhaps use it as default

[freben]

Agreed with the above. Maybe we should investigate using * dependencies for these.

[aramissennyeydd]

@awanlin just saw this issue - yes! this is the issue I was seeing. I will also add that transitive deps also need to be adjusted, I added yarn resolutions that match the manifest to fix this issue.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.