You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
📜 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?
🏢 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
The text was updated successfully, but these errors were encountered: