Skip to content

chore: use https repository metadata - #3

Open
snkk2x-collab wants to merge 1 commit into
josestg:masterfrom
snkk2x-collab:codex/https-repository-metadata
Open

chore: use https repository metadata#3
snkk2x-collab wants to merge 1 commit into
josestg:masterfrom
snkk2x-collab:codex/https-repository-metadata

Conversation

@snkk2x-collab

Copy link
Copy Markdown

Summary

  • Update the package repository metadata from the SSH GitHub form to a public HTTPS URL.
  • Leave runtime code, dependencies, package version, entrypoints, type declarations, and lockfile unchanged.

Rationale

This repository is public, so npm consumers should be able to follow the source repository link without SSH or GitHub key setup.

Validation

  • node -e "const p=require('./package.json'); if (p.repository !== 'git+https://github.com/josestg/rehype-code-title.git') throw new Error(JSON.stringify(p.repository)); console.log(p.repository)"
  • git diff --check
  • git ls-remote https://github.com/josestg/rehype-code-title.git HEAD
  • pnpm install --ignore-scripts --lockfile=false
  • pnpm test
  • pnpm pack --dry-run

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant