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.

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

Merged
merged 2 commits into from
Jul 30, 2024

Conversation

hashtagchris
Copy link
Contributor

node 14.17.0 no longer works due to node prefixes being added in isaacs/minipass@1270e6a

References

node 14.17.0 build break: https://github.com/npm/ssri/actions/runs/10049925593/job/27776871923

@hashtagchris hashtagchris requested a review from a team as a code owner July 30, 2024 20:17
@wraithgar wraithgar changed the title fix!: Address breaking engine change in dependency Address breaking engine change in dependency Jul 30, 2024
@wraithgar
Copy link
Member

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.

package.json Outdated Show resolved Hide resolved
@wraithgar
Copy link
Member

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`
@hashtagchris hashtagchris force-pushed the hashtagchris-node-prefix branch from f39e29a to 4f02df0 Compare July 30, 2024 20:51
@hashtagchris hashtagchris force-pushed the hashtagchris-node-prefix branch from 4f02df0 to 70f9d7d Compare July 30, 2024 20:54
@hashtagchris hashtagchris requested a review from wraithgar July 30, 2024 21:03
Copy link
Member

@wraithgar wraithgar left a 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.

@hashtagchris hashtagchris merged commit 0fa3964 into main Jul 30, 2024
22 of 23 checks passed
@hashtagchris hashtagchris deleted the hashtagchris-node-prefix branch July 30, 2024 22:15
@github-actions github-actions bot mentioned this pull request Jul 30, 2024
hashtagchris added a commit to npm/template-oss that referenced this pull request Aug 5, 2024
<!-- 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
hashtagchris added a commit to npm/template-oss that referenced this pull request Aug 5, 2024
<!-- 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants