Skip to content

Conversation

@github-actions
Copy link
Contributor

🤖 I have created a release beep boop

21.3.1 (2026-02-10)

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 February 10, 2026 18:56
@github-actions
Copy link
Contributor Author

github-actions bot commented Feb 10, 2026

Release Manager

Release workflow run: https://github.com/npm/pacote/actions/runs/21878322219

Release Checklist for v21.3.1

  • 1. Approve this PR

    gh pr review 448 -R npm/pacote --approve
  • 2. Merge release PR 🚨 Merging this will auto publish 🚨

    gh pr merge 448 -R npm/pacote --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/pacote $(gh run list -R npm/pacote --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 0e79641 to 765f96a Compare February 10, 2026 18:57
@wraithgar wraithgar merged commit 18d36e6 into main Feb 10, 2026
10 checks passed
@wraithgar wraithgar deleted the release-please--branches--main branch February 10, 2026 19:23
@github-actions
Copy link
Contributor Author

🤖 Created releases:

🌻

@github-actions
Copy link
Contributor Author

github-actions bot commented Feb 10, 2026

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