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

Use Node16 instead of Node12 #170

Open
BrycensRanch opened this issue Feb 27, 2023 · 5 comments
Open

Use Node16 instead of Node12 #170

BrycensRanch opened this issue Feb 27, 2023 · 5 comments

Comments

@BrycensRanch
Copy link

BrycensRanch commented Feb 27, 2023 •
edited
Loading

Support for Node.js 12 will soon be dropped by GitHub Actions.
@ataylormays-duetto
Copy link

+1

@BrycensRanch
Copy link
Author

No response, time to make a fork

@lcollins lcollins mentioned this issue Oct 16, 2023
Open
@lcollins
Copy link

It looks like Node 20 has overtaken Node 16 on GitHub Actions (https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/)

@BrycensRanch
Copy link
Author

It looks like Node 20 has overtaken Node 16 on GitHub Actions (https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/)

most based open source contributor now I wonder how long it'll take for that PR to get merged. See you in 12 months looool

@lcollins
Copy link

FYI all - I have released a folk of this action to the marketplace here https://github.com/marketplace/actions/publish-spotbugs-report

Will deprecate it if the original author accepts my PR #176

@h3xstream h3xstream mentioned this issue Jan 10, 2024
Open
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

No branches or pull requests
3 participants
@lcollins @ataylormays-duetto @BrycensRanch