The parser pin takes v0.20.0, and says so on purpose - #171
Merged
Conversation
The pin named v0.17.0 while the release that ships the instance checks is v0.20.0, and a pin that is behind is intent until it is moved — so leaving it said this site meant v0.17.0. It did not; it was two releases behind because the branch that would have moved it to v0.19.0 was superseded before it landed. Nothing observable changes. lib/instance.mjs is the same blob at v0.17.0, v0.19.0 and v0.20.0, so model.json rebuilds byte for byte and model:check passes without a rebuild being needed at all. What moves is the lockfile's resolved commit, now the one v0.20.0 sits on. Verified: model:check, pages:check, pin:check, design:check, test:build, test:dupes, test:og, og:check and verify all pass, the last two against a served copy; conventions-check passes. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
The pin named v0.17.0 while the release that ships the instance checks is v0.20.0. A pin that is behind is intent until it is moved, so leaving it said this site meant v0.17.0 — it did not. It was two releases behind because #169, which would have moved it to v0.19.0, was superseded by #170 and closed.
Nothing observable changes.
lib/instance.mjsis the same blob4a50f24de862at v0.17.0, v0.19.0 and v0.20.0, somodel.jsonrebuilds byte for byte andmodel:checkpasses with no rebuild in this diff at all. What moves is the lockfile's resolved commit, noweab533a, which is where v0.20.0 sits.Verified: model:check, pages:check, pin:check, design:check, test:build, test:dupes, test:og, og:check and verify all pass, the last two against a served copy; conventions-check passes.
🤖 Generated with Claude Code