Release 0.0.24

[blooop]

dl <workspace> up has been in [Unreleased] since it landed, and it is the one entry in there that another tool already depends on: wayfinder's prewarm fires dl <workspace> up the moment a launch is staged. With no release carrying it, a fully up-to-date machine ran wf 0.14.0 against the released dl 0.0.23, passed every check wf made — dl on PATH, checkout declares a devcontainer — and then failed inside the prewarm on an argument that release had never heard of.

Nothing here but the version: the [Unreleased] section becomes 0.0.24, and pyproject.toml and conda.recipe/recipe.yaml follow it.

This unblocks blooop/wayfinder, which now holds the dl it finds to a floor of 0.0.24 and declares devlaunch >=0.0.24 as a conda run dependency — neither can go green until 0.0.24 is on prefix.dev/blooop.

🤖 Generated with Claude Code

Summary by Sourcery

Cut a 0.0.24 release of devlaunch and document it in the changelog.

Build:

• Bump project version to 0.0.24 in pyproject.toml and conda recipe metadata.

Documentation:

• Add 0.0.24 section to the changelog documenting the previously unreleased dl <workspace> up command.

[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

Bumps the project to release 0.0.24 and aligns all packaging metadata and changelog entries with the new version so that the previously unreleased dl <workspace> up command is now part of an official release.

File-Level Changes

Change	Details	Files
Publish version 0.0.24 and move the previously unreleased dl <workspace> up entry into a tagged release.	Add a new 0.0.24 section to the changelog and move the existing dl <workspace> up entry under it. Update the conda recipe context version from 0.0.23 to 0.0.24. Update the Python project version in pyproject.toml from 0.0.23 to 0.0.24.	CHANGELOG.md conda.recipe/recipe.yaml pyproject.toml

---

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.95%. Comparing base (bb7f821) to head (e002863).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #175   +/-   ##
=======================================
  Coverage   93.95%   93.95%           
=======================================
  Files          21       21           
  Lines        2565     2565           
=======================================
  Hits         2410     2410           
  Misses        155      155           

🚀 New features to boost your workflow:

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