-
Notifications
You must be signed in to change notification settings - Fork 54
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
Upgrade to Node 20.12.2 #112
Upgrade to Node 20.12.2 #112
Conversation
Fixed uglify configurations to change based on whether we are in debug mode or not.
One question on this one. I kept the npm |
Upgrading grunt-contrib-uglify to 5.2.2 ensures that we're consistently using a modern version of Uglify that can handle modern syntax.
The CI steps need to be updated to use Node 20. While doing so, we incorporate some additional work: - Update all actions to use the latest versions that run on Node 20 - Update the test matrix to use our .nvmrc file as one of the Node versions to test against - Check for uncommitted changes after installing dependencies
8592d6e
to
7463868
Compare
I don't really have an option either way. Consistency is good, but |
Upgraded the project to Node 20.12.2, including its GitHub Actions job.
This supersedes PR #111, see that PR for additional notes that were taken into consideration.