-
-
Notifications
You must be signed in to change notification settings - Fork 375
chore: Upgrade @octokit/rest for CVE patch - no-ESM mitigation patch - Fixes #1479 #1481
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
Conversation
- v19 dropped support for node 10/12 (https://github.com/octokit/rest.js/releases/tag/v19.0.0) - v20 dropped support for node 14/16, removed preview support for the REST API, and removed the agent option (https://github.com/octokit/rest.js/releases/tag/v20.0.0) - v21 updated the package to ESM (https://github.com/octokit/rest.js/releases/tag/v21.0.0) None of these breaking changes should impact v12 of danger-js as it requires node >= 18.
Hate this field.
This is a build-tool so doesn't affect our users, but it does prevent casual CI testing on Node 18.
@orta Appveyor appears to be failing the CI, even though all the tests passed, and there's no reported error messages |
Eh, I can live with the appveyor builds being red |
Hello folks -- how do we progress landing this fix? |
+1 to the above - any updates? Looks like the green light has been given |
@justinc324 @mikehall314 I've merged it, but I don't have permissions to package and ship a release, so it'll go out when that next happens. In the meantime, you could directly reference the SHA in your package version selectors, I think? |
Alternative PR for: #1477
Fixes: #1479
Fixes transitive CVE: GHSA-h5c3-5r3r-rr8q
Contents
"^20.9.0 || >=22.0.0"
. I could tweak CI to install with node-20, and then run it with node 18, but that seems messy/risky/low-value.This kicks the can down the road on our migration to ESM.