ci: bump registry-bridge action to content-addressed tarball URLs#2100
Open
fengmk2 wants to merge 3 commits into
Open
ci: bump registry-bridge action to content-addressed tarball URLs#2100fengmk2 wants to merge 3 commits into
fengmk2 wants to merge 3 commits into
Conversation
Point the preview-build action at pkg-pr-registry-bridge#58 (a83d8aa), which uploads tarballs content-addressed (/-/tarball/<name>/<version>/<shasum>.tgz) and serves dist.tarball as /tarballs/<name>/<version>/<shasum>.tgz. This fixes the ERR_PNPM_TARBALL_INTEGRITY a non-byte-reproducible rebuild of the same commit could cause: each build gets its own URL, so a republish can never cross bytes and integrity. The bridge is already deployed; this activates the new upload path for preview builds.
✅ Deploy Preview for viteplus-preview canceled.
|
fengmk2
commented
Jul 8, 2026
Contributor
Registry bridge build (
|
| Package | Version |
|---|---|
vite-plus |
0.0.0-commit.eaddff82ebc2d119734e91bf72a40b696e21c329 |
@voidzero-dev/vite-plus-core |
0.0.0-commit.eaddff82ebc2d119734e91bf72a40b696e21c329 |
Install the Vite+ CLI built from this commit, then migrate a project:
# macOS / Linux
curl -fsSL https://vite.plus | VP_PR_VERSION=2100 bash# Windows (PowerShell)
$env:VP_PR_VERSION="2100"; irm https://vite.plus/ps1 | iexAfter installing, upgrade the current project's vite-plus to this test build with:
vp migrateOr point your package manager at the bridge registry https://registry-bridge.viteplus.dev/:
| Package manager | Registry config |
|---|---|
| npm / pnpm / Bun | .npmrc: registry=https://registry-bridge.viteplus.dev/ |
| Yarn (v2+) | .yarnrc.yml: npmRegistryServer: "https://registry-bridge.viteplus.dev/" |
Then pin the build (vite aliases to vite-plus-core; pnpm can use a catalog, npm an overrides entry):
{
"devDependencies": {
"vite-plus": "0.0.0-commit.eaddff82ebc2d119734e91bf72a40b696e21c329",
"vite": "npm:@voidzero-dev/vite-plus-core@0.0.0-commit.eaddff82ebc2d119734e91bf72a40b696e21c329"
}
}
Contributor
🐳 Docker preview imageBuilt from this PR's registry bridge build:
# remove any stale local copy from a previous run, then pull fresh
docker rmi ghcr.io/voidzero-dev/vite-plus:pr-2100 2>/dev/null; docker pull ghcr.io/voidzero-dev/vite-plus:pr-2100Quick check: docker run --rm ghcr.io/voidzero-dev/vite-plus:pr-2100 vp --versionSee docs/guide/docker.md for usage. |
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
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.
Points the
preview-buildaction at pkg-pr-registry-bridge#58 (a83d8aa, merged + deployed), which makes preview tarballs content-addressed:/-/tarball/<name>/<version>/<shasum>.tgzdist.tarball=/tarballs/<name>/<version>/<shasum>.tgzThis fixes the
ERR_PNPM_TARBALL_INTEGRITYa non-byte-reproducible rebuild of the same commit could cause: each build gets its own URL, so a republish can never cross bytes and integrity. The bridge is already deployed and back-compat (existing version-addressed previews still install via a revalidatable fallback), so this just activates the new upload path for future preview builds.Add the
preview-buildlabel to smoke-test a labeled build against the deployed bridge.