[codex] Use HTTPS repository metadata - #335
Draft
xingdi614-alt wants to merge 1 commit into
Draft
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.
What changed
Updated the package repository URL from the SSH-only form to the public git+https form.
Why
The currently published npm metadata normalizes the source value to git+ssh, which can require GitHub SSH credentials in package tooling and automation. The HTTPS URL remains cloneable without SSH configuration.
This is metadata-only and does not change runtime code, dependencies, or the lockfile.
Validation
The complete yarn test run has one existing failure in src/tests/didkey.test.ts because its fixed JWT expired in December 2025; the failure is unrelated to this package metadata change.