Release v0.41.39: bounded resolver work and atomic activation #497
No reviewers
Labels
No labels
code-review
correctness
dos
performance
security
severity/high
severity/low
severity/medium
tech-debt
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
h-dv/code-index!497
Loading…
Reference in a new issue
No description provided.
Delete branch "release/v0.41.39"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Prepare v0.41.39 from the qualified #53 implementation merged in #496. Resolver checkpoints expose SQLite work and CPU costs; indexed own-import decisions and constrained join order reduce redundant work. Activation resolves within the publication transaction and retains the previous active generation when a work budget refuses the incoming generation.
This PR changes only version references in Cargo.toml, Cargo.lock, README.md and distribution/registry.v1.json. The version-only guard passes (22 replacements). Source commit
76ad893152passed Linux #2267, Windows #2266, package suites #2268 and pilots #2269. Corpus target equivalence covered 1,144,443 references; deterministic work, activation rollback and counter-boundary regression tests passed.Publish the annotated v0.41.39 tag on this version commit after normal merge. Keep #53 open until release CI, public artifact and signature checks, installation, and exact published self-dogfood with edit/restore and the resolver-cost resource have passed.