Skip to content

test: vite-plus prerelease 0.0.0-commit.7ebf81e43af581194844e8fe18f65ed2eb544642 - #5

Draft
fengmk2 wants to merge 4 commits into
mainfrom
update-vite-plus-prerelease-test-0.0.0-commit.7ebf81e43af581194844e8fe18f65ed2eb544642
Draft

test: vite-plus prerelease 0.0.0-commit.7ebf81e43af581194844e8fe18f65ed2eb544642#5
fengmk2 wants to merge 4 commits into
mainfrom
update-vite-plus-prerelease-test-0.0.0-commit.7ebf81e43af581194844e8fe18f65ed2eb544642

Conversation

@fengmk2

@fengmk2 fengmk2 commented Aug 23, 2026

Copy link
Copy Markdown

Ecosystem-ci smoke test for vite-plus v0.3.0. Draft / do not merge.

Includes a test-branch-only commit exempting packages from pnpm's trustPolicy: no-downgrade: registry-bridge preview builds carry no provenance attestation (real npm releases do), plus one third-party cross-major false positive (pnpm/pnpm#10202).

aidenybai and others added 3 commits August 23, 2026 02:18
Ecosystem-ci smoke test only. Registry-bridge preview builds carry no provenance attestation, so no-downgrade rejects them. Real npm releases are published with provenance.
vite-plus 0.0.0-commit.7ebf81e43af581194844e8fe18f65ed2eb544642, via the ecosystem-ci smoke test.
@fengmk2 fengmk2 self-assigned this Aug 23, 2026
Publishing a preview package needs a GitHub App or token the fork does not have, and it does not exercise the pinned Vite+. The build steps still 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.

2 participants