Repository navigation
Prepare hardened registry relaunch with open-source and service boundaries - #2
Merged
Merged
Conversation
This was referenced Oct 25, 2026
Merged
AppSolves
force-pushed
the
audit/registry-relaunch-rc
branch
from
October 25, 2026 23:09
1ddaa96 to
caf19e6
Compare
AppSolves
force-pushed
the
audit/registry-relaunch-rc
branch
from
October 25, 2026 23:26
caf19e6 to
36c7612
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Preserves the registry/security and Apache-2.0 work. Adds a fail-closed, manual-only private GHCR publication gate: existing PRIVATE package identities, actual protected-environment/owner reviews, anonymous denial and owner-attested ACL/inheritance checks are required before login/push. Dedicated publisher and read-only deployment credentials replace GITHUB_TOKEN publishing; no automatic OCI source linkage is emitted. Private image layers are not imported from or exported to public-repository Actions caches. Future separately approved publication additionally checks actual digests, visibility, authorized pulls and receipts while preserving SBOM/provenance.
Six offline policy regressions pass. No image was published and no package visibility, secret, environment or cloud setting was changed. Actual package visibility remains UNCONFIRMED with current read permissions; missing package/environment proof blocks publication. Existing container/upstream findings still require security disposition.
Coordinated immutable source snapshot
9d316205f3a23584f5f91e09572c2c7391a350c610677630de2f8396592c2fbc727752d985d9f53860a6e93d3e166c8310812210bd523a537db65e7a096d2a496cfd03b31fb0e67e4cdbb34f23f98df378acee5fb3b98939ec8d1f1920f4e002f20b54cd9606a541926db2f7991197623eb4f190cd03083dVerification status
Local stable 1.1.0/compiler-helper installation, corrupt-download rollback, protocol rejection, Cranelift and LLVM Full LTO, and actual args install/lock/runtime checks passed. Existing published 1.0.16/helper assets and the global installation remain untouched. Source binaries are identified by their real source version plus exact SHA, never relabeled as already released 1.1.0.
The final exact-six-SHA four-platform acceptance and final-head required CI are running/queued; not yet claimed passed. The portable actual-args Host fix already passed Windows/Linux/macOS at editor 9f9eda5; the finalized pin-only heads are being rerun.
Separate release gates
Engineering/merge → Fidan 1.1.0 stable artifacts → approved production DAL launch → args 0.1.0 → separately approved editor/site/distribution updates. The args source sentinel remains. PRIVATE GHCR visibility/ACL/environment proof and container/dependency CVE disposition, real providers/infrastructure, restore/rollback and legal approvals remain external gates. None are inferred from green CI.
All six PRs remain Draft. No merge, tag/release, package/image publication, deployment, production/cloud/secret mutation or force-push is part of this change.