chore(main): release 10.0.0-alpha - #3304
Merged
Merged
Conversation
orchestkit-release-bot
Bot
requested a review
from yonatangross
as a code owner
August 8, 2026 07:35
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
✅ CI Assessment ReportScore: 91/100 (Grade A)
📊 Coverage Details
Generated by OrchestKit CI Report • vitest + @vitest/coverage-v8 |
orchestkit-release-bot
Bot
changed the title
orchestkit-release-bot
Bot
force-pushed
the
release-please--branches--main
branch
from
August 8, 2026 07:45
f68007a to
ce7bfff
Compare
orchestkit-release-bot
Bot
force-pushed
the
release-please--branches--main
branch
from
August 8, 2026 11:25
1ad57c2 to
81ce33d
Compare
orchestkit-release-bot
Bot
changed the title
orchestkit-release-bot
Bot
force-pushed
the
release-please--branches--main
branch
4 times, most recently
from
August 8, 2026 14:14
4760bf7 to
91a26dd
Compare
yonatangross
added a commit
that referenced
this pull request
Aug 8, 2026
…3341) The first recomputed release PR (#3304) went red on validate-counts. Not a release bug: the gate hard-coded plugins[0] as "the" version, and since the channel split (#3340) plugins[0] is the PINNED stable entry, 9.8.0 by design, while package.json carries 10.0.0-alpha. The entry that must agree with the release is the one whose source.ref tracks main, selected by that property with the old positional behaviour as fallback for a single-entry layout. The pinned entry has its own guard (test-alpha-channel.sh), so nothing is lost by excluding it here. Verified both directions before pushing, against real trees: main (9.8.0 everywhere) exit 0 PASSED release branch (10.0.0-alpha) exit 0 PASSED, tracking entry named The other two red checks on #3304 were stale runs against a superseded bot commit; the schema suite passes at its current head, reproduced in a worktree. Refs #164 Refs #3333
orchestkit-release-bot
Bot
force-pushed
the
release-please--branches--main
branch
from
August 8, 2026 14:31
6188a57 to
26fa767
Compare
yonatangross
added a commit
that referenced
this pull request
Aug 8, 2026
* fix(release): stop the build stamping the pinned channel entry Why #3304 stayed red after the recompute produced correct content. The branch on origin had ork 9.8.0/v9.8.0 and ork-alpha 10.0.0-alpha the whole time; CI's fresh-build step then ran stamp-counts, which wrote .plugins[0].version = $v and position 0 is the PINNED stable entry since #3340. The checkout under test got corrupted to ork=10.0.0-alpha, and test-alpha-channel correctly failed the pin/version agreement. A writer addressing entries by position is the same defect as the validate-counts reader fixed in #3341, one layer up. Swept every remaining positional consumer in one pass: scripts/stamp-counts.sh stamps the tracking entry (ref==main), pinned entries untouched; plugins[0] fallback for a single-entry layout tests/unit/test-sync-versions.sh reads the tracking entry; CLAUDE.md capture made prerelease-aware (bare X.Y.Z read 10.0.0-alpha as 10.0.0) tests/manifests/ test-marketplace-ordering.sh "all entries share one version" stopped being the invariant with the channel split; it only passed CI because the corrupting stamp made them equal. Now: tracking entry == top-level version. Plus one unrelated latent race the same session surfaced: test-sync-versions built its sandbox via `tar -cf - | tar -x`. The extractor exits on a complete archive, the producer's final write takes EPIPE, "tar: Write error", exit 1 under pipefail — with all 6503/6503 files landed. Whether it fires depends on archive size vs pipe alignment, so adding files flips it. Now a temp tar file: no pipe, no race. Verified by replaying CI's sequence on a worktree of the actual release branch with these fixes copied in: RED-PROOF old stamp on that tree: ork -> 10.0.0-alpha (pin says v9.8.0) new stamp ork 9.8.0/v9.8.0 kept · ork-alpha 10.0.0-alpha stamped after alpha-channel 8 passed · ordering exit 0 · validate-counts PASSED · sync-versions round-trip all green at 9.8.0 Refs #164 Refs #3333 * docs(playground): the writer edition of stamp-by-position Satisfies the PR Playground gate. Interactive: stamp the release version with each writer and watch the pin check flip; the corrupting path and the by-meaning path side by side. Refs #164
orchestkit-release-bot
Bot
force-pushed
the
release-please--branches--main
branch
2 times, most recently
from
August 8, 2026 15:16
2e3c3ec to
f27b7ca
Compare
orchestkit-release-bot
Bot
force-pushed
the
release-please--branches--main
branch
from
August 8, 2026 15:39
9ee6292 to
86cd41e
Compare
Auto-regenerated by .github/workflows/skill-autobuild.yml after a src-only edit left the committed build output stale (#2528).
Contributor
Author
|
🤖 Created releases: 🌻 |
orchestkit-release-bot
Bot
added
autorelease: tagged
and removed
autorelease: pending
labels
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
1 participant
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.
🤖 I have created a release beep boop
10.0.0-alpha (2026-08-08)
⚠ BREAKING CHANGES
/ork:quickvizis now/ork:glyph. There is no alias, because a stub named quickviz would reintroduce the/quitprefix collision this change exists to remove.Features
Bug Fixes
Miscellaneous
Code Refactoring
This PR was generated with Release Please. See documentation.