Repository navigation
Conversation
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.
Registering a project/version now creates immutable release metadata: matching canonical retries return the same record, while conflicting digest or metadata returns 409. Staging/production promotion uses an expected revision, so two operators reading the same revision cannot both replace the pointer. A composite foreign key prevents channels pointing across projects.
The example uses pinned Rust/Axum/SQLx/Tokio, project-scoped bearer tokens, verified Cloud TLS, restricted runtime grants, separate migration credentials and explicit setup/cleanup. Queries use typed runtime-checked SQLx mappings, so the committed Cargo.lock builds without database credentials. It stores decisions only; no artifact downloads or deployments.
Validation on native Ubuntu ARM64 against ClickHouse Managed Postgres/PostgreSQL 18.6: two unit tests and six Cloud tests passed, covering a 12-request duplicate race, a 2-request promotion race, mismatched retries, cross-project API/DB rejection, input limits (including NUL), rollback, permissions and wrong-CA/hostname rejection. Empty bootstrap, migrate/seed/down/up/replay passed. The reproducible external-process restart script preserved release/channel identity and retry behavior; a fresh target built without database/token variables. GitHub workflow runs formatting, unit tests and build with no Cloud secrets.
Companion article remains a local draft for review and publication; no article URL is included. Temporary Cloud service cleanup and VM retention are recorded in local programme evidence.