Repository navigation
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 2 Skipped Deployments
|
This branch was successfully deployed
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.
Draft: the separate code-only fix #1123 merged normally as
547c4ecbf3f7f7bf5662ed78522fbe8f6fe0b522. This proposal preserves the earlier genuine capture, while fresh corrected-main capture, review and service checks remain required before admission. It is not trusted-main or publication authority.Global release arbitration is blocked when
create-b4-app@0.15.5lacks its keyed publish bundle. This admits the exact historical completion record allowed by the reviewed policy, captured through the normal collector from merged controller5ce2bfd2baba81b1c5ae28561bebcc2f7cab1fa2on 2026-10-28 at 16:39–16:41 UTC.The record authenticates the original successful publisher archive and independent audit. Two fresh sweeps, started 60 seconds apart, establish all 21 exact tarball identities, 20 complete ordinary verifications, and the affected package’s precise provenance-only shape. Both complete GitHub snapshots are retained; only the already approved download-counter differences are normalized for comparison. The original verifier assertion remains distinct from fresh keyed-signature proof.
This PR contains ten byte-identical captured files, ten derived data pins, the pin-file checksum, and three exact existing-schema frozen-evidence brand entries. All 94 existing pins and every other brand entry remain unchanged. Ordinary 0.15.7 verification still requires full proof for all packages.
Validation: independent capture-evidence and admission-scope reviews passed; strict family discovery, binary archive authentication, byte/mode/hash comparisons and twelve independent data-family tests passed. The unchanged brand gate reproduced the three exact failures before the required entries were added and now passes all fifteen tests. Local
pnpm ci:validatepassed integrity, lint, build-cache, build and typecheck, then failed on six original 5-second timeouts in unchanged Vercel/filesystem tests. Both complete files subsequently passed sequentially at their original limits (133 and 8 tests); all three supplementary suites passed. The failed full-run evidence is retained and no full local pass is claimed. Normal CI, native Vercel, CopilotKit and the immediate fresh premerge service/global checks must pass before merge.Record SHA-256:
33e0c76cb15a5ddebe5da958d0b31d8b8630fa64fa30b0a015a6fa53b84b8857.