You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bump the workspace and internal crate pins to 0.7.0 so the next
minor release can be published from a single coherent repo state.
This also updates the in-repo release-facing references that still
pointed at 0.6.0 and reruns the documented local release checklist.
Constraint: Release prep must keep the workspace version, internal crate pins, and release-path assertions in sync
Constraint: cargo publish --dry-run checks Git dirtiness even when jj already records the mutable change state
Rejected: Fold in extra code cleanups during the release cut | would broaden a release-only change without improving publishability
Confidence: high
Scope-risk: narrow
Reversibility: clean
Directive: When running release dry-runs from an active jj working-copy change, export first or use --allow-dirty
Tested: cargo test
Tested: cargo build -p taskers --bin taskers --bin taskers-gtk
Tested: env TASKERS_TERMINAL_BACKEND=mock bash scripts/headless-smoke.sh ./target/debug/taskers --smoke-script baseline --diagnostic-log stderr --quit-after-ms 5000
Tested: bash scripts/smoke_linux_release_launcher.sh
Tested: cargo publish --dry-run --allow-dirty -p taskers-domain
Tested: cargo publish --dry-run --allow-dirty -p taskers-paths
Tested: cargo run -p taskers-cli -- --help
Tested: cargo run -p taskers-cli -- notify --help
Tested: cargo check
Tested: cargo clippy --workspace --all-targets
Tested: cargo install --path crates/taskers-app --force
Not-tested: pushing tag v0.7.0 to origin and publishing the draft GitHub release/assets
Not-tested: full crates.io publish sequence for the dependent workspace crates
0 commit comments