Skip to content

Conversation

basti1302
Copy link
Member

Now that Node.js 22.8 is out, which fixes
nodejs/node#54518, we can unpin Node.js 22 again. This commit reverts #80345a1cd11a13a7fa9e7db8230244ed56c78034.

Now that Node.js 22.8 is out, which fixes
nodejs/node#54518, we can unpin Node.js 22
again. This commit reverts #80345a1cd11a13a7fa9e7db8230244ed56c78034.
@basti1302 basti1302 requested a review from a team as a code owner September 4, 2024 08:44
@basti1302
Copy link
Member Author

basti1302 commented Sep 4, 2024

22.8.0 has been released as a GH action as well but it still downloads 22.7.0 🤔 ... let's wait a bit and try again.

Run actions/setup-node@v4
Attempting to download 22.x...
Acquiring 22.7.0 - x64 from https://github.com/actions/node-versions/releases/download/22.7.0-10511334152/node-22.7.0-linux-x64.tar.gz
Extracting ...

Copy link

sonarqubecloud bot commented Sep 4, 2024

@basti1302 basti1302 enabled auto-merge (rebase) September 17, 2024 09:05
@basti1302 basti1302 merged commit 11457e8 into main Sep 17, 2024
9 checks passed
@basti1302 basti1302 deleted the unpin-nodejs-22 branch September 17, 2024 09:10
Copy link

🎉 This PR is included in version 1.1.5 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant