Skip to content

Cut 0.36.0 - #593

Merged
blooop merged 1 commit into
mainfrom
release/0.36.0
Sep 9, 2026
Merged

Cut 0.36.0#593
blooop merged 1 commit into
mainfrom
release/0.36.0

Conversation

@blooop

@blooop blooop commented Sep 9, 2026

Copy link
Copy Markdown
Owner

Releases the [Unreleased] section as it stood: the completion fix from #592 — fix: a flag before the workspace spec stopped tab completion and the prebuild fix from #590 — fix: the prebuild tag moved for files the image cannot see.

Four files, the same four every cut touches: rust/Cargo.toml (the single source of the version), rust/Cargo.lock, the two version strings in README.md, and the CHANGELOG.md heading. dl --version and aid --version both print 0.36.0 from a --locked release build.

Minor rather than patch, which is what every cut in this repo has been.

🤖 Generated with Claude Code

https://claude.ai/code/session_01GxeUVm3R579Tqai6GwoEmb

Summary by Sourcery

Chores:

  • Update the project version and release metadata to 0.36.0.

The [Unreleased] section as it stood becomes the release: one completion fix and
one prebuild fix, both of which were costing people something silently.

A flag before the workspace spec no longer stops tab completion. `aid --codex
owner/repo<TAB>` offered nothing at all, and so did every other agent flag and
`dl --devcontainer robot owner/repo<TAB>`, because the script found the spec by
counting words from the command and neither grammar places it by count. It scans
the words before the cursor now and counts the positional ones.

The half worth reading twice is which way the flag table points. It lists the
flags a workspace spec may follow, and every other flag ends the line, because
the flags nobody thinks to list are all on the ending side: the first attempt
listed the endings and put ten flags in the wrong arm, each of which refuses a
workspace for one of four different reasons. `dl --repos my-ws` answers "--repos
takes no workspace", `dl --json my-ws` is a clap error about the missing `--ls`,
and a leading `--force` is not a modifier at all but the workspace slot itself.
Completing a name onto any of those is worse than completing nothing, so the
default arm is the refusal, and both tables are derived from the grammar with a
test doing the subtraction.

Editing prose under `.devcontainer/` no longer throws away the prebuilt
container. The prebuild tag is a hash of the build context, and with a Dockerfile
that copies nothing devpod hashed the whole context directory, so the feature's
README and the host-side hook moved a tag that is supposed to move only when the
image would differ. Every launch on a branch carrying such an edit was building
locally, several minutes at a time, with slowness as the only symptom.

Claude-Session: https://claude.ai/code/session_01GxeUVm3R579Tqai6GwoEmb
@sourcery-ai

sourcery-ai Bot commented Sep 9, 2026

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This release-only PR cuts version 0.36.0 by changing the Cargo workspace source version, synchronizing Cargo.lock, updating README version references, and moving the existing unreleased fixes under a dated changelog heading. Review the lockfile metadata diff and verify that both binaries report 0.36.0 from a locked release build.

File-Level Changes

Change Details Files
Bump the project release version consistently to 0.36.0 across source metadata, lockfile, documentation, and changelog.
  • Update the workspace package version, with corresponding lockfile metadata regeneration.
  • Update README badges and the documented dl --version output.
  • Add the 0.36.0 changelog heading while preserving the unreleased fixes under the new release.
rust/Cargo.toml
rust/Cargo.lock
README.md
CHANGELOG.md

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨

@blooop
blooop merged commit 2f05c38 into main Sep 9, 2026
15 checks passed
@blooop
blooop deleted the release/0.36.0 branch September 9, 2026 13:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant