Release 0.10.0

[blooop]

A workspace is now named by the spec you typed, where it used to be named by its
id — in the selector (owner | repo | branch) and on the tab
(blooop/devlaunch@main, which now survives the first shell prompt). The id itself
did not change: it still addresses every workspace, names every clone directory and
is still the container hostname.

Ships #370 and #371, and the five defects self-review found in them. See CHANGELOG.

🤖 Generated with Claude Code

Summary by Sourcery

Release 0.10.0 with specification-based workspace naming in selectors and terminal tabs while preserving stable workspace IDs.

New Features:

• Display workspace selectors using owner, repository, and branch names derived from the typed workspace specification.
• Persist specification-based names in terminal tabs and suppress title updates when configured.

Bug Fixes:

• Prevent selector label collisions and ambiguous workspace ID parsing from targeting the wrong workspace.
• Keep workspace tabs correctly named when opened by ID and avoid corrupting shell prompts across Bash and POSIX login shells.
• Filter ref names safely before adding title-setting commands to shell profiles.

Build:

• Bump the Rust workspace version to 0.10.0.

Documentation:

• Document the 0.10.0 workspace naming, selector, tab title, and defect fixes in the changelog.

[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

Release 0.10.0 changes how workspaces are presented and titled (selector rows and tab names now use the original spec instead of the opaque id), and fixes several edge cases around workspace distinctness, id decoding, tab title setup, and prompt handling, plus bumps the Rust workspace version to 0.10.0.

Sequence diagram for workspace tab title setup

sequenceDiagram
    participant User
    participant Devlaunch
    participant Profile as Shell profile
    participant Shell
    participant Terminal
    User->>Devlaunch: Enter workspace with spec
    Devlaunch->>Profile: Append deduplicated title PS1 line
    Devlaunch->>Shell: Handover to login shell
    Shell->>Profile: Source profile
    Shell->>Terminal: Print PS1 with workspace title escape
    Terminal-->>User: Tab shows owner/repo@branch

Loading

Flow diagram for workspace naming and display

flowchart LR
    Spec["Typed workspace spec"] --> Identity["Workspace id"]
    Spec --> Display["Display name: owner | repo | branch"]
    Identity --> Address["Addressing, clone directory, hostname"]
    Display --> Selector["Selector row"]
    Display --> Tab["Persistent tab title"]
    Selector --> Collision{"Drawn labels collide?"}
    Collision -->|Yes| FullId["Show whole id"]
    Collision -->|No| Columns["Show owner, repo, branch"]

Loading

Flow diagram for selector collision handling

flowchart TD
    Rows["Workspace rows"] --> Labels["Build owner, repo, branch labels"]
    Labels --> Distinct{"Labels distinct?"}
    Distinct -->|Yes| Compact["Render three columns"]
    Distinct -->|No| IdRows["Render whole workspace ids"]
    Compact --> Select["Map picked row using its own text"]
    IdRows --> Select
    Select --> Action["Open selector action, including dl rm"]

Loading

File-Level Changes

Change	Details	Files
Workspace display and tab naming now use the typed spec (owner/repo@branch) instead of the opaque workspace id, with selector rows split into explicit owner, repo, and branch columns and tab titles persisted across prompts via a profile-injected PS1 modification.	Documented that workspace names shown to users are now based on the original spec rather than the internal id, while the id still functions as address, clone directory name, and container hostname. Explained the selector now renders three columns (owner, repo, branch) instead of a lossy ref-slug representation, with collision handling that falls back to full ids when necessary to keep rows distinct. Described the new tab title behavior where shells append an escape sequence to PS1 via a profile snippet so the tab remains named owner/repo@branch for the entire session, controlled by DEVLAUNCH_NO_TITLE and only installed when the workspace enters Running.	CHANGELOG.md
Fixed multiple workspace-selection and id-decoding edge cases so selector rows remain distinct, ambiguous repo slug readings are rejected, tab titles don’t regress to hash-based ids, and shell prompts are not corrupted by non-Bash escape sequences or trailing newlines in refs.	Clarified that workspace distinctness in the selector is now based on the drawn labels, avoiding cases where non-cloned workspaces and clones shared identical rows and acted on the wrong workspace. Described rejection of ambiguous ids where truncated repo slugs could be interpreted as different branches, causing the row to fall back to displaying the raw id instead of a misleading branch name. Explained that opening a workspace by id no longer appends a second conflicting profile line, preventing the tab title from being reset to the hash-based id. Documented that dash login shells now avoid printing escape sequences literally in the prompt, preferring an unnamed tab over a corrupted prompt. Noted that trailing newlines in refs are now filtered before being written into profile PS1 assignments so both halves of the title use a consistently filtered name.	CHANGELOG.md
Bumped the Rust workspace package version to 0.10.0 to match the release.	Updated the [workspace.package] version from 0.9.0 to 0.10.0 in Cargo.toml to reflect the new release.	rust/Cargo.toml rust/Cargo.lock

---

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 95.22%. Comparing base (a199061) to head (74500eb).

Additional details and impacted files

Flag	Coverage Δ
python	42.98% <ø> (ø)
rust	95.57% <ø> (+0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
shipped code (rust)	95.57% <ø> (+0.01%)	⬆️
harness and tooling (python)	42.98% <ø> (ø)

🚀 New features to boost your workflow:

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