Repository navigation
fix(lastcode): validate checkpoint lint before publish - #120
Merged
Merged
Conversation
Loading
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.
The nightly checkpoint smoke gate did not run the repository format-and-lint check, so checkpoint 1211 was advertised as installable even though the local update later failed on mobile custom-theme lint.
This preserves the existing mobile notice colors with generated adaptive theme tokens and changes checkpoint smoke validation to run
vp check, so the same class of formatting or lint failure blocks publication.Validation: focused format/lint, 85 focused tests, scripts and mobile typechecks, and exact-head Quick CI against
lastcode/main.Built with GPT-5.6-sol through the Codex harness.