Skip to content

Conversation

github-actions[bot]
Copy link
Contributor

🤖 I have created a release beep boop

19.0.0 (2025-07-24)

⚠️ BREAKING CHANGES

  • npm-registry-fetch now supports node ^20.17.0 || >=22.9.0

Bug Fixes

Dependencies

Chores


This PR was generated with Release Please. See documentation.

Copy link
Contributor Author

github-actions bot commented Jul 24, 2025

Release Manager

Release workflow run: https://github.com/npm/npm-registry-fetch/actions/runs/16505674133

Release Checklist for v19.0.0

  • 1. Approve this PR

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

    gh pr merge 278 -R npm/npm-registry-fetch --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/npm-registry-fetch $(gh run list -R npm/npm-registry-fetch --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 855d9e3 to c82a4db Compare July 24, 2025 19:10
@owlstronaut owlstronaut merged commit a50fb07 into main Jul 24, 2025
14 checks passed
@owlstronaut owlstronaut deleted the release-please--branches--main branch July 24, 2025 19:25
Copy link
Contributor Author

🤖 Created releases:

🌻

Copy link
Contributor Author

github-actions bot commented Jul 24, 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