ci: track and auto-merge @akalforge/pg-conformance updates - #198
Merged
Merged
Conversation
The Postgres conformance harness now takes its schema fingerprint and corpus from a shared package that publishes a patch on every merge to its own repository. `npm ci` installs strictly from the lockfile and ignores the range in package.json, so a published release reaches this repository only when something moves the lockfile. Dependabot rather than Renovate because Renovate needs a GitHub App installed against the org. Scoped twice over: dependabot.yml allows only this one dependency — the sole npm dependency in what is otherwise a Composer project — and the workflow independently refuses anything else. Only patch updates auto-merge; a minor or major means the fingerprint changed shape, which is when a human should look. `--auto` waits for every required check, including the conformance matrix across PostgreSQL 16, 17 and 18, so an update that broke this harness leaves the pull request open and red rather than landing. Co-Authored-By: Claude <noreply@anthropic.com>
|
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.
Closes the loop on the shared conformance data introduced in #196.
Why this is needed
npm ciinstalls strictly from the lockfile and ignores the range inpackage.json. So the shared package auto-publishing patches, plus~0.0.1here, achieves nothing on its own — the release succeeds and reaches nobody. Something has to move the lockfile, and droppingnpm ciwould trade reproducible installs for it.Dependabot, not Renovate
Renovate needs a GitHub App installed against the org. Dependabot is already available and does the same job here. Allow auto-merge also had to be enabled on the repo — that is a permission that lets a PR be marked merge-on-green, not a behaviour that merges anything by itself.
Scoped twice, deliberately
dependabot.ymlallows only@akalforge/pg-conformance— the sole npm dependency in what is otherwise a Composer project — and the workflow independently refuses anything else that reaches it.Only patch updates auto-merge. A minor or major means the fingerprint changed shape, which is exactly when a human should look.
Nothing merges blind
--autowaits for every required check, including the conformance matrix across PostgreSQL 16, 17 and 18. An update that broke this harness leaves the PR open and red rather than landing — and the upstream package already tests itself against PostgreSQL 14–18 before publishing, so a bad patch has to get past both.🤖 Generated with Claude Code