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 6.0.0 #209

Merged
merged 1 commit into from
Sep 25, 2024
Merged

chore: release 6.0.0 #209

merged 1 commit into from
Sep 25, 2024

Conversation

github-actions[bot]
Copy link
Contributor

🤖 I have created a release beep boop

6.0.0 (2024-09-24)

⚠️ BREAKING CHANGES

  • write-file-atomic 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 24, 2024

Release Manager

Release workflow run: https://github.com/npm/write-file-atomic/actions/runs/11022376466

Release Checklist for v6.0.0

  • 1. Approve this PR

    gh pr review 209 -R npm/write-file-atomic --approve
  • 2. Merge release PR 🚨 Merging this will auto publish 🚨

    gh pr merge 209 -R npm/write-file-atomic --squash
  • 3. 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/write-file-atomic $(gh run list -R npm/write-file-atomic -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 7d76ab9 to f17885e Compare September 24, 2024 21:44
@reggi reggi merged commit 9fcd402 into main Sep 25, 2024
12 checks passed
@reggi reggi deleted the release-please--branches--main branch September 25, 2024 17:34
Copy link
Contributor Author

🤖 Created releases:

Copy link
Contributor Author

github-actions bot commented Sep 25, 2024

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.

1 participant