[blooop]

Cuts 0.1.2. The version lives in rust/Cargo.toml's [workspace.package] (the
single source the publish workflow reads), so the bump plus the Cargo.lock
member versions plus the changelog section is the whole release.

What ships

One user-facing change, #270:

• A clone refused as not-found names the owner dl knows. dl kinisi/kinisi_ros
  where the repository is kinisi-robotics/kinisi_ros used to end at git's own six
  lines — "Repository not found" plus four lines of access-rights advice — which
  read identically to a permissions problem and named nothing to try instead. dl now
  checks the same completion cache the shell completes from and adds one line:
  Did you mean 'kinisi-robotics/kinisi_ros'?, carrying the branch back when the
  spec had one. Divergence row 29.

Narrow by construction: only a host's own not-found wording earns the line, only
from a clone step, and not when the cache also knows the repository under the owner
typed. git's text above it is unchanged in every case, so a machine with no
candidate in its cache sees exactly what it saw before.

One thing folded in

devlaunch-test-support's versioned_with_the_workspace asserts this crate's
inherited version against a literal, so it has to move with every release. The
0.1.1 bump left it at "0.1.0" and no CI job caught it — the rust-parity job
tests devlaunch-runner, devlaunch-core, aid and dl by name and never this
crate — so a developer's cargo test --workspace has been red since 0.1.1. Green
again here.

Worth knowing rather than fixing silently: the test is a tripwire for this crate
tracking the workspace version, and it cannot read that version any way other than
the literal it compares against. It will need this same one-character edit at 0.1.3.

Verified

• dl --version reports dl 0.1.2; cargo test --workspace green (test-support
  included, for the first time since 0.1.1); cargo fmt --check clean.
• The publish workflow's release-notes awk was dry-run against this changelog
  section — it extracts the ## [0.1.2] block and passes the non-empty gate.
• Name the owner dl knows when a clone comes back not-found #270 merged with all 13 checks green, rust-parity and e2e included.

On merge, publish.yml sees the version change, builds the manylinux bin-wheel,
publishes to PyPI, tags v0.1.2 and writes the release from the changelog;
conda-publish.yml chains off that tag.

🤖 Generated with Claude Code

Summary by Sourcery

Release version 0.1.2 with the updated changelog and workspace package metadata.

Documentation:

• Add the 0.1.2 release section and changelog notes.

Tests:

• Update the test-support workspace-version assertion for the 0.1.2 release.

Chores:

• Bump the workspace and lockfile package versions to 0.1.2.

[sourcery-ai]

Sorry @blooop, you have reached your weekly rate limit of 500000 diff characters.

Please try again later or upgrade to continue using Sourcery

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Release prep PR for devlaunch 0.1.2: bumps the workspace version, refreshes Cargo.lock, adds the 0.1.2 changelog section describing the single user-facing change, and fixes the devlaunch-test-support version tripwire test to match the new workspace version.

Sequence diagram for dl clone not-found suggestion behavior

sequenceDiagram
    actor User
    participant dl
    participant git
    participant completion_cache

    User->>dl: [runs dl kinisi/kinisi_ros]
    dl->>git: [invoke git clone]
    git-->>dl: [repository not found error]
    dl->>completion_cache: [lookup owner/repository candidate]
    alt [candidate found and cache does not know typed owner]
        dl-->>User: [print git error text]
        dl-->>User: [print Did you mean 'kinisi-robotics/kinisi_ros'?]
    else [no candidate found or cache knows typed owner]
        dl-->>User: [print git error text only]
    end

Loading

File-Level Changes

Change	Details	Files
Bump workspace version to 0.1.2 and regenerate lockfile for the Rust workspace.	Update [workspace.package] version from 0.1.1 to 0.1.2 in Cargo.toml so publish workflows read the new release version. Refresh Cargo.lock member versions to align with the new workspace version and dependency graph.	rust/Cargo.toml rust/Cargo.lock
Document the 0.1.2 release and its user-facing change in the changelog.	Add a new 0.1.2 section under Unreleased with the release date. Describe the clone-not-found owner-suggestion behavior shipped in Name the owner dl knows when a clone comes back not-found #270.	CHANGELOG.md
Fix the devlaunch-test-support version tripwire test to track the workspace version for 0.1.2.	Update the versioned_with_the_workspace test literal from 0.1.0 to 0.1.2 so env!("CARGO_PKG_VERSION") matches and workspace tests pass. Preserve the test as a manual tripwire for future releases rather than removing or making it dynamic.	rust/devlaunch-test-support/src/lib.rs

---

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

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.26%. Comparing base (8eea8d8) to head (624fc79).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #271   +/-   ##
=======================================
  Coverage   93.26%   93.26%           
=======================================
  Files          25       25           
  Lines        3771     3771           
=======================================
  Hits         3517     3517           
  Misses        254      254           

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.