Skip to content

v0.3.54 — release-completion bookkeeping (0.3.53 published backfill + three-version audit)

Choose a tag to compare

View all tags
@Linux2010 Linux2010 released this 08 Nov 07:40
· 10 commits to main since this release
v0.3.54
f55ddc7
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

v0.3.54 — release-completion bookkeeping (0.3.53 published backfill + three-version audit)

Docs-only bookkeeping cycle completing the v0.3.53 publication. No src/, web/ or tests/ product code changes.

What changed

  • CHANGELOG: the 0.3.53 entry is corrected from candidate — release withheld to published (real npm publish timestamp 2026-11-08T02:39:25.949Z, tag v0.3.53, merge 3d7c581 (#313), GitHub Release link); the section date moved to the real release date 2026-11-08 (same date-equals-release convention as 0.3.49–0.3.52). The entry now records honestly that the clause-B block was lifted by the single-rerun flake classification and that the WEB32-P0-08 root cause remains open. Adds the [0.3.54] candidate entry.
  • README / README.zh-CN: header summaries rewritten from the stale "release withheld" wording to the 0.3.53-released state; install pin → 0.3.54.
  • docs: docs/plan/evidence/v0.3.54/status-audit.md — three-version (0.3.51–0.3.53) delivery-status audit: git tags (v0.3.51→0702878, v0.3.52→a054c44, v0.3.53→3d7c581, local rev-parse + remote ls-remote cross-check, all on main), registry versions exist, dist-tags.latest chain 0.3.51 → 0.3.52 → 0.3.53 with no regressions. Includes the v0.3.53 release-facts backfill and the open WEB32-P0-08 root-cause item.
  • Version bump (6 places): package.json, npm-shrinkwrap.json (top + packages[""]), CHANGELOG.md, README.md, README.zh-CN.md + tests/coding-task-eval.test.ts packageVersion pin.
  • Plan: docs/plan/v0.3.54-plan.md. PR: #314, squash-merged to main as f55ddc7.

Quality gates (CI run 42456978544 — head 4bcda3b, 18/18 jobs success, first attempt, zero flake reruns)

Job Conclusion Duration
Release gate (release:check) ✅ success 1m37s
TypeScript type-check ✅ success 47s
Dependency security audit ✅ success (0 vulnerabilities) 29s
Dependency health report (offline) ✅ success 35s
Node 22 verification ✅ success 7m26s
Node 24 verification ✅ success 6m37s
Node 26 verification ✅ success 5m25s
Web E2E critical journey on Node 22.12.0 floor ✅ success 6m25s
Web E2E critical journey on Node 24.0.0 floor ✅ success 6m17s
Web E2E critical journey on Node 26.0.0 floor ✅ success 6m58s
Web E2E full suite three consecutive runs ✅ success 29m52s
Build the exact release tgz once ✅ success 1m9s
Exact tgz on Node 22.12.0 floor ✅ success 1m16s
Exact tgz on Node 24.0.0 floor ✅ success 1m1s
Exact tgz on Node 26.0.0 floor ✅ success 1m8s
Lean Harness benchmark and confluence ✅ success 2m43s
Aggregate exact-artifact Web E2E receipt ✅ success (decision GO) 33s
Aggregate fail-closed v0.3.x release receipt ✅ success (decision GO) 19s

Local gates: npm run release:check PASS 10/10 (full Jest: 382 suites, 4588 passed / 5 skipped); npm run build exit 0; tests/coding-task-eval.test.ts 5/5.

Release artifact integrity

  • Tarball sha256: 2d063ca06b1a269f26ae8fedf013393f23429905dd9e0351f3c975d546d2f85d
    — local pack (clean worktree at f55ddc7) byte-identical to CI web-e2e-receipt.tarballSha256 (decision GO) and to the local release-gate artifact.
  • Registry shasum (sha1): 58fb5fca4d6c92254d54dd561754bae39a9a0b56 — matches the published tarball.
  • npm publish: exit 0; authoritative acceptance signal E409 Cannot publish over previously staged version "0.3.54" on republish; registry-visible latest=0.3.54, published 2026-11-08T07:39:20.165Z.
  • Tag: v0.3.54 (annotated, peel → f55ddc7), pushed; tree identity 4bcda3b^{tree} == f55ddc7^{tree} (09d58e89…) verified before tagging.

Install

npm install -g @orion-agents/orion-code@0.3.54
orion --version
orion doctor

Notes

  • Docs-only cycle consuming a version number: quality clause C normally reserves version bumps for cycles with product deltas; the standing automation directive "advance exactly one version per round" takes precedence, consistent with rounds v0.3.38–v0.3.53. Flagged for maintainer review.
  • WEB32-P0-08 root cause remains open (docs/plan/evidence/v0.3.53/investigation-and-audit.md); this release changes nothing in that area.
  • The human-labeled paid quality benchmark and real Host + Chrome full-chain E2E remain honestly not_run (no model credentials in the automation environment).
Assets 2
Loading