Release 0.3.0

[blooop]

Cuts 0.3.0: ## [Unreleased] becomes ## [0.3.0], rust/Cargo.toml's
[workspace.package] version goes to 0.3.0, and the two places that track it by
literal follow — rust/Cargo.lock's five workspace crates and
devlaunch-test-support's versioned_with_the_workspace.

Minor rather than patch because this release moves state that already exists on
disk: the workspace-id budget goes 38 → 47 (#283), so the id derived for a long
branch name changes, and that id names both the devpod workspace and the clone
directory under ~/.cache/devlaunch/repos/. Every additive release since 0.1.0
took a patch bump; this is not additive, and the version is the only place a user
sees that before their next launch does.

Existing containers keep opening — dl addresses a workspace by the devpod id
recorded in metadata.json, which wins over the derivation. A clone directory
whose leaf changes is re-cloned under the new name on the next launch, and the old
one becomes a directory no record claims, which dl --prune lists and offers to
remove.

Merging this to main is what triggers Auto-publish: PyPI, the v0.3.0 tag and
the GitHub release, with Conda Publish chained off it.

🤖 Generated with Claude Code

Summary by Sourcery

Release version 0.3.0 across the project metadata and changelog.

Build:

• Bump the Rust workspace and workspace crate lockfile versions to 0.3.0.

Documentation:

• Finalize the 0.3.0 changelog entry.

Tests:

• Update the workspace-version consistency test for 0.3.0.

[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

This PR cuts the 0.3.0 release by promoting the changelog entry from Unreleased, bumping the Rust workspace version to 0.3.0, updating the generated Cargo.lock entries accordingly, and aligning the devlaunch test-support version assertion with the new workspace version.

File-Level Changes

Change	Details	Files
Promote the Unreleased changelog section to a dated 0.3.0 release entry.	Insert a new ## [0.3.0] - 2026-08-20 section immediately after ## [Unreleased] Keep existing workspace-id change notes under the new 0.3.0 section	CHANGELOG.md
Bump the Rust workspace package version to 0.3.0 and synchronize dependent artifacts.	Update [workspace.package] version field from 0.2.2 to 0.3.0 Refresh Cargo.lock so the five workspace crates reflect version 0.3.0 Update test-support assertion to expect CARGO_PKG_VERSION 0.3.0	rust/Cargo.toml rust/Cargo.lock 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 (3ac7038) to head (f2f6c34).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #285   +/-   ##
=======================================
  Coverage   93.26%   93.26%           
=======================================
  Files          25       25           
  Lines        3774     3774           
=======================================
  Hits         3520     3520           
  Misses        254      254           

🚀 New features to boost your workflow:

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