Repository navigation
CI: lighter checks on pull requests, everything on main, nightly and releases - #137
Merged
Merged
Conversation
Pull requests run the lint, core tests, core isolation, pgrx tests on PG 15-18, the SQL harness, the Docker build, the packages job's first build and cargo-deny (advisories non-blocking), with Lifecycle, pg_upgrade (16 to 17) and beside-managed on PG 16 only. Pushes to main, the nightly schedule, dispatches and release-* PRs run every job and matrix cell, with advisories blocking. Documented in CONTRIBUTING.md. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012Rxfe2L3iVjSwSBPdUu1Ke
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.
Splits CI into two tiers, as agreed for 0.9.0 (#103).
Every pull request: fmt, Clippy + rustdoc, actionlint; warren-core tests and the core-isolation check; pgrx tests on PG 15–18 (with upgrade.py and dump.py); generators + SQL harness; cargo-deny bans/licenses/sources (blocking) and advisories (reported, not blocking); Lifecycle and beside-managed on PG 16; pg_upgrade 16→17; the Docker build; the packages job's first .deb build.
Full tier (push to main, nightly, workflow_dispatch, and release PRs, i.e. head branch
release-*): everything above plus every Lifecycle, pg_upgrade and beside-managed cell, the second .deb build, the vendored offline/reproducible build, segment decoder fuzzing, arm64 and macOS. Advisories block here.The tier test is
github.event_name != 'pull_request' || startsWith(github.head_ref, 'release-'), repeated where needed (a job'sif:andstrategycan't read workflow env); a header comment in ci.yml explains it. No job names change, but non-release PRs no longer report Lifecycle/beside-managed PG 15/17/18 or pg_upgrade 15→18 / 17→18, so those must not be required checks.CONTRIBUTING.md gains "What CI runs, and when"; CHANGELOG notes it under 0.9.0. actionlint is clean.
Generated by Claude Code