Skip to content

Release 0.1.1 - #269

Merged
blooop merged 2 commits into
mainfrom
release/0.1.1
Aug 20, 2026
Merged

blooop merged 2 commits into
mainfrom
release/0.1.1

Conversation

@blooop

@blooop blooop commented Aug 20, 2026 •

Copy link
Copy Markdown
Owner

Ships the review follow-ups merged in #265 (#262/#263/#264): restored Python wording on three messages, streaming provisioning notices, single-report purge failures, per-adoption reconcile endings, race-free completion-cache staging, a refresh child that survives a binary swap, divergence row 28, and the CI-enforced public-API freeze.

Version 0.1.0 → 0.1.1 in rust/Cargo.toml (the single source — the wheel, conda package and dl --version all read it); lockfile refreshed; changelog entry added. Auto-publish tags v0.1.1 and ships PyPI + conda on merge.

🤖 Generated with Claude Code

Summary by Sourcery

Release version 0.1.1 with Rust/Python parity fixes, more reliable provisioning and refresh behavior, stricter metadata validation, and a frozen public API.

Bug Fixes:

  • Restore Python-compatible wording for invalid git references and unfetchable recorded default branches.
  • Stream provisioning notices during installation instead of batching them after completion.
  • Report each purge failure once at the step where it occurs.
  • Report each reconciliation adoption's actual outcome in attempt order.
  • Prevent overlapping completion-cache refreshes from overwriting each other's staged data.
  • Keep background completion refreshes working when a binary update replaces the running executable.

Enhancements:

  • Freeze the devlaunch-core public API with a CI-checked snapshot and reduce unused declarations to crate visibility.
  • Reject non-finite, out-of-range, and lone-surrogate values in metadata.json as corruption while preserving the file for quarantine handling.

Build:

  • Bump the workspace release version from 0.1.0 to 0.1.1 and refresh the lockfile.

Documentation:

  • Add the 0.1.1 changelog entry documenting parity fixes and behavioral changes.

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

sourcery-ai Bot commented Aug 20, 2026

Copy link
Copy Markdown

Reviewer's Guide

Release 0.1.1 wires up the Rust port’s review follow-ups, adds a 0.1.1 changelog entry, and bumps the workspace version so packaging/CLI now report 0.1.1, with minor Rust lockfile adjustments refreshed accordingly.

File-Level Changes

Change Details Files
Add 0.1.1 changelog entry documenting Rust-port follow-up fixes and CI-enforced public API freeze.
  • Insert new 0.1.1 section with date and link to PR Rust port review follow-ups: modeling, robustness, API freeze #265, explicitly stating no command grammar or JSON shape changes.
  • Document restored Python-equivalent wording for three user-facing messages, including invalid git ref and unfetchable default-branch errors.
  • Describe streaming provisioning notices, single-report purge failures, per-adoption reconcile endings, race-free completion-cache staging, completion refresh child surviving binary swap, CI public-API freeze, and stricter metadata.json reader behavior as divergence row 28.
CHANGELOG.md
Bump Rust workspace package version from 0.1.0 to 0.1.1 and refresh lockfile for the release.
  • Update workspace package version string to 0.1.1 so all packaging and dl --version reads the new release number.
  • Regenerate Cargo.lock to reflect the version bump and any dependency resolution updates.
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

@codecov

codecov Bot commented Aug 20, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.26%. Comparing base (9fc1274) to head (17bfdcc).

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main     #269   +/-   ##
=======================================
  Coverage   93.26%   93.26%           
=======================================
  Files          25       25           
  Lines        3771     3771           
=======================================
  Hits         3517     3517           
  Misses        254      254           

Impacted file tree graph

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

The scaffold's the_workspace_compiles_and_tests_run asserted the exact
version string, which fails every release bump. The version's one source
is [workspace.package]; the test now only checks the crates inherit one.
@blooop
blooop merged commit 99da7ba into main Aug 20, 2026
15 checks passed
@blooop
blooop deleted the release/0.1.1 branch August 20, 2026 12:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant