Repository navigation
chore(release): 0.7.0 - #413
Merged
Merged
Conversation
Bumps every shared version surface to 0.7.0 and writes the 0.7.0 changelog. Also updates the three version pins the checklist missed (wiki_mcp.md example JSON, mcp_test.ts, graph_cache_test.ts version + fingerprint hash) and names them in AGENTS.md. The merge publishes to JSR; the v0.7.0 tag publishes npm, PyPI, and the GitHub release.
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
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.
What
Bumps every release version surface from
0.6.0to0.7.0and writes the 0.7.0 changelog. This is a prep PR: it is not merged until a human says so, because the merge is itself a publish.Read this before merging
The merge is a publish.
publish-jsr.ymltriggers on theCIworkflow completing onmainand publishes whatever version is there (gated onJSR_PUBLISH_ENABLED=true). So merging this PR publishes@wazoo/wiki@0.7.0to JSR. Thev0.7.0tag is then the second half of the release:release.ymlbuilds the six standalone binaries and publishes the GitHub Release, npm, and PyPI. Two gates, not one.Version surfaces
All bumped together, and
tests/version_test.tspasses (5/5):package.json,package-lock.json(root andpackages[""]),deno.json,pyproject.toml,src/wiki/version.ts,docs/wiki/wiki.mdThree more places pin the version and are not generated, which the release checklist previously did not mention. All are updated here, and
AGENTS.md's Release workflow section now names them so the next release does not have to rediscover them via a red test run:docs/wiki/wiki_mcp.md— the staticexample shapeJSONtests/mcp_test.ts—description.versiontests/graph_cache_test.ts—manifest.versionand the manifest fingerprint hash (the manifest includesVERSION, so the pinned hash changes on every bump:430acc47…→fa71b23d…)Also in this release
docs/wiki/wiki_render.md— the SPARQL table'swikirow, regenerated withrender(thenfmt).Why 0.7.0
Two additive public features since 0.6.0:
buildThemedSitein@wazoo/wiki/theme(#409) andextraTokenson the layout renderers (#407). Minor bump for a pre-1.0 package, consistent with 0.3.0 → 0.6.0. The changelog also records thewiki file newheadline fix (#402) and the two documentation changes that landed with them (#401, #411).Verification
deno run -A src/wiki/cli.ts -c docs/wiki.yml fmt --check | lint --strict | check --strict | render --check→ all exit 0deno task fmt:check/deno task lint/deno task check→ exit 0deno run -A docs/build.ts --output-dir _site→ Built 111 pages; the site reportssoftwareVersion 0.7.0deno task test→ 569 passed, 1 ignored, 5 failed. The 5 aretests/verify_cli_test.ts(retired-Python-CLI-on-PATH and cutover-version cases) and fail identically on pristinemainhere; CI runs them green on a machine without that PATH entry.git grep 0.6.0over tracked files now matches only the## 0.6.0changelog history heading.Follow-on
After this publishes,
wiki-templatesbumps its pins (wazootech-wiki==0.7.0,jsr:@wazoo/wiki@0.7.0) and the wikipedia template moves ontobuildThemedSite, dropping its copy of the page loop (T5b).