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

chore: release 4.0.0 #87

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Sep 3, 2024

🤖 I have created a release beep boop

4.0.0 (2024-09-03)

⚠️ BREAKING CHANGES

  • @npmcli/node-gyp now supports node ^18.17.0 || >=20.5.0

Bug Fixes

Chores


This PR was generated with Release Please. See documentation.

Copy link
Contributor Author

github-actions bot commented Sep 3, 2024

Release Manager

Release workflow run: https://github.com/npm/node-gyp/actions/runs/10687824654

Release Checklist for v4.0.0

  • 1. Checkout the release branch and test

    gh pr checkout 87 --force
    npm update
    npm test
    gh pr checks 87 -R npm/node-gyp --watch
  • 2. Publish

    npm publish --tag=latest
  • 3. Merge release PR

    gh pr merge 87 -R npm/node-gyp --squash
    git checkout main
    git fetch
    git reset --hard origin/main
  • 4. Check For Release Tags

    Release Please will run on the just pushed release commit and create GitHub releases and tags for each package.

    gh run watch -R npm/node-gyp $(gh run list -R npm/node-gyp -w release -b main -L 1 --json databaseId -q ".[0].databaseId")

@github-actions github-actions bot force-pushed the release-please--branches--main branch from 849d5d8 to 7dbb3a4 Compare September 3, 2024 17:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants