chore: release v0.41.17 #444
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!444
Loading…
Reference in a new issue
No description provided.
Delete branch "codex/release-0.41.17"
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.17 with #443’s configured background plugin updates, signed live-channel discovery, and corrected shadowed-approval reporting (#441/#442).
Only the four declared version sites change.
version_bump.sh --version-only HEADpasses for7da3598f5e6a62c1e21e1855ae053a5ac70af9ce. Package versions, ABI, dependency pins, guest inputs, compatibility floors and workflows are unchanged.The direct parent is qualified source
21ab63bf, normally merged through #443 asac1e3d2f; source and merge have identical treeef3b7ead. All corrected-head workflows passed: Windows 6569, core 6570, packages 6571, pilots 6572. Linux workspace/timing passed 5,063/44 tests; native Windows workspace passed 4,841, followed by its native profile/smoke gates. The superseded first head’s bound-registration failure is documented in #443 and was not merged.Normal version-branch checks and merge still apply. Tag the qualified version head after the merge/tree/classifier proof in
docs/releasing.md, then verify signed artifacts, isolated .16→.17 upgrade, published-daemon background checks and self-dogfood. Host sources change inside the conservative extraction fingerprint, so package-enabled projects may rebuild at startup; database/approvals are retained.Stable v0.41.17 is released and independently verified. All normal source/version/release gates passed, plus published-artifact signatures/hashes, .16→.17 upgrade/concurrency checks, the native daemon's configured background update check, and self-dogfood. Full receipt: #442 (comment)
The host-source fingerprint changes and may require a startup activation rebuild. Existing databases and approvals are retained. Independent package checks follow existing
[update]policies; this release adds no manual MCP updater tool.