Release 0.0.10

[blooop]

Cuts 0.0.10 so the login-shell fix reaches an installed dl.

main is at 0.0.9, but tag v0.0.9 predates six merged PRs — #77, #78, #76, #81 and #82 are all sitting on main unreleased. Most immediately #82: without a release, dl blooop/devlaunch -- "claude --version" still fails with exit 127 on an installed build, which is exactly what was just observed on the host:

SSH command: devpod ssh devlaunch-main --command claude --version --send-env GH_TOKEN
bash: line 1: claude: command not found

No bash -lc in that argv — the installed build is pre-#82.

Changes

• pyproject.toml and conda.recipe/recipe.yaml: 0.0.9 → 0.0.10. Both, because the recipe carries its own context.version and pins tag: v${{ version }} — leaving it behind would make the conda build fetch the wrong tag.
• CHANGELOG.md: a ## [0.0.10] section covering everything merged since v0.0.9.

The changelog section is not optional bookkeeping here: publish.yml runs etils-actions/pypi-auto-publish with parse-changelog: true, so it reads the notes for the new version out of this file.

After merge

publish-job fires on the push to main, sees the version increase, publishes to PyPI and tags/releases v0.0.10; that release event triggers conda-publish.yml, which builds the recipe and pushes to prefix.dev/blooop. Once that lands:

pixi global install --channel conda-forge --channel https://prefix.dev/blooop devlaunch
dl --install   # completions changed in 0.0.9 — aid shares dl's completion function

Note

The end-to-end check for #82 — dl <repo> -- 'claude --version' exiting 0 — is still unwitnessed; no container in that work had devpod. This release is what makes it checkable on a real host.

🤖 Generated with Claude Code

Summary by Sourcery

Release version 0.0.10 with updated packaging metadata and changelog to capture recent fixes and improvements.

New Features:

• Support development installs that register as a separate dl-next CLI while keeping the released dl binary intact.

Bug Fixes:

• Ensure dl <repo> -- <cmd> commands run in a login shell so workspace PATH (including pixi-installed binaries) is respected and commands no longer fail with command not found.

Enhancements:

• Improve workspace ID derivation to avoid collisions between different specs by widening the ID suffix and centralizing parsing.
• Reduce devpod shell-outs per invocation by reusing answers and refreshing completion caches on a TTL once per run to lower startup latency.

Build:

• Bump project and conda recipe version from 0.0.9 to 0.0.10 to align source, PyPI, and conda builds with the new release.

[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

Bumps devlaunch from 0.0.9 to 0.0.10, updates the conda recipe context version accordingly, and adds a 0.0.10 changelog section documenting the recent login-shell fix and other behavior changes so the automated publish workflow can cut and tag the new release correctly.

Flow diagram for version and changelog driven publish workflow

flowchart LR
  A[Push_to_main_with_version_0_0_10] --> B[Publish_job_detects_version_change]
  B --> C[Publish_job_reads_changelog_with_parse_changelog_true]
  C --> D[Publish_job_publishes_to_pypi_and_tags_v0_0_10]
  D --> E[Release_event_triggers_conda_publish]
  E --> F[Conda_publish_builds_recipe_with_context_version_0_0_10]
  F --> G[Conda_package_published_to_prefix_dev_blooop]

Loading

File-Level Changes

Change	Details	Files
Version bump to 0.0.10 across Python package metadata and conda recipe so both distributions align on the new release tag.	Update the project version field from 0.0.9 to 0.0.10 in the Python package metadata. Update the conda recipe context.version from 0.0.9 to 0.0.10 so the recipe fetches the correct v0.0.10 tag during builds.	pyproject.toml conda.recipe/recipe.yaml
Add a 0.0.10 changelog section capturing the login-shell fix and other recent behavioral changes required by the automated publishing workflow.	Document the fix ensuring dl <repo> -- <cmd> runs its command in a login shell so PATH matches interactive attaches and avoids command-not-found errors. Describe workspace id derivation changes that prevent collisions between specs by widening the id suffix and using a single parse boundary. Describe performance improvements that reduce devpod shell-outs and refresh completion cache on a TTL per invocation instead of on every completion. Describe development install behavior change that installs as dl-next, leaving released dl untouched and reading entry points from pyproject.toml.	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

• 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 89.24%. Comparing base (b304cb6) to head (ddf3ffe).

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #86   +/-   ##
=======================================
  Coverage   89.24%   89.24%           
=======================================
  Files          12       12           
  Lines        1636     1636           
=======================================
  Hits         1460     1460           
  Misses        176      176           

🚀 New features to boost your workflow:

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