Align repository URLs with the renamed GitHub repo#80
Merged
Conversation
- Point repository.url at vercel-labs/native in all eight platform packages so npm provenance validation passes (the v0.4.1 publish failed on the first package) - Guard in check-version-sync.js: platform repository.url and homepage must match the main package - Sweep remaining vercel-labs/zero-native links and zero-native.dev domains across docs, templates, and fixtures to the new canonical names
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![vercel[bot]](https://avatars.githubusercontent.com/in/8329?s=60&v=4){kind=small}
Railly
approved these changes
Jul 9, 2026
- version:sync now stamps repository and homepage from the main package into each platform package, making the check script's remediation hint accurate
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
2 participants
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.
Bug
The v0.4.1 Release run failed publishing the first package: npm rejects the publish because
repository.url(git+https://github.com/vercel-labs/zero-native.git) doesn't match the provenance repository (vercel-labs/native). #78 updated only the main CLI package; all eight platform packages undernpm/*/were missed. Nothing was published, so merging this retries the full 0.4.1 publish (Release runs on every main push and skips already-published versions).Fix
repository.url→vercel-labs/nativeandhomepage→native-sdk.devin all eight platform packages (andhomepagein the main package)check-version-sync.jsnow asserts platformrepository.url/homepagematch the main package — the release workflow runs this before publishing, so a half-landed rename can't reach npm againvercel-labs/zero-nativelinks andzero-native.devdomains across README/CONTRIBUTING/RELEASING, docs site config (github star API, sitemap, robots), generated-CI templates, CEF download URL, and test fixturesLeft alone deliberately: CHANGELOG history, the eval-sandbox container image path (registry namespace, not a GitHub URL), and the
vercel linkproject name — the latter two flagged for follow-up.Verification
scripts:check,version:check("Versions in sync: 0.4.1"),npm pack --dry-runall passNote: the npm trusted-publisher config for the nine packages must point at repository
vercel-labs/nativepost-rename (RELEASING.md now says so).