release: 0.62.0

[blooop]

Release 0.62.0: dl rmt (#685).

Bumps the workspace version in rust/Cargo.toml and rust/Cargo.lock, the README's conda badge and dl --version example, and cuts ## [0.62.0] in the CHANGELOG. publish.yml tags and publishes on merge.

🤖 Generated with Claude Code

Summary by Sourcery

Prepare the 0.62.0 release with updated project metadata and user-facing version references.

Build:

• Bump the workspace and lockfile versions to 0.62.0.

Documentation:

• Update the README release references for version 0.62.0.
• Record the 0.62.0 release and dl rmt addition in the changelog.

[sourcery-ai]

Sorry @blooop, you've used your own review budget of 250,000 diff characters for the last 7 days.

You can request another review in 3 days and 1 hour by commenting @sourcery-ai review. Upgrade to get a review now.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This release commit synchronizes the Rust package metadata, lockfile, README references, and changelog for version 0.62.0, documenting dl rmt as the release feature.

File-Level Changes

Change	Details	Files
Updates the project and user-facing release metadata from 0.61.0 to 0.62.0.	Bumps the Rust workspace and lockfile package versions. Updates the README Conda badge and documented version output. Adds the dated 0.62.0 changelog section and associates the dl rmt entry with issue feat: dl rmt removes the workspace this herdr tab is named after #685.	rust/Cargo.toml rust/Cargo.lock README.md 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 94.60%. Comparing base (887a9e6) to head (07823e8).

Additional details and impacted files

Flag	Coverage Δ
python	42.98% <ø> (ø)
rust	94.80% <ø> (-0.02%)	⬇️

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

Components	Coverage Δ
shipped code (rust)	94.80% <ø> (-0.02%)	⬇️
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.