Repository navigation
fix!: do not switch to git+ssh for https repository links - #434
Merged
Merged
Conversation
wraithgar
changed the title
When the URL explicitly contains https, do not try to switch to ssh. This change is necessary for [npm][3] to retain the protocol, please see the link and the referenced issues [here][1] and [here][2] reporting problems when using ssh instead of requested https. [1]: npm/cli#2610 [2]: npm/cli#4305 [3]: npm/cli#8703 Signed-off-by: Oldřich Jedlička <[email protected]>
oldium
force-pushed
the
fix/git-https
branch
from
November 22, 2025 21:44
a200ae9 to
37f4bf5
Compare
Contributor
Author
|
Rebased to latest main |
Contributor
|
This kind of change is one that is likely going to need to be a semver major one, out of an abundance of caution. It looks good as-is, but historically this kind of change is pretty disruptive in places we don't expect. We will keep this PR open, and I have added it to the future changes tracking issue |
This was referenced Feb 24, 2026
Closed
owlstronaut
changed the title
owlstronaut
approved these changes
Apr 29, 2026
Merged
owlstronaut
pushed a commit
that referenced
this pull request
Jun 15, 2026
🤖 I have created a release *beep* *boop* --- ## [22.0.0](v21.5.0...v22.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 * [`09316f5`](09316f5) [#504](#504) bump to new node engine range (@owlstronaut) * [`2ab74b0`](2ab74b0) [#497](#497) strip patchedDependencies from the packed package.json (#497) (@manzoorwanijk) * [`66e7ea7`](66e7ea7) [#487](#487) forward globalIgnoreFile option to npm-packlist (@ljharb) ### Bug Fixes * [`ce804fb`](ce804fb) [#498](#498) avoid ReDoS in addGitSha committish stripping (#498) (@owlstronaut) * [`1f5f131`](1f5f131) [#494](#494) pass --global=false when preparing git dependencies (@owlstronaut) * [`e0af7f6`](e0af7f6) [#486](#486) respect ignoreScripts option for git dependencies (@owlstronaut) * [`12c8c8f`](12c8c8f) [#481](#481) fall back to git clone when tarball response is not a valid archive (@babyhuey) * [`61f065a`](61f065a) [#481](#481) use statusCode instead of constructor name for tarball fallback in git fetcher (@j1mb0-1) * [`6d160c1`](6d160c1) [#434](#434) do not switch to git+ssh for https repository links (#434) (@oldium) ### Dependencies * [`371e8b0`](371e8b0) [#504](#504) `[email protected]` * [`b68c6c2`](b68c6c2) [#504](#504) `[email protected]` * [`57793ab`](57793ab) [#504](#504) `[email protected]` * [`33eacc9`](33eacc9) [#504](#504) `[email protected]` * [`a131916`](a131916) [#504](#504) `[email protected]` * [`2b03527`](2b03527) [#504](#504) `[email protected]` * [`5f8ad42`](5f8ad42) [#504](#504) `[email protected]` * [`ee3b96d`](ee3b96d) [#504](#504) `[email protected]` * [`033f655`](033f655) [#504](#504) `@npmcli/[email protected]` * [`ddcc738`](ddcc738) [#504](#504) `@npmcli/[email protected]` * [`6a28eb2`](6a28eb2) [#504](#504) `@npmcli/[email protected]` * [`5879416`](5879416) [#504](#504) `@npmcli/[email protected]` * [`41ea727`](41ea727) [#504](#504) `@npmcli/[email protected]` ### Chores * [`3fc5fd4`](3fc5fd4) [#504](#504) `@npmcli/[email protected]` (@owlstronaut) * [`7350ab8`](7350ab8) [#504](#504) `[email protected]` (@owlstronaut) * [`c7c7d7f`](c7c7d7f) [#504](#504) template-oss-apply (@owlstronaut) * [`e9ac85e`](e9ac85e) [#501](#501) template-oss-apply (@owlstronaut) * [`e184356`](e184356) [#501](#501) `[email protected]` (@owlstronaut) * [`644ebb6`](644ebb6) [#479](#479) template-oss-apply (@owlstronaut) * [`ee64bea`](ee64bea) [#479](#479) `@npmcli/[email protected]` (@owlstronaut) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
owlstronaut
pushed a commit
to npm/cli
that referenced
this pull request
Jun 19, 2026
This prevents changing URLs from `https` and `git+https` into `git+ssh`, but keeps the fall-back to `git+ssh` when the protocol is not specified. The change in [pacote](npm/pacote#434) is necessary in order to have this fully working. ## References Supersedes #5256 Blocked by npm/pacote#434 Fixes #4305 Fixes #2610 Signed-off-by: Oldřich Jedlička <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
BREAKING CHANGE: git specs using the
httpsorgit+httpsprotocol now resolve togit+httpsURLs instead of being switched togit+ssh. Shortcut specs (e.g.github:user/repo,user/repo) andgit+ssh/git://specs are unchanged.When the URL explicitly contains https, do not try to switch to ssh. This change is necessary for npm to retain the protocol, please see the link and the referenced issues here and here reporting problems when using ssh instead of requested https.
References
Relates to npm/cli#8703