Repository navigation
Two-branch release strategy: CI gating + docs (stacked on #1) - #2
Closed
alexshapalov wants to merge 5 commits into
Closed
alexshapalov wants to merge 5 commits into
alexshapalov wants to merge 5 commits into
Conversation
- release.yml: a guard job refuses any tag that is not an ancestor of origin/main, so public release artifacts are built from main only; a tag from prod or a feature branch cannot publish. - ci.yml: run on push to main and prod (not the dev branch). - docs/pgx/local-dev/release-strategy.md: the branch topology with verified SHAs (prod = 913630e, tag pgx-v0.1-beta.1, the PGRun Beta v1 engine), the one-way selective cherry-pick backport policy, the no-auto-sync rule, the branch-protection and prod engine-only CI spec to apply in GitHub settings, and the artifact-source separation (public install vs PGRun internal build). Prepared for review: no branches pushed, no release published, no GitHub settings or PGRun deploy configuration changed. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
alexshapalov
added a commit
that referenced
this pull request
Oct 18, 2026
Two-branch release strategy: CI gating + docs (re-opens #2 onto main)
alexshapalov
added a commit
that referenced
this pull request
Oct 18, 2026
pgx run — one command to a ready database (stacked on #2)
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
1 participant
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.
Two-branch release strategy (CI gating + docs)
Stacked on #1. This PR is the single commit
f4f7bc4be2; its base ispgx-local-devso the diff is only the release-strategy change. After #1 merges tomain, this retargets tomain.Changes
release.yml— adds aguardjob: a release tag must be an ancestor oforigin/main, so a tag pushed fromprodor a feature branch cannot produce public artifacts. Public releases are cut frommainonly.ci.yml— runs onpushtomainandprod(plus all PRs).docs/pgx/local-dev/release-strategy.md— the branch topology, verified SHAs (prod=913630e11d=pgx-v0.1-beta.1, rollback727f31e49f), the one-way cherry-pick backport policy (main → prod, never a branch merge), the no-auto-sync rule, the branch-protection + prod engine-only CI spec, and the artifact-source separation (public installer downloads GitHub Release artifacts; PGRun stages internal ssh builds pinned by SHA-256 — disjoint).Model
mainprodprodis an ancestor ofmain; they do not diverge.main's engine is byte-identical to the deployedprodengine plus the additive libxml2 fix.🤖 Generated with Claude Code