Skip to content

chore: use public repository metadata#70

Closed
YfengJ wants to merge 1 commit into
BinaryMuse:masterfrom
YfengJ:codex/use-public-repository-metadata
Closed

chore: use public repository metadata#70
YfengJ wants to merge 1 commit into
BinaryMuse:masterfrom
YfengJ:codex/use-public-repository-metadata

Conversation

@YfengJ

@YfengJ YfengJ commented Jun 19, 2026

Copy link
Copy Markdown

Summary

  • update the package repository URL from git:// to git+https://
  • leave runtime code, dependencies, package version, entry points, types, license, and package contents unchanged

Validation

  • npm view toml --json
  • metadata assertion for package identity, entry points, types, license, and repository fields
  • npm ci --ignore-scripts --no-audit --no-fund
  • npm run build
  • npm test
  • npm pack --dry-run --ignore-scripts --json .
  • git diff --check

Note: npm run test:spec currently requires the external .binarymuse/toml-test fixture checkout and cannot run from a fresh clone without that data.

@YfengJ

YfengJ commented Jun 21, 2026

Copy link
Copy Markdown
Author

CI note: the failing Node 24 job appears unrelated to this metadata-only change. I reproduced the same npm run test:spec result on upstream master (3840fac) and on this branch: both fail only on the current external toml-test BOM cases, valid/utf8-bom-01 and valid/utf8-bom-02. The package local npm test suite passes, and this PR only changes the repository URL metadata.

@YfengJ YfengJ closed this by deleting the head repository Jun 26, 2026
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