fix: publish new package versions from independent release URLs #396
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!396
Loading…
Reference in a new issue
No description provided.
Delete branch "codex/package-catalog-release-fix"
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?
C# 0.1.5 was published successfully, but core finalization stopped before uploading assets because its catalog still pointed at
v0.40.0/de.h-dv.csharp-0.1.5.cip(HTTP 404). The package record writer had retained the old core release segment when moving the version row.New package versions now use their encoded
pkg/<id>/v<version>release URLs automatically. Unchanged historical versions retain their published URLs;--own-releasecan also repair an already recorded version. The current C# row was repaired through that writer and matches the signed, served channel. All eleven package identities are unchanged.Runtime 0.41.2 carries the correction without changing the existing v0.41.1 tag, which remains a prerelease. C# 0.1.5 already admits this runtime through its
>=0.41.1floor and needs no new package release. The same batch pins the artifact pilots to published runtime v0.41.1, which admits C# and passes its semantic checks, and separates current ABI admission fields from the historical support-policy audit. C# static/instance-call coverage and a stable ABI promise remain open.Validation:
-D warnings; formatting and diff checks passed.C# readiness also tracks the compiler-verified instance/extension wrong-target case in #397. A capability-withdrawal/reindex/restore control confirmed that withholding
extension_methodsclears that edge while preserving package ownership. Full C# semantic readiness remains open.