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.

Sign up for GitHub

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

Jump to bottom

Upgrade from Node.js 16 to Node.js 20 #207

Closed
rafalpietrawski opened this issue Jan 25, 2024 · 4 comments · Fixed by #208
Closed

Upgrade from Node.js 16 to Node.js 20 #207

rafalpietrawski opened this issue Jan 25, 2024 · 4 comments · Fixed by #208

Comments

@rafalpietrawski
Copy link

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: mdgreenwald/mozilla-sops-action@v1.5.0. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
@fabn fabn mentioned this issue Feb 15, 2024
Merged
nickstenning added a commit to replicate/actions that referenced this issue Feb 22, 2024
@nickstenning
Bump sops action
791d4e8 
This will still complain about Node 16 usage. See:

  mdgreenwald/mozilla-sops-action#207
@mdgreenwald
Copy link
Owner

@fabn This should be fixed in v1.6.0.

@fabn
Copy link
Contributor

fabn commented Mar 4, 2024

Thanks 💪🏻

@mdgreenwald
Copy link
Owner

@fabn Sorry it took so long! I have been battling several illnesses and then went on a brief vacation. Glad I could help get this fixed for you. 👍🏻

@fabn
Copy link
Contributor

fabn commented Mar 4, 2024

Don't worry, I hope everything is ok now. Thanks again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use node 20 for action fabn/mozilla-sops-action
3 participants
@fabn @mdgreenwald @rafalpietrawski