fix: publish new package versions from independent release URLs #396

Merged
buildagent merged 2 commits from codex/package-catalog-release-fix into master 2026-10-20 12:30:42 +02:00
Member

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-release can 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.1 floor 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:

  • Reproduced the stale-core URL with a failing regression, then passed all 9 source-ownership tests.
  • 82 targeted catalog, synthesis, release-script, ownership and version-site tests passed.
  • Ran the real writer: only the two C# transport URLs changed; checked both against the signed channel; repeated dry run has no drift.
  • The exact publication download gate fetched all 22 package/signature URLs successfully.
  • Affected Clippy targets passed with -D warnings; formatting and diff checks passed.
  • Both artifact pilots passed against the signed shipped v0.41.1 runtime; C# was admitted and all 83 phases passed. The runtime release's builds and Windows archive smoke also passed; only catalog publication failed.
  • Downloaded the actual C# 0.1.5 and Timeline 0.1.0 release packages: both CIP files are byte-identical to the packages exercised by the shipped-runtime pilots, and both published signatures passed installation in fresh operator stores.

C# readiness also tracks the compiler-verified instance/extension wrong-target case in #397. A capability-withdrawal/reindex/restore control confirmed that withholding extension_methods clears that edge while preserving package ownership. Full C# semantic readiness remains open.

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-release` can 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.1` floor 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: - Reproduced the stale-core URL with a failing regression, then passed all 9 source-ownership tests. - 82 targeted catalog, synthesis, release-script, ownership and version-site tests passed. - Ran the real writer: only the two C# transport URLs changed; checked both against the signed channel; repeated dry run has no drift. - The exact publication download gate fetched all 22 package/signature URLs successfully. - Affected Clippy targets passed with `-D warnings`; formatting and diff checks passed. - Both artifact pilots passed against the signed shipped v0.41.1 runtime; C# was admitted and all 83 phases passed. The runtime release's builds and Windows archive smoke also passed; only catalog publication failed. - Downloaded the actual C# 0.1.5 and Timeline 0.1.0 release packages: both CIP files are byte-identical to the packages exercised by the shipped-runtime pilots, and both published signatures passed installation in fresh operator stores. C# readiness also tracks the compiler-verified instance/extension wrong-target case in #397. A capability-withdrawal/reindex/restore control confirmed that withholding `extension_methods` clears that edge while preserving package ownership. Full C# semantic readiness remains open.
fix: route new package versions to independent release assets
All checks were successful
Package CI / package (php) (pull_request) Successful in 31m31s
Package CI / package (csharp) (pull_request) Successful in 31m59s
CI / CI lane wall-clock headroom (pull_request) Successful in 1m7s
CI / guest crates (fmt, clippy, doc) (pull_request) Successful in 1m39s
Package CI / package (typescript) (pull_request) Successful in 33m7s
Package CI / package (rust) (pull_request) Successful in 33m29s
Package CI / package (javascript) (pull_request) Successful in 33m36s
Pilot plugin compatibility / Pilot compatibility (timeline) (pull_request) Successful in 1m9s
Package CI / package (ruby) (pull_request) Successful in 34m43s
Pilot plugin compatibility / Pilot compatibility (csharp) (pull_request) Successful in 3m11s
Pilot plugin compatibility / Pilot compatibility result (pull_request) Successful in 1s
Package CI / package (python) (pull_request) Successful in 38m57s
CI / cargo check (MSRV 1.98) (pull_request) Successful in 18m37s
CI (Windows) / fmt + clippy + build + test (windows) (pull_request) Successful in 39m22s
CI / cargo doc (intra-doc links) (pull_request) Successful in 9m53s
CI / cargo deny (pull_request) Successful in 11m39s
CI / cargo test (abi, 32-bit + wasm32) (pull_request) Successful in 12m21s
CI / cargo check (windows-gnu) (pull_request) Successful in 16m45s
Package CI / package-corpus (javascript) (pull_request) Successful in 48m24s
Package CI / package-corpus (python) (pull_request) Successful in 48m33s
Package CI / package-corpus (csharp) (pull_request) Successful in 48m49s
Package CI / package-corpus (php) (pull_request) Successful in 48m51s
Package CI / package-corpus (rust) (pull_request) Successful in 48m51s
Package CI / package-corpus (typescript) (pull_request) Successful in 47m40s
Package CI / package-corpus (ruby) (pull_request) Successful in 53m57s
Package CI / package overhead budgets (nightly, one package at a time) (pull_request) Has been skipped
CI / cargo test (pull_request) Successful in 30m15s
CI / OSS corpus (tier 1) (pull_request) Successful in 44m5s
CI / cargo test (daemon transport) (pull_request) Successful in 10m41s
CI / Plugin path cost + pool throughput (nightly) (pull_request) Has been skipped
3775079ec8
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
h-dv/code-index!396
No description provided.