Release code-index 0.41.10 #413
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!413
Loading…
Reference in a new issue
No description provided.
Delete branch "codex/release-0.41.10"
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 core 0.41.10 with the daemon recovery, coverage disclosure and Windows source-cache fixes merged in #411. Only Cargo.toml, Cargo.lock, README.md and distribution/registry.v1.json change; plugin bytes, schema, ABI and guest SDK remain unchanged. Python stays at 0.1.4.
The direct parent
feb95a0cpassed all required core, native Windows, package and pilot workflows (1504–1507). Windows passed 4,806 main tests and 27 timing tests; core timing passed all 37 tests. The source merge tree was verified identical to that qualified parent. Version-only validation passed locally.After normal version-only checks and merge, tag this PR head
d2597cd3, a merged ancestor directly parented by the qualified source commit, so the existing release gate can reuse qualification without recursively resolving a merge commit (#409). Verify the version merge tree before tagging. Conservative activation rebuilding remains tracked in #410 and #412.Released stable v0.41.10: https://git.h-dv.de/h-dv/code-index/releases/tag/v0.41.10 . Normal release run 1520/global 6352 passed all 10 jobs, including the inherited CI gate, four builds, Windows archive smoke, archive assembly, publication and signed channel seeding.
Independent post-publication verification passed: the published 0.41.9 binary verified the new signed core catalog and both signed channel projections; the new binary verified them too. All four downloaded archive hashes matched the authenticated catalog. All seven CIP/signature pairs in every archive were byte-identical to 0.41.9; all 11 channel packages and 32 existing versions were retained.
An isolated project/operator home upgraded with the actual published 0.41.9 and 0.41.10 binaries and bundles, without an explicit plugin update or root config. Python 0.1.4 retained its signed digest and ready/withheld=0 layout. Activation generation changed 2→3 as expected under the existing core-label policy (#412); this release does not remove that rebuild cost. No partner installations or existing project daemons were changed.