Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🔧 Repository: Move to Node 20 and 22 in CI #2490

Open
2 tasks done
awanlin opened this issue Jan 13, 2025 · 0 comments
Open
2 tasks done

🔧 Repository: Move to Node 20 and 22 in CI #2490

awanlin opened this issue Jan 13, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@awanlin
Copy link
Contributor

awanlin commented Jan 13, 2025

📜 Description

The upstream Backstage repo has moved to running their CI using Node 20 and 22 as per their Node version policy. This was done as part of the 1.33.0 release.

We should also move to Node 20 and 22 in our CI so that we can be sure that plugins will work on the supported Node versions. Ideally upgrading all the plugins to a version equal to or greater than 1.33.0 would be the first step. This Renovate PR #2403 should give us some insights as to which plugins might need additional work to support this change.

👍 Expected behavior

We should be running the CI using Node 20 and 22

👎 Current Behavior

We are currently running the CI using Node 18 and 20

👟 Reproduction steps

N/A

📃 Provide the context for the Bug.

Backstage Adopters have already started to use Node 22 as the default. By staying on top of this it will help avoid issues with plugins that might not work with Node 22.

👀 Have you spent some time to check if this bug has been raised before?

  • I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

Are you willing to submit PR?

No, I don't have time to work on this right now

@awanlin awanlin added the bug Something isn't working label Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant