Skip to content

chore: use public repository metadata#6

Open
pqmashiro-commits wants to merge 1 commit into
mattdsteele:masterfrom
pqmashiro-commits:patch-1
Open

chore: use public repository metadata#6
pqmashiro-commits wants to merge 1 commit into
mattdsteele:masterfrom
pqmashiro-commits:patch-1

Conversation

@pqmashiro-commits

Copy link
Copy Markdown

Summary

  • Update repository.url from the legacy git:// protocol to a public HTTPS git URL.
  • Keep the change metadata-only: no runtime code, dependency, lockfile, package version, or build output changes.

Why

The published gulp-dart-sass@1.1.0 package metadata reports:

{
  "type": "git",
  "url": "git://github.com/mattdsteele/gulp-dart-sass.git"
}

The current source package.json has the same legacy transport, without the trailing .git:

{
  "type": "git",
  "url": "git://github.com/mattdsteele/gulp-dart-sass"
}

Using git+https://github.com/mattdsteele/gulp-dart-sass.git makes the package metadata easier to consume in environments where unauthenticated git:// traffic may be blocked or discouraged.

Contributing note

The contributing guide asks contributors to open an issue before a PR, but GitHub reports Issues are disabled for this repository (has_issues: false). I opened the PR directly because this is a small metadata-only cleanup.

I did not update CHANGELOG.md because this does not change package runtime behavior, dependencies, public API, or generated output.

Verification

node -e "const p=require('./package.json'); if (p.repository.url !== 'git+https://github.com/mattdsteele/gulp-dart-sass.git') { console.error(p.repository); process.exit(1) } console.log(p.name, p.version, p.repository.url)"
git diff --check
pnpm pack --dry-run --json

Observed metadata check output:

gulp-dart-sass 1.1.0 git+https://github.com/mattdsteele/gulp-dart-sass.git

pnpm pack --dry-run --json completed successfully. git diff --check reported no whitespace errors, aside from the normal Windows LF-to-CRLF working-copy warning.

Update repository.url from legacy git:// to git+https://.
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