chore: release 22.0.0

[github-actions]

🤖 I have created a release beep boop

22.0.0 (2026-05-26)

⚠️ BREAKING CHANGES

• 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

• 66e7ea7 #487 forward globalIgnoreFile option to npm-packlist (@ljharb)

Bug Fixes

• 1f5f131 #494 pass --global=false when preparing git dependencies (@owlstronaut)
• e0af7f6 #486 respect ignoreScripts option for git dependencies (@owlstronaut)
• 12c8c8f #481 fall back to git clone when tarball response is not a valid archive (@babyhuey)
• 61f065a #481 use statusCode instead of constructor name for tarball fallback in git fetcher (@j1mb0-1)
• 6d160c1 #434 do not switch to git+ssh for https repository links (fix!: do not switch to git+ssh for https repository links #434) (@oldium)

Chores

• 644ebb6 #479 template-oss-apply (@owlstronaut)
• ee64bea #479 @npmcli/template-oss@4.30.0 (@owlstronaut)

---

This PR was generated with Release Please. See documentation.

[github-actions]

Release Manager

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

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")