Skip to content

🔖 Bump workspace packages to 0.8.1 - #476

Merged
taras merged 1 commit into
mainfrom
release/0.8.1
Aug 18, 2026
Merged

taras merged 1 commit into
mainfrom
release/0.8.1

Conversation

@taras

@taras taras commented Aug 18, 2026

Copy link
Copy Markdown
Owner

Why

0.8.0 published to npm but only partly to JSR: @executablemd/workflow was
rejected for having no license, which aborted the workspace publish and skipped
@executablemd/cli with it. #473 fixed that, but the gap cannot be closed by
re-running 0.8.0's jobs
— v0.8.0 points at f3d777d, which predates the fix,
and the jsr job checks out the tag's own commit with a bare actions/checkout.
A re-run rebuilds the unfixed tree and fails identically.

Cutting 0.8.1 from main is the documented path (§2) and the only one that
publishes the two missing packages with provenance.

What changes

Before: manifests declare 0.8.0; JSR carries eight of ten packages at it.
After: every @executablemd manifest declares 0.8.1, so publishing the draft
release as v0.8.1 passes both workflows' tag guards and publishes all ten to
both registries.

Scope

Included

  • version in each member's deno.json and package.json (20 files)
  • the matching workspace entries in bun.lock, which deno task bump does not
    touch and bun install will not restamp (§2)

Intentionally unchanged

  • packages/test-support stays at 0.0.0 — private, and outside the lockstep.
  • pnpm-lock.yaml and deno.lock record no @executablemd version, so neither
    needed restamping.
  • .github/workflows/publish-packages.yml — regenerated and byte-identical, as
    membership did not change.

Generated or mechanical changes

  • Every file here is a version stamp. There is no behavior change; xmd --version reports 0.8.1 because packages/cli/src/cli.ts reads it from the
    manifest.

How to verify it

deno run -A packages/cli/src/deno.ts --version        # 0.8.1
deno test -A scripts/tests/bump-version.test.ts \
             scripts/tests/publish-workflow-generator.test.ts \
             scripts/tests/publish-workflow-membership.test.ts
deno task check:jsr

Risks and limitations

  • 0.8.0 stays as it is on both registries: npm keeps all ten, JSR keeps the
    eight it accepted. Nothing is unpublished or moved.
  • Recovery: none needed — until the draft release is published as v0.8.1,
    this changes nothing outside the repository.

Scope confirmation

  • Every changed file supports the purpose described above.
  • Unrelated cleanup and formatting changes are excluded.
  • Generated or mechanical changes are clearly identified.
  • The description matches the final diff and test results.

0.8.0's JSR half cannot be recovered by re-running its jobs: tag v0.8.0
points at f3d777d, which predates the license fix in #473, and the jsr job
checks out the tag's own commit. npm carries all ten packages at 0.8.0;
JSR is missing @executablemd/workflow and @executablemd/cli.

Stamps every @executablemd manifest and restamps the matching workspace
entries in bun.lock, which the bump task does not touch (release spec §2).
packages/test-support stays at 0.0.0 — it is private and outside the
lockstep.
@github-actions

Copy link
Copy Markdown

PR #476: 🔖 Bump workspace packages to 0.8.1

21 files, +30 / -30

Scope

🟡 21 files changed. Are all changes related?

🟡 Changes span 11 directories.

🟡 PR mixes config and source changes.

🟡 package.json changed without dependency justification.

Structural

✅ No structural bloat detected.

Slop

✅ Slop indicators look low.

Static Analysis

✅ Oxlint found no issues.

Correctness

No extraneous code patterns detected.

@taras
taras enabled auto-merge (squash) August 18, 2026 03:36
@taras
taras merged commit 351282d into main Aug 18, 2026
16 checks passed
@taras
taras deleted the release/0.8.1 branch August 18, 2026 03:45
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