Point the SCM URLs at HTTPS - #595
Merged
Merged
Conversation
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
1 participant
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.
connectionis meant to be the anonymous, read-only URL, and both it anddeveloperConnectionhere arethe scp-like SSH form. That makes a release depend on the releaser having an SSH key configured, and gives
anonymous consumers a URL they cannot use.
Every other component in the org uses the HTTPS URL, which works through the git credential helper. Same
change as codehaus-plexus/plexus-sec-dispatcher#142, where the SSH form was not merely inconvenient but
malformed and blocked the release outright.
This change was created with AI assistance.