chore: sync the StackBlitz live lab to 1.0.0-beta.10 - #64
Merged
Merged
Conversation
Required immediately after publication, not before the next release. verify:stackblitz queries the registry, so the predecessor gap closed the moment beta.10 appeared on npm and every branch run now fails until this lands: The live lab pins [email protected], but [email protected] is already published on npm. That gate is doing what it was added for. Before it existed, beta.9 shipped and the lab silently served beta.8 for four days while CI stayed green. Regenerated the standalone lockfile; the lab is excluded from the workspace and carries its own. The verifier resolved the published package and completed a real development transform, source map, and clean production build against it, which also covers the runbook's clean-consumer check. Co-Authored-By: Claude Opus 5 <[email protected]>
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
1 participant
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.
Post-release synchronization for
v1.0.0-beta.10, required immediately rather than before the next release.Why now
verify:stackblitzqueries the registry, so the one-version predecessor gap closed the moment beta.10 appeared on npm. Every branch and pull-request run fails until this lands:That gate is #59 doing exactly what it was added for. Before it existed, beta.9 shipped and the public lab silently served beta.8 for four days while CI stayed green — the drift was only found during launch preparation.
Change
Bumped the pin and regenerated the standalone lockfile. The lab is excluded from the workspace (
!examples/stackblitz) so it carries its own.Verification
pnpm verify:stackblitznow resolves the published package and completes a real development transform, source map, and clean production build against it:That also covers the runbook's clean-consumer check — installing the exact published version into a TypeScript + Vite project and exercising both a dev transform and a production build.
pnpm verify:linkspasses.Release state for the record
[email protected], dist-tagbeta→1.0.0-beta.10.https://slsa.dev/provenance/v1).v1.0.0-beta.10on3ef48eb.🤖 Generated with Claude Code