Release v0.41.26 from the qualified runtime #477
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!477
Loading…
Reference in a new issue
No description provided.
Delete branch "release/v0.41.26"
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?
Promotes the runtime merged in #476 as v0.41.26. The v0.41.25 workflow stopped before publication because Git's default tag cleanup stripped the release-note headings. That tag stays unchanged; the replacement release will use
--cleanup=verbatimand an actual tag-body preflight.Only the four declared version sites change: workspace manifest and workspace lock entries, current README release links, and registry core metadata. No runtime code, dependency pin, guest build input, package version, ABI, performance limit or sample count changes.
Validation: all nine version-site tests passed;
version_bump.sh --version-only HEADproves the exact metadata-only change; annotated-tag preflight preserves the complete notes and passes the pipeline's body/heading conditions. The runtime parent has green required CI and fresh seven-language plus mixed-load qualification. Existing CI checks the version-only proof before inheriting that evidence.