Pin the site to v0.2.10 - #43
Merged
Merged
Conversation
The wasm module is the one the release built, checked against `deed-v0.2.10-checksums.txt` before it was committed, and the 0.2.9 one is gone rather than left beside it. Three scripts now carry the pin instead of two: the playground, the diagnostics page, and the agents page added last week. Each refuses to show anything if the module it loaded reports a different version than the page claims, so a half-finished pin is visible rather than quiet. The example corpus is re-taken from the tag. Nothing in it changed between 0.2.9 and 0.2.10, so only the index's version field moved. `node tools/check.mjs`: 72 files, every link resolves, and v0.2.10 loaded and answered about all 29 examples.
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 playground, the diagnostics page and the agents page all run the compiler
in the reader's tab, so pinning is swapping one vendored module for another and
moving every version string that names it.
The module is the artefact
release.ymlbuilt for the tag, verified againstdeed-v0.2.10-checksums.txtbefore it was committed. The 0.2.9 module isremoved rather than left beside it, so there is one compiler on the site.
Each of the three scripts compares what the module reports to what the page
claims and shows an error instead of an answer when they differ, which is what
keeps a half-finished pin from reading as a working one.
The examples are re-taken from the tag. None of them changed between the two
releases; only the index's version field moved.
Gate:
node tools/check.mjs— 72 files, every link resolves, and v0.2.10loaded and answered about all 29 examples.