Carry the documentation corrections to npm and the site - #20
Merged
Merged
Conversation
The hook already rejected a bare `0.0.1-beta.3`, with a comment about how a version number lands on every file the release touched. One word in front slips past it: `Release 0.0.2-beta.2` did exactly what the bare version would have done, on twelve files, and cannot be reworded now — the tag points at it and this project does not rewrite published history. The integrations table and the distribution table now say where each thing can be got, rather than pairing that with where it cannot. And the roadmap entry describing jsray-vscode and jsray-terminal as unpublished, bundling Core 0.0.1-beta.5, has been overtaken on every count.
A registry page is frozen per version and the site is built from main, so neither learns a correction except by releasing one. This release exists to deliver the ones written since beta.2, and it changes no runtime behaviour: dist/ differs only in the version string it reports. It also closes the gap that produced the previous release's subject. The commit-msg hook refused a bare version number but not a version with one word in front, and it only ever ran on a machine that had configured core.hooksPath — so CI now runs the same file against every commit a pull request adds.
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
jsray | b5e1f92 | Commit Preview URL Branch Preview URL |
Sep 05 2026, 04:21 PM |
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.
Release 0.0.2-beta.3. Documentation and the guards around it; no runtime change.
Also adds the CI job that runs
tools/hooks/commit-msgagainst every commit a pull request adds — this pull request is the first thing it checks.