-
Notifications
You must be signed in to change notification settings - Fork 21
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
Address breaking engine change in dependency #137
Conversation
I updated the PR title to NOT be semantically correct as an extra signal for us to remember to rebase merge this, not squash. The first commit has the correct subject and body for the changelog for the breaking change. |
CI linting failure is a known bug in template-oss that has since been fixed. Ironically it's one of the things that #136 would fix, but we can't land it cause of the engines issue that THIS pr is fixing. |
node 14.17.0 no longer works due to isaacs/minipass@1270e6a BREAKING CHANGE: `ssri` is now compatible with the following semver range for node: `^16.13.0 || >=18.0.0`
f39e29a
to
4f02df0
Compare
4f02df0
to
70f9d7d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not 100% sure if BREAKING CHANGE:
can be at the end of the footer .. the spec is fuzzy. We can try this if you want, it's easy enough to fix w/ a force push.
<!-- What / Why --> <!-- Describe the request in detail. What it does and why it's being changed. --> A breaking change footer like the one below is over 100 characters, resulting in commitlint CI failures. ``` BREAKING CHANGE: `ssri` is now compatible with the following semver range for node: `^16.13.0 || >=18.0.0` ``` ## References <!-- Examples: Related to #0 Depends on #0 Blocked by #0 Fixes #0 Closes #0 --> Example CI failure: https://github.com/npm/ssri/actions/runs/10169599799/job/28126863705#step:7:12 Associated PR: npm/ssri#137
<!-- What / Why --> <!-- Describe the request in detail. What it does and why it's being changed. --> Our breaking change footers related to engine changes are often >100 characters, resulting in commitlint CI failures. <!-- Examples: Related to #0 Depends on #0 Blocked by #0 Fixes #0 Closes #0 --> Example CI failure: https://github.com/npm/ssri/actions/runs/10169599799/job/28126863705#step:7:12 Associated PR: npm/ssri#137
node 14.17.0 no longer works due to
node
prefixes being added in isaacs/minipass@1270e6aReferences
node 14.17.0 build break: https://github.com/npm/ssri/actions/runs/10049925593/job/27776871923