Skip to content

fix(registry): preserve legacy registry.zpkg.net compatibility alias - #380

Merged
ORESoftware merged 16 commits into
mainfrom
fix/github-source-archive-fallback
Sep 16, 2026
Merged

ORESoftware merged 16 commits into
mainfrom
fix/github-source-archive-fallback

Conversation

@ORESoftware

@ORESoftware ORESoftware commented Sep 13, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Semantically reconciled with current main after the original GitHub source-fallback implementation was superseded by merged PR #379.

Current main already owns the deterministic GitHub tag-archive fallback, PAX metadata handling, strict archive safety checks, tagged manifest identity/version validation, pinned-digest replay, private REST tarball access, and provenance checks. Those duplicate/stale changes were intentionally dropped during the reconciliation rather than choosing ours or theirs mechanically.

The remaining useful delta is narrowly scoped:

  • canonicalize the legacy compiled https://registry.zpkg.net endpoint to https://zpkg.net at the registry transport boundary;
  • accept the legacy endpoint with or without a trailing slash;
  • leave custom HTTP(S) and file:// registries unchanged;
  • retain a focused unit test for the alias behavior.

Current main is an ancestor of this branch. Final cleanup commit b6b8e2d17c0d6146754800cde4ef0ec77cedaeee restored .cli-flags.toml and .zpkg.toml byte-for-byte from main after stale one-line drift reappeared, so the PR now differs from current main only in src/registry.rs.

Merge gate remains exact-head substantive CI plus normal review/protection requirements; no gate should be bypassed.

Preserve current main's merged deterministic GitHub tag fallback and latest-dependency gate. Drop the superseded duplicate source-normalizer/workflow implementation from this branch while retaining the still-useful legacy registry.zpkg.net -> zpkg.net compatibility alias and its focused test.
@ORESoftware ORESoftware changed the title fix(fallback): normalize GitHub source archives into installable Zed deps fix(registry): preserve legacy registry.zpkg.net compatibility alias Sep 15, 2026
Preserve main's merged public CLI portability workflow while retaining only the reviewed legacy registry.zpkg.net -> zpkg.net transport alias and focused test from #380. Current deterministic GitHub/R2/GHCR fallback behavior remains sourced from main; no stale fallback implementation is resurrected.
Preserve #380's focused registry.zpkg.net compatibility alias while taking current main's exact rustfmt-clean env/TOML files. No fallback or registry feature code beyond the reviewed alias is changed.
Preserve the reviewed one-file registry.zpkg.net compatibility alias tree exactly while incorporating current main as the second parent. Current-main comparison proves the candidate differs only in src/registry.rs.
Restore .cli-flags.toml and .zpkg.toml byte-for-byte from current main so this branch contains only the intended registry.zpkg.net compatibility alias change in src/registry.rs.
@ORESoftware
ORESoftware merged commit b23ae01 into main Sep 16, 2026
18 of 25 checks passed
ORESoftware added a commit that referenced this pull request Sep 16, 2026
Rebuild the candidate from current main after #380, overlaying only the five reviewed secret-argv boundary files. This preserves the newly landed registry alias and avoids reviving stale branch state.
ORESoftware added a commit that referenced this pull request Sep 16, 2026
Rebuild the release candidate from current main after #380, overlaying only the reviewed 0.3.1 release metadata files. This preserves the newly landed registry alias while keeping the release diff scoped to Cargo.toml, Cargo.lock, and .zpkg.toml.
ORESoftware added a commit that referenced this pull request Sep 16, 2026
Rebuild the candidate from current main after #380, overlaying only src/dev.rs and tests/develop_edge_cases.rs. This preserves the registry alias and current flags contracts while retaining the reviewed managed-CARGO_HOME path-root fix.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant