Repository navigation
🔖 Bump workspace packages to 0.8.1 - #476
Merged
Merged
Conversation
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.
PR #476: 🔖 Bump workspace packages to 0.8.121 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. CorrectnessNo extraneous code patterns detected. |
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.
Why
0.8.0 published to npm but only partly to JSR:
@executablemd/workflowwasrejected for having no license, which aborted the workspace publish and skipped
@executablemd/cliwith it. #473 fixed that, but the gap cannot be closed byre-running 0.8.0's jobs —
v0.8.0points atf3d777d, which predates the fix,and the
jsrjob checks out the tag's own commit with a bareactions/checkout.A re-run rebuilds the unfixed tree and fails identically.
Cutting 0.8.1 from
mainis the documented path (§2) and the only one thatpublishes the two missing packages with provenance.
What changes
Before: manifests declare
0.8.0; JSR carries eight of ten packages at it.After: every
@executablemdmanifest declares0.8.1, so publishing the draftrelease as
v0.8.1passes both workflows' tag guards and publishes all ten toboth registries.
Scope
Included
versionin each member'sdeno.jsonandpackage.json(20 files)bun.lock, whichdeno task bumpdoes nottouch and
bun installwill not restamp (§2)Intentionally unchanged
packages/test-supportstays at0.0.0— private, and outside the lockstep.pnpm-lock.yamlanddeno.lockrecord no@executablemdversion, so neitherneeded restamping.
.github/workflows/publish-packages.yml— regenerated and byte-identical, asmembership did not change.
Generated or mechanical changes
xmd --versionreports0.8.1becausepackages/cli/src/cli.tsreads it from themanifest.
How to verify it
Risks and limitations
eight it accepted. Nothing is unpublished or moved.
v0.8.1,this changes nothing outside the repository.
Scope confirmation