Repository navigation
release: 0.60.1 - #681
Merged
Merged
release: 0.60.1#681
Conversation
Reviewer's guide (collapsed on small PRs)Reviewer's GuideThis patch release packages the setup-pass optimization from #678, which reuses one shell across setup stages instead of spawning a bash for each stage, avoiding repeated $BASH_ENV reads during cold launches. The PR also synchronizes the 0.60.1 release metadata and documentation; no public API or feature behavior is intentionally changed. Sequence diagram for the optimized cold-launch setup passsequenceDiagram
participant Launch as Cold launch
participant Setup as Setup pass
participant Shell as Single shell
participant Stage as Setup stages
participant Env as BASH_ENV profile
Launch->>Setup: start setup pass
Setup->>Shell: spawn one shell
Shell->>Env: read BASH_ENV once
Setup->>Stage: run session, zellij, codex, title, onboarding, trust stages
Stage-->>Shell: execute each stage in subshells
Shell-->>Setup: complete setup pass
Setup-->>Launch: continue launch
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR releases 0.60.1. It ships one change, #678 — the setup pass runs its stages in subshells, not a bash each.
What changes
$BASH_ENVpoints at a heavy shell profile no longer pays one read of it per stage. Over six cold launches of such an image, the setup trip went from 10.9s–11.1s to 6.7s–6.9s. #678 has the details.rust/Cargo.toml,rust/Cargo.lock(bycargo update -w --offline, 5 workspace crates only), the README conda badge and the READMEdl --versiontranscript.CHANGELOG.mdgets the## [0.60.1] - 2026-10-16heading, and the entry gets(#678).The change adds no feature and changes no public API, so this is a patch bump.
How I checked it
pixi run test: 838 passed, 7 skipped, 42 deselected.rust/target/release/{dl,aid,dla} --versionprintdl 0.60.1,aid 0.60.1andaid 0.60.1.git diff rust/Cargo.lockchanges only the 5 workspace crates.prek run --all-filespasses.Merge danger
Door: one-way. The merge starts the publish to PyPI and the conda channel, and a published version cannot be taken back.
Blast radius: small. If the change is wrong, a cold launch can set the hostname, title, session name or Claude onboarding wrongly in a new container.
dl <ws> recreateruns the pass again.🤖 Generated with Claude Code
Summary by Sourcery
Release version 0.60.1 with the optimized setup-pass behavior and synchronized project metadata.
Documentation:
Chores: