Skip to content

v0.10.1 — start here: finishing what 0.10.0 started, and how to help #6094

Description

@Hmbown

Status (2026-09-22): v0.10.0 is published. 0.10.1 is in planning. 0.10.1 is a patch release: it finishes work 0.10.0 started. It adds no new features and makes no breaking changes. This is a release plan, not a release announcement. A version bump in source does not mean packages or binaries have been published.

What shipped in 0.10.0

  • A redesigned terminal workbench, clearer model, provider, fleet and plugin settings, and more reliable session and runtime behavior. It replaces the unpublished 0.9.14 candidate.
  • Release notes: v0.10.0. Full history: CHANGELOG.md.
  • The v0.10.0 milestone keeps its completion history, including the links carried over from the former v0.9.14 plan.

What 0.10.1 is: finish what we started

Each item below already has one or more partial fixes behind it. 0.10.1 closes those gaps instead of adding scope. CI and release-pipeline fixes land first, because every other change lands through that gate.

Product fixes

CI and release pipeline (these land first)

  • Make the CI ratchets block pull requests the same way they block main, so a green PR cannot turn main red. Each ratchet gets an update command so the fix lands in the same PR.
  • Update the release record automatically after publish, so a new release no longer turns Web Frontend red.
  • Run the parity gate in the release candidate, so the tagged SHA is the SHA the candidate validated.
  • Keep macOS jobs on fork PRs within the 90-minute limit, and keep the Actions cache under its size cap.
  • Stop the PR-to-issue link check from reading "does not close #N" as a closing keyword. Automation applies labels and does not post comments.

Also open in this milestone

Not in 0.10.1 (planned for 0.11 or later)

ACP sessions on the full turn runtime (#5835), the session-store rewrite (#6144), sub-agent decomposition (#6293), the catalog single-authority work (#6396), the context_status tool (#6217), and test-environment convergence.

Where work is tracked

  • The v0.10.1 milestone is the release list. Items above without an issue link get one when work starts.
  • Issues mirror to our internal tracker automatically, so please file once.

How PRs land

  • Every PR lands through hosted CI. A local pass, a model trial and a published release are separate levels of evidence, and one does not stand in for another.
  • Contributor PRs are reviewed and merged as their own PRs, with credit. If your branch needs a rebase or a fix, we help on your branch.
  • Write Fixes #N or Closes #N only when the PR really resolves the issue. Otherwise use Refs #N.

How to report

  • Bugs: use the bug report template. Include reproduction steps, codew --version (with the build SHA), and the client and operating system you used. For a freeze, say what the turn was doing when it stopped, and attach anything that appeared in crashes/.
  • Design feedback: show the screen and describe what you were trying to do, what was unclear, and your window size. Mouse and keyboard behavior both matter.
  • Features: use the feature request template. New features are aimed at 0.11, not this patch.

How to help

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionFurther information is requested

    Projects

    • Status
      Backlog

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions