Skip to content

Conversation

@github-actions
Copy link
Contributor

🤖 I have created a release beep boop

7.0.0 (2025-10-22)

⚠️ BREAKING CHANGES

  • write-file-atomic now supports node ^20.17.0 || >=22.9.0

Bug Fixes

Chores


This PR was generated with Release Please. See documentation.

@github-actions github-actions bot requested a review from a team as a code owner October 22, 2025 15:15
@github-actions
Copy link
Contributor Author

github-actions bot commented Oct 22, 2025

Release Manager

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

Release Checklist for v7.0.0

  • 1. Approve this PR

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

    gh pr merge 220 -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 --workspace release -b main -L 1 --json databaseId -q ".[0].databaseId")

@github-actions github-actions bot force-pushed the release-please--branches--main branch from 511349d to f0d2a7d Compare October 22, 2025 15:17
@owlstronaut owlstronaut merged commit 2d6070a into main Oct 22, 2025
13 checks passed
@owlstronaut owlstronaut deleted the release-please--branches--main branch October 22, 2025 15:23
@github-actions
Copy link
Contributor Author

🤖 Created releases:

🌻

@github-actions
Copy link
Contributor Author

github-actions bot commented Oct 22, 2025

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