Skip to content

chore: release 22.0.0#480

Merged
owlstronaut merged 1 commit into
mainfrom
release-please--branches--main
Jun 15, 2026
Merged

chore: release 22.0.0#480
owlstronaut merged 1 commit into
mainfrom
release-please--branches--main

Conversation

@github-actions

@github-actions github-actions Bot commented Apr 29, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

22.0.0 (2026-06-15)

⚠️ BREAKING CHANGES

  • pacote now supports node ^22.22.2 || ^24.15.0 || >=26.0.0
  • git specs using the https or git+https protocol now resolve to git+https URLs instead of being switched to git+ssh. Shortcut specs (e.g. github:user/repo, user/repo) and git+ssh/git:// specs are unchanged.

Features

Bug Fixes

Dependencies

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 April 29, 2026 18:02
@github-actions

github-actions Bot commented Apr 29, 2026

Copy link
Copy Markdown
Contributor Author

Release Manager

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

Release Checklist for v22.0.0

  • 1. Approve this PR

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

    gh pr merge 480 -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")

@owlstronaut owlstronaut mentioned this pull request Apr 29, 2026
2 tasks
@github-actions
github-actions Bot force-pushed the release-please--branches--main branch 3 times, most recently from 0a86511 to 73e0ae8 Compare May 1, 2026 15:26
@github-actions
github-actions Bot force-pushed the release-please--branches--main branch 2 times, most recently from 691e0f4 to a6c5cce Compare May 12, 2026 16:23
@github-actions
github-actions Bot force-pushed the release-please--branches--main branch 4 times, most recently from bd783f7 to 07147f0 Compare May 26, 2026 21:26
@rakrsh rakrsh mentioned this pull request Jun 1, 2026
@github-actions
github-actions Bot force-pushed the release-please--branches--main branch 6 times, most recently from a5220de to 7ad6820 Compare June 9, 2026 15:38
@manzoorwanijk

Copy link
Copy Markdown
Contributor

I thought this release would happen yesterday (Wednesday). 😄

@github-actions
github-actions Bot force-pushed the release-please--branches--main branch from 7ad6820 to 6feacc9 Compare June 15, 2026 20:06
@github-actions
github-actions Bot force-pushed the release-please--branches--main branch from 6feacc9 to 85e3c43 Compare June 15, 2026 20:07
@owlstronaut

Copy link
Copy Markdown

I thought this release would happen yesterday (Wednesday). 😄

I was waiting for upstream engine bumps :D It is happening now!

@owlstronaut
owlstronaut merged commit e4e44c5 into main Jun 15, 2026
30 checks passed
@owlstronaut
owlstronaut deleted the release-please--branches--main branch June 15, 2026 20:10
@github-actions

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

@github-actions

github-actions Bot commented Jun 15, 2026

Copy link
Copy Markdown
Contributor Author

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.

2 participants