Repository navigation
basou: Release v0.6.0 (SDK read API, JSON Schemas, billing-grade stats) - #43
Merged
Merged
Conversation
Promote the Unreleased section to 0.6.0 and bump all four package manifests (core / cli / sdk / basou) to 0.6.0 in lockstep. Highlights since 0.5.0: - billing-grade work-measurement v2: Codex active time from real per-turn intervals, plus a machine_active_time_ms model-compute measure (#40). - @basou/sdk v0.2: a runtime, read-only programmatic API over @basou/core's readers for reading .basou/ provenance (#41). - @basou/core JSON Schema artifacts for the on-disk formats, generated from the Zod schemas and shipped under ./schemas/* (#42). Also: document the four-package lockstep bump in CONTRIBUTING, and record the 0.6.0 pre-publish dry-run tarball contents in the release checklist (core now ships its schemas/, cli ships two entry points). This commit only prepares the release; tagging v0.6.0 and the OIDC publish remain maintainer actions. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Summary
Release preparation for v0.6.0. Promotes the
## UnreleasedCHANGELOG section to## 0.6.0 — 2026-06-05and bumps all four package manifests (@basou/core,@basou/cli,@basou/sdk,basou) to0.6.0in lockstep. A minor bump: everything since 0.5.0 is additive.Highlights since 0.5.0
task_started/task_complete) instead of a gap-capped approximation, plus amachine_active_time_msmodel-compute measure.@basou/sdkv0.2 (feat(sdk): add a read-only programmatic API for workspace provenance #41) — a runtime, read-only programmatic API over@basou/core's readers for reading.basou/provenance (was types-only).@basou/coreJSON Schema artifacts (feat(core): emit JSON Schema artifacts for the on-disk .basou/ formats #42) — draft 2020-12 schemas for the on-disk formats, generated from the Zod schemas and shipped under./schemas/*.Also in this PR
CONTRIBUTING.md"Release flow" step 3 now documents the four-package lockstep bump (addspackages/basou, which tracks the same version though it is not yet auto-published).docs/release-checklist.mdrecords the 0.6.0 pre-publish dry-run tarball contents and corrects the stale "exactly five files" expectation:@basou/corenow ships 13 files (dist + 8schemas/*.json),@basou/cli8 (two entry points),@basou/sdk5 (now a real runtime, not the 0.3.1 placeholder). Notes that publishing is the OIDC tag-push workflow, with the manualpnpm publishflow as the documented fallback.What this PR does NOT do (maintainer actions)
Per
CONTRIBUTING.mdRelease flow, this commit only prepares the release. After merge, a maintainer:git tag -a v0.6.0 -m "..."and pushes it;v*.*.*tag push triggers.github/workflows/release.yml→ verify → OIDC trusted-publish of@basou/core/@basou/cli/@basou/sdkwith provenance.(
basouis not in the publish matrix and is not auto-published this release; its version is bumped only for monorepo consistency.)Test plan
pnpm install(no lockfile change — version-only bump), thenpnpm -r build && pnpm typecheck && pnpm test && pnpm lintall green (core 732 + sdk 17 + cli 417; lint clean apart from pre-existing unrelated warnings). Pre-publish dry-run (pnpm --filter @basou/<pkg> publish --dry-run) captured for all three published packages and recorded in the checklist.🤖 Generated with Claude Code