Skip to content

chore(release): 0.7.0 - #413

Merged
EthanThatOneKid merged 1 commit into
mainfrom
release-0.7.0
Oct 14, 2026
Merged

EthanThatOneKid merged 1 commit into
mainfrom
release-0.7.0

Conversation

@EthanThatOneKid

Copy link
Copy Markdown
Collaborator

What

Bumps every release version surface from 0.6.0 to 0.7.0 and 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.yml triggers on the CI workflow completing on main and publishes whatever version is there (gated on JSR_PUBLISH_ENABLED=true). So merging this PR publishes @wazoo/wiki@0.7.0 to JSR. The v0.7.0 tag is then the second half of the release: release.yml builds 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.ts passes (5/5):

  • package.json, package-lock.json (root and packages[""]), deno.json, pyproject.toml, src/wiki/version.ts, docs/wiki/wiki.md

Three 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 static example shape JSON
  • tests/mcp_test.ts — description.version
  • tests/graph_cache_test.ts — manifest.version and the manifest fingerprint hash (the manifest includes VERSION, so the pinned hash changes on every bump: 430acc47… → fa71b23d…)

Also in this release

  • docs/wiki/wiki_render.md — the SPARQL table's wiki row, regenerated with render (then fmt).

Why 0.7.0

Two additive public features since 0.6.0: buildThemedSite in @wazoo/wiki/theme (#409) and extraTokens on the layout renderers (#407). Minor bump for a pre-1.0 package, consistent with 0.3.0 → 0.6.0. The changelog also records the wiki file new headline 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 0
  • deno task fmt:check / deno task lint / deno task check → exit 0
  • deno run -A docs/build.ts --output-dir _site → Built 111 pages; the site reports softwareVersion 0.7.0
  • deno task test → 569 passed, 1 ignored, 5 failed. The 5 are tests/verify_cli_test.ts (retired-Python-CLI-on-PATH and cutover-version cases) and fail identically on pristine main here; CI runs them green on a machine without that PATH entry.
  • git grep 0.6.0 over tracked files now matches only the ## 0.6.0 changelog history heading.

Follow-on

After this publishes, wiki-templates bumps its pins (wazootech-wiki==0.7.0, jsr:@wazoo/wiki@0.7.0) and the wikipedia template moves onto buildThemedSite, dropping its copy of the page loop (T5b).

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.
@EthanThatOneKid
EthanThatOneKid merged commit a7074ee into main Oct 14, 2026
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant