Repository navigation
release 0.2.4 - #68
Conversation
Fifteen commits of main have had no release. `latest` and main's manifests both said 0.2.3 while the code differed by 85 files, so the version number matched and the tree did not — which is worse than an obvious lag. This is what npm has been missing: #50 through #66, including `orca quickstart`, the framework support checks, OpenCode catalog capture, the credential-sanitising series, and the publishing automation itself. First release made with `scripts/set-version.mjs`: one command for the thirty-eight fields across thirteen manifests, plus the lockfile. Merging this is the release — `release.yml` sees a version with no tag, runs the gate, publishes in dependency order and creates `v0.2.4` itself. Verified before pushing: 38 fields moved, every internal pin at 0.2.4, `publish-order.mjs` clean, zero `registry.npmjs.org/@orcareplay` entries in the lockfile, `npm ci` green on it, and the full suite at 2033 passed / 23 failed with the failure set identical to main's baseline. The diff is 14 files and 77 lines each way — the same shape as the hand-written `release 0.2.3` commit. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
085de4b to
4305406
Compare
![orcacode-review[bot]](https://avatars.githubusercontent.com/in/4254738?s=60&v=4){kind=small}
There was a problem hiding this comment.
🐳 OrcaCode Review
✅ No findings — nothing to flag in this PR. Great work!
OrcaCode Review — Route Smarter. Ship Safer. Spend Less.
Engine-reported: 357 calls · 17.8M tokens · 98% cached
❤️ Share · Install OrcaCode Review
Free on GitHub — the review runs on your own OrcaRouter key. If it helped, a shout-out goes a long way.
Share: X · Reddit · LinkedIn
Follow: X · Discord · LinkedIn · OrcaRouter
There was a problem hiding this comment.
⚠️ Outdated review — the PR head changed from 085de4b to 4305406 during the review; these findings describe a diff the PR no longer has.
These findings describe085de4b86025. Re-run the review to check the PR as it stands now.
🐳 OrcaCode Review
✅ No findings — nothing to flag in this PR. Great work!
OrcaCode Review — Route Smarter. Ship Safer. Spend Less.
Engine-reported: 368 calls · 19.6M tokens · 98% cached
❤️ Share · Install OrcaCode Review
Free on GitHub — the review runs on your own OrcaRouter key. If it helped, a shout-out goes a long way.
Share: X · Reddit · LinkedIn
Follow: X · Discord · LinkedIn · OrcaRouter
1 participant
Orca-Code-Review — push 1
✅ no blocking findings
Merging this publishes
0.2.4to npm aslatestand createsv0.2.4. Nothing else in the diff.latesthas been stuck on 0.2.3 while main moved 15 commits ahead — the version number matched and the code did not. This ships #50–#66:orca quickstart, the framework support checks, OpenCode catalog capture, the credential-sanitising series, and the publishing automation itself.First release made with
scripts/set-version.mjsinstead of by hand:node scripts/set-version.mjs 0.2.4 --lockChecked before pushing
0.2.4publish-order.mjsregistry.npmjs.org/@orcareplaycount 0 (the 0.2.1 poisoning)npm cion the new lockfilerelease 0.2.3The automation this exercises
Already verified in production on the #66 merge and a dispatched dry run:
release.yml'sdecideansweredmain is at 0.2.3, which is already tagged — nothing to releaseand skipped the release job, in seconds.Publish nextran end to end:picksucceeded (soactions: readis right), chose main's tip8812949, derived0.2.4-main.g8812949, moved 38 fields and packed all 12 — 12 dry-run lines, 0 publishing lines, npm untouched.🤖 Generated with Claude Code