Skip to content

Conversation

@github-actions
Copy link
Contributor

🤖 I have created a release beep boop

7.0.0 (2025-10-22)

⚠️ BREAKING CHANGES

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:19
@github-actions
Copy link
Contributor Author

github-actions bot commented Oct 22, 2025

Release Manager

Release workflow run: https://github.com/npm/validate-npm-package-name/actions/runs/18721091108

Release Checklist for v7.0.0

  • 1. Approve this PR

    gh pr review 148 -R npm/validate-npm-package-name --approve
  • 2. Merge release PR 🚨 Merging this will auto publish 🚨

    gh pr merge 148 -R npm/validate-npm-package-name --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/validate-npm-package-name $(gh run list -R npm/validate-npm-package-name --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 bb8a877 to a45d178 Compare October 22, 2025 15:20
@owlstronaut owlstronaut merged commit 1307824 into main Oct 22, 2025
14 checks passed
@owlstronaut owlstronaut deleted the release-please--branches--main branch October 22, 2025 15:26
@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

1 participant