Skip to content

ci: adopt validated minimal EDB installer pin for PG14–18 - #10

Merged
ShutenOishi merged 1 commit into
mainfrom
ci/minimal-edb-pg14-18-20261016
Oct 15, 2026
Merged

ShutenOishi merged 1 commit into
mainfrom
ci/minimal-edb-pg14-18-20261016

Conversation

@ShutenOishi

Copy link
Copy Markdown
Contributor

PG14–18 minimal EDB installer: operator-authorized fleet rollout

One-file, one-line change: pin reusable pgextwin/build/.github/workflows/build-extension.yml from 455f0ccc667697f600700a6e64bcfd6c57b6a977 to 4adc71076283dc9cf64543b760c65b054f5a85f0 (accepted pilot plpgsql_check #43; shared builder build #110). This excludes pgAdmin/StackBuilder from EDB installation; preserves pinned PostgreSQL version, bounded Chocolatey retry, strict exit-code/headers/import-lib checks.

Gate before merge: exact PR head/base, protected main required Windows required summary from App15368 SUCCESS, PG14–18 Windows jobs and extension functional smoke SUCCESS, five actual newly generated PR-run Artifacts independently checked for outer/inner ZIP CRC, SHA256 vs SPDX2.3 SBOM-listed file hashes, Grype JSON and applicable policy, PACKAGE-INFO exact Run/ref/builder pin, proper package contents. Measure installer phase separate from external EDB download; report PG17 download outliers without bypassing any required test. Expected-head squash only after full PASS, and independent postmerge CI/Artifact audit afterwards. Any failed CI/integrity STOP; incomplete HOLD.

Existing unrelated candidate/Grype PRs are untouched. Manual Dispatch, signing, Publisher, Release, Tag, settings, Secrets, budget and branch-protection edits prohibited. Tracks Issue #46 and Issue #75.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant