Skip to content

🔖 Prepare v0.14.0 release - #1097

Merged
taras merged 2 commits into
mainfrom
codex/release-0.13.2
Nov 4, 2026
Merged

taras merged 2 commits into
mainfrom
codex/release-0.13.2

Conversation

@taras

@taras taras commented Nov 4, 2026 •

Copy link
Copy Markdown
Owner

Why

This release adds capabilities across REPL execution, imports, diagnostics, permissions and workflow support. Taras selected the minor version 0.14.0 rather than the previous rolling-draft patch suggestion.

What changes

Stamp all eleven publishable packages to 0.14.0 in their Deno and npm manifests, and their eleven bun.lock workspace records. Relative to main, the patch contains only 33 version replacements across 23 files. Private packages, dependency ranges and release configuration retain their existing values.

How to verify it

deno task test scripts/tests/bump-version.test.ts scripts/tests/version-lockstep.test.ts passes four groups with 21 steps on the updated source, including actual workspace lockstep. The same independent Fable reviewer passed exact signed head af85d6f88e24108d9817b34087ffd46d81e71b44. The unchanged schema accepted its 694-character summary without an exception; all three observations are nonblocking. Required exact-head branch CI and exact-current-main health remain merge gates.

The prior 0.13.2 commit 959e8c8 received PASS for both clauses with two nonblocking observations. Its original 1,234-character summary is preserved under Taras’s specific one-time 1,200-character-limit exception. This is historical evidence for that commit; the new version receives its own review and checks.

Release preparation

The corpus measurement required after recent test additions is running separately on green main 8639637: https://github.com/taras/executable.md/actions/runs/41751371601. No measurement artifact or timing result is claimed yet. All eleven package names already exist on npm and JSR. After preparation and required checks, publish the rolling draft as v0.14.0 from verified main using the documented release process. Registry environment approval remains a human gate.

Scope confirmation

  • Every changed file supplies the release version.
  • No source, dependency range, workflow or generated artifact changes.
  • Mechanical changes come from deno task bump 0.14.0 and workspace-only bun.lock restamping.
  • Description reflects the current diff and available evidence.

@github-actions

github-actions Bot commented Nov 4, 2026

Copy link
Copy Markdown

PR #1097: 🔖 Prepare v0.13.2 release

23 files, +33 / -33

Scope

🟡 23 files changed. Are all changes related?

🟡 Changes span 12 directories.

🟡 PR mixes config and source changes.

Structural

✅ No structural bloat detected.

Slop

✅ Slop indicators look low.

Static Analysis

✅ Oxlint found no issues.

Correctness

No extraneous code patterns detected.

@taras taras changed the title 🔖 Prepare v0.13.2 release 🔖 Prepare v0.14.0 release Nov 4, 2026

@taras taras left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Independent Fable review — PASS

Reviewed commit af85d6f88e24108d9817b34087ffd46d81e71b44 using Claude / requested model fable, high effort, in the same independent conversation as the prior version-only review. Both acceptance clauses passed: version lockstep and release-source consistency. The unchanged review schema accepted this response; no length exception or response retry applies to this head.

Reviewed af85d6f (parent 959e8c8, green main 8639637) in place; checkout clean before and after. The commit is 33 single-line edits in 23 files, every one 0.13.2 -> 0.14.0, and the cumulative diff from 8639637 is likewise version-only in the same 23 files. The 11 publishable members (per spec §2 and scripts/lib/publishable-members.ts) declare 0.14.0 in deno.json, package.json and their bun.lock entries; test-support stays private at 0.0.0 and site is not a member. No dependency or non-version line changed. Consumers (cli.ts XMD_VERSION, release.yml and publish-packages.yml gates) are untouched. Focused lockstep and membership tests passed (4 suites, 18 steps). No blocking findings.

Nonblocking observations

  • Pre-existing, not in the acceptance clauses and not a release consumer: site/routes/index.tsx:37 hardcodes const VERSION = "v0.13.1", rendered as the eyebrow label (line 787) and the text of a link to the GitHub releases page (line 378). The bump task and spec §2 deliberately touch only manifests and bun.lock, the tag gates and binary never read this constant, and the site deploys separately (deploy.yml on site/** pushes), so correctness of v0.14.0 is unaffected. It was already stale at 0.13.2 and will advertise v0.13.1 after 0.14.0 ships; site/static/install.sh is unaffected because it resolves releases/latest at run time. Worth a separate follow-up, not a change to this commit.

  • Retained from the 959e8c8 review, pre-existing and unchanged here: scripts/lib/bump-version.ts selects members by deno.json name under @executablemd without the package.json private exclusion that scripts/lib/publishable-members.ts and both tag gates apply. The sets coincide because the only private member (packages/test-support) has no deno.json, so this bump stamped exactly the 11 publishable members. No action needed for this release.

  • Retained observation: the exec test corpus measurement and CI status on 8639637 are separate mechanical work outside this review; per AGENTS.md review boundaries CI is neither positive nor negative evidence, and nothing in this commit depends on it.

The original 959e8c8 review and its human-approved length exception remain historical evidence for that earlier commit. This review covers the new minor-version head. Required branch CI and exact-current-main health remain merge gates.

@taras
taras merged commit 32b53ab into main Nov 4, 2026
57 checks passed
@taras
taras deleted the codex/release-0.13.2 branch November 4, 2026 01:23
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