Skip to content

Third wave: complete PG14-18 Windows Releases for pgTAP, pg_variables and pg_store_plans #141

Closed
Closed
Third wave: complete PG14-18 Windows Releases for pgTAP, pg_variables and pg_store_plans#141

Description

@ShutenOishi
ShutenOishi
opened on Oct 19, 2026

Objective

Add pgTAP, pg_variables, pg_store_plans as three new pgextwin Windows x64 distributions for PG14, PG15, PG16, PG17, PG18. Keep PG14 only while lifecycle metadata says maintained (EOL 2026-11-12).

Implemented work

Open gates

  1. Review pilot job logs for all 15 combinations; fix real MSVC/SQL failures, run regression and keep PR feat: stage pgTAP, pg_variables and pg_store_plans for Windows PG14-18 #140 draft until validated.

  2. Provision pgextwin/pgtap, pgextwin/pg_variables, pgextwin/pg_store_plans repositories via authenticated GitHub GUI (GitHub connector in Chat does not expose repository creation); transfer per-repo staging directories with immutable source pins.

  3. Preserve existing required Windows summary check/branch protection and App15368 binding; run PR/full matrix, merge only after success, verify postmerge.

  4. Extend central candidate/watch allowlist after actual CI acceptance, preserving 0 0 * * * UTC and candidate vs publication authorization split.

  5. Formal signed/manual Promotion after immutable candidate+operator gates, public asset original bytes/SHA256/attestation verification; add verified Catalog entries and Japanese/English Website records, then audit live URLs.

  6. Preserve Issue 75 GO B/G4/G5 NO-GO and any unrelated publication deny. Never waive failed CI, expand secrets, budgets or protections.

Completion

Provide PG major matrix, exact upstream SHA, protected PR/postmerge Windows CI, release ID/URL, ZIP hashes and provenance status, Catalog/Website publication URLs per extension. A staged source tree, unsigned pilot or Draft PR is not a finished distribution.

Activity

  1. ShutenOishi commented on Oct 19, 2026

    @ShutenOishi
    ShutenOishi
    on Oct 19, 2026 – with ChatGPT Codex Connector
    ContributorAuthor

    Third-wave Windows pilot failure triage (2026-10-19 JST)

    • The first 15-way unsigned pilot run 39254783102 is FAILURE (15/15); no run has been waived or counted as success. https://github.com/pgextwin/build/actions/runs/39254783102
    • pgTAP PG14: CREATE EXTENSION and positive/intentional negative TAP functional SQL succeeded in the real Windows process, then package.ps1 failed at missing stage path; fixed by explicit absolute dist creation for all three.
    • pg_variables PG14-18: MSVC C2198 at pinned upstream pg_variables.c:1164 (MemoryContextMethods.stats invocation missing required print_to_stderr argument). Applied fail-closed guarded compatibility adjustment in disposable checkout.
    • pg_store_plans PG14-15: generated parser/gram.h absent in EDB Windows headers. Derived explicit PG14 and PG15 lexer token IDs from postgres/postgres REL_14_STABLE and REL_15_STABLE grammars and checked parsing against PG16 upstream known IDs. Added PG14/15-only token shim with bounded replacement.
    • pg_store_plans PG16-18: MSVC C2375 at pg_store_plans.c PG_FUNCTION_INFO_V1 export declarations. Added bounded PGDLLEXPORT decoration in temporary SHA-verified source, and removed redundant Windows unlink macro.
    • Source pins preserved, all extension configs require PG14-18, no central promotion/watch allowlist changes, candidate and formal Release still disabled until actual verified acceptance.
    • Corrected staging head: 731d5525ef7f95d497f723ddb5db57058e5c9e1b; protected Draft PR feat: stage pgTAP, pg_variables and pg_store_plans for Windows PG14-18 #140 remains open. The rerun static required Validate #39257829304 SUCCESS; rerun 15-way Windows pilot #39257829301 queued as of this record, not yet accepted.
    • New organization repos (pgtap, pg_variables, pg_store_plans), postmerge Windows, signed public Releases, public original-byte attestation/SHA, Catalog and Japanese/English Website all still uncompleted.

    Do not publish or mark complete from unsigned candidate evidence. Continue corrections per extension independently.

  2. ShutenOishi commented on Oct 19, 2026

    @ShutenOishi
    ShutenOishi
    on Oct 19, 2026 – with ChatGPT Codex Connector
    ContributorAuthor

    2026-10-19 UTC — resumed third-wave implementation; independent repair

    GET: build PR #140 head 8b4bf81 (Draft, unmerged); required Validate Run 39265611567 SUCCESS. Historical unsigned Pilot Run 39258338515: pgTAP 5/5 real Windows functional/ZIP success, pg_variables 0/5, pg_store_plans 0/5.

    Second unsigned Pilot Run 39264357663: pg_store_plans PG14/15/16 success (PG17/18 still running at evidence snapshot); pgTAP continues success. pg_variables failures: PG14/15 CREATE EXTENSION unable to find macro-generated variable_set_any; PG16 linker LNK2019 AssertArg. Source v1.2.1 has 18 macro-generated getter/setter PG_FUNCTION_INFO_V1 functions. Bounded SHA-pinned disposable checkout adjustment: replace AssertArg with Assert, collect and export 18 C function symbols + pg_finfo pairs, retain _PG_fini. Earlier fixes for PG14–18 heaptoast.h and MemoryContextMethods.stats are retained.

    New owner repos now exist, independently GET confirmed: pgextwin/pgtap, pgextwin/pg_variables, pgextwin/pg_store_plans. Created separate Draft protected-path PRs: pgextwin/pgtap#1 ; pgextwin/pg_variables#1 ; pgextwin/pg_store_plans#1 . All include immutable upstream SHA, PG14–18 manifest, Test Contract, reusable windows.yml, features, packaging and fail-closed disabled candidate+formal promotion.

    Current queued CI: repaired central Pilot Run https://github.com/pgextwin/build/actions/runs/39265611678 ; independent full Windows CI pgTAP https://github.com/pgextwin/pgtap/actions/runs/39265050945 ; pg_variables https://github.com/pgextwin/pg_variables/actions/runs/39265637108 ; pg_store_plans https://github.com/pgextwin/pg_store_plans/actions/runs/39265290641 . Report actual conclusions on fresh GET only.

    Hard safety blocker: all three newly created repository main branches currently report protected=false via GitHub branch GET. Existing GitHub connector cannot mutate branch protection; no merge, Release, Catalog or Website publication allowed before existing required CI/App15368 settings are installed and verified by authorized GUI. The branch-protection REST endpoint returned HTTP 403 for existing repos; preserve existing protections without guessing or weakening. No new external reviewer prerequisite. Signer/Publisher/policy gates untouched. No unsigned pilot counts as formal signed release.

    Next: consume exact failing Windows jobs only, patch each independently; verify dedicated Windows jobs and protection, then postmerge, authorized signed Promotion, public ZIP/SHA/attestation and downstream publish. PG14 maintained until 2026-11-12.

  3. ShutenOishi commented on Oct 19, 2026

    @ShutenOishi
    ShutenOishi
    on Oct 19, 2026 – with ChatGPT Codex Connector
    ContributorAuthor

    Third wave, 2026-10-19 — dedicated PR progress / actual evidence

    • pgTAP: PR Support PostgreSQL-major-specific upstream refs #1 MERGED, SHA fa176c872c9b801cef93019843eba61f54831e80, protected main=true; original exact-head Run 39265050945 SUCCESS, PG14/15/16/17/18 Windows 5/5 + Windows required summary SUCCESS. Postmerge 39271994163 launched, NOT accepted yet: Chocolatey HTTP 503 from community v2 feed, independent of extension output.
    • pg_store_plans: PR Support PostgreSQL-major-specific upstream refs #1 MERGED, SHA a45579103978f8c11d7943a8db1edcebaea2d87d, protected main=true; original exact-head Run 39265290641 SUCCESS, Windows PG14–18 5/5 plus required summary SUCCESS. Postmerge 39272028396 launched, NOT accepted yet: Chocolatey HTTP 503.
    • pg_variables: PR Support PostgreSQL-major-specific upstream refs #1 OPEN/DRAFT, latest head 9b78696ea7041345a782e95dae04ee516bc6523c. Source compile and CREATE EXTENSION passed original Windows PG14–18 CI but its asynchronous concurrent session smoke check failed. Cause: malformed literal DO $ ... END $;; corrected to PostgreSQL DO $$ ... END $$;, added writer-session job diagnostics. Latest Run 39271680274 first attempt hit external Chocolatey 503 across majors before functional test. Used GitHub re-run failed jobs only to start attempt 2; outcome not yet accepted.
    • Central build PR #140 remains DRAFT, run 39265611678 FAILURE, multiple fail jobs due broken original concurrent SQL test or subsequent Chocolatey 503. The code fix is applied to dedicated pg_variables PR, but not yet synced to staging; must keep comparison exact and not claim central 15/15 success.
    • Public-source recovery: previously independently verified SHA256 of all five EDB PG14–18 EXE installer bytes is frozen at issue 75 evidence. Direct-EDB alternative must validate the actual downloaded SHA256 and required server runtime; do not treat historic byte source integrity as installer runtime or signing proof.
    • All four main branches GET protected=true (GitHub protection policy details GET 403); no branch protection changed and no required CI waived. Postmerge failure is failure, not accepted; signed Promotion, published releases, Catalog/Website still unexecuted and unauthorized. Preserve Issue Eliminate Work-only Dispatch: Chat-authorized Release trigger and automatic Catalog proposal #75 GO B/G4/G5 deny and no secret/budget changes.

    Next: await exact attempt-2 Windows logs for pg_variables; fix if functional failure, merge only after exact-head 5/5+summary, then postmerge. Once Chocolatey feed recovers, use failed-jobs-only retries for two independently merged postmerge runs. No formal Release until required independent signer/publisher operator gate passes.

  4. ShutenOishi commented on Oct 19, 2026

    @ShutenOishi
    ShutenOishi
    on Oct 19, 2026 – with ChatGPT Codex Connector
    ContributorAuthor

    Chocolatey HTTP 503 recovery — actionable follow-up (2026-10-19 UTC)

    • Postmerge Windows CI on merged pgTAP main fa176c872c9b801cef93019843eba61f54831e80: https://github.com/pgextwin/pgtap/actions/runs/39271994163 — FAILURE for externally unavailable Chocolatey community V2 package feed (HTTP 503) on several majors; exact-head PR Run 39265050945 5/5 SUCCESS is preserved and NOT substituted for postmerge.
    • Postmerge pg_store_plans main a45579103978f8c11d7943a8db1edcebaea2d87d: https://github.com/pgextwin/pg_store_plans/actions/runs/39272028396 — same external HTTP 503; original protected PR Run 39265290641 5/5 SUCCESS.
    • pg_variables PR Support PostgreSQL-major-specific upstream refs #1 head 9b78696ea7041345a782e95dae04ee516bc6523c: re-run only failed jobs, Run 39271680274 attempt 2; all 5 Windows installs blocked by Chocolatey V2 HTTP 503, before repaired concurrent-live-session smoke. No smoke success claim; PR stays Draft.
    • Proactive, safe alternative implemented, not yet accepted: protected Draft fix: SHA256-verified EDB fallback for Chocolatey 503 on Windows PG14–18 #142. Normal Chocolatey server+CLI install unchanged; on bounded registry failure only, fetch exactly one matching EDB PG14–18 Windows EXE from HTTPS, verify exact historical independently witnessed byte count + SHA256 for that major BEFORE unattended execution, reject version/source/hash/bytes/install/runtime mismatch and delete download. These five fixed hashes come from immutable successful Issue Eliminate Work-only Dispatch: Chat-authorized Release trigger and automatic Catalog proposal #75 Runs 39038000517 and 39038162434; it is not evidence of Signed Publisher or Release authorization. Five-major Windows real bootstrap canary workflow added; current Validate resolver was adjusted without deleting the safety assertion (checks all five literal source pins, size, SHA, safe execution order and failure rules). CI: resolver Run 39273781739 SUCCESS; canary Run 39273781729 still running, unaccepted.
    • No merge of fix: SHA256-verified EDB fallback for Chocolatey 503 on Windows PG14–18 #142 or retargeting of required reusable workflow until independent canary succeeds and PR branch/protection gates pass. No reduction of CI, branch protection or formal Release safeguards; GO B/G4/G5 remain NO-GO. Failure status never waived.

    Until canary confirms the fallback path, keep product releases and Catalog/Website unmodified.

  5. ShutenOishi commented on Oct 19, 2026

    @ShutenOishi
    ShutenOishi
    on Oct 19, 2026 – with ChatGPT Codex Connector
    ContributorAuthor

    2026-10-19 — independent byte-pinned recovery verified and tagged-dollar SQL fix

    Next dependency: once exact-head #142 Windows canary 5/5 + repaired PG14 feature test + resolver all succeed, mark #142 ready and merge through protection; then retarget just the three third-wave per-repo reusable Windows workflow SHA through protected PRs to use the vetted fallback. Verify full 5-major Windows and postmerge; formal signed Release still requires existing explicit operator/central authorization.

  6. ShutenOishi commented on Oct 19, 2026

    @ShutenOishi
    ShutenOishi
    on Oct 19, 2026 – with ChatGPT Codex Connector
    ContributorAuthor

    Third-wave recovery, 2026-10-19 UTC — current verified facts

    • Two protected merges already complete: pgtap Support PostgreSQL-major-specific upstream refs #1 => main fa176c872c9b801cef93019843eba61f54831e80; pg_store_plans Support PostgreSQL-major-specific upstream refs #1 => main a45579103978f8c11d7943a8db1edcebaea2d87d. Dedicated PR CI exactly PG14–18 5/5 + Windows required summary SUCCESS (Run 39265050945 and 39265290641). Postmerge Runs 39271994163 / 39272028396 FAILED transient Chocolatey community V2 HTTP 503: do not count PR success as postmerge success.
    • pg_variables Support PostgreSQL-major-specific upstream refs #1 remains DRAFT/unmerged. Source HEAD 0fb14eac695b3aa530a7cfd18637c741157354f8 fixes malformed PL/pgSQL inline dollar-quote using tagged DO $pgextwin$ ... END $pgextwin$;. Separate real Windows PG14 concurrent-two-backend Run 39275675522 SUCCESS with exact HEAD; both writer persistence and session isolation witnessed. Dedicated full CI 39275557754 failed Chocolatey registry HTTP 503 before functional test. Do not merge until full required matrix CI.
    • Protected Draft build PR fix: SHA256-verified EDB fallback for Chocolatey 503 on Windows PG14–18 #142 link implements fail-closed recovery: Chocolatey bounded 3 attempts first; only each attempt an exact community.chocolatey.org/api/v2/ response HTTP 502/503/504 permits EDB fallback. EDB PG14–18 installation EXEs constrained by pinned version, URL, actual byte count and exact SHA256 from independently successful historical Issue 75 byte acquisition; rejected on any mismatch, zero publication permission. PG14–18 original fallback canary Run 39273568420 5/5 SUCCESS including server start and actual SQL. This Run is historical earlier implementation; current strict 502/503/504 guard is undergoing new five-major tests.
    • Latest PR fix: SHA256-verified EDB fallback for Chocolatey 503 on Windows PG14–18 #142 source HEAD at last GET bb92f6411fe6d115f94bf964b77164095b7f0ad3 including updated offline guard tests. Required Validate Run 39276523696 and PG14–18 Windows canary Run 39276523443 started; NOT YET accepted. Last major negative found real 503,503,504 on PG15, prompting minimal safer 502/503/504 extension; 404, wrong package, hash/size mismatch and binary failure DENY.
    • Prepared branches in pgtap/pg_store_plans to adopt immutable merged build SHA once fix: SHA256-verified EDB fallback for Chocolatey 503 on Windows PG14–18 #142 passes all gates. No new code changes in either previously-successful extension.
    • No Release, Catalog/Website mutations while postmerge/no valid promotion receipt. Keep Issue 75 GO B/G4/G5 NO-GO and all signer/publisher controls unchanged.

  7. ShutenOishi commented on Oct 19, 2026

    @ShutenOishi
    ShutenOishi
    on Oct 19, 2026 – with ChatGPT Codex Connector
    ContributorAuthor

    Third-wave update — live CI actions, 2026-10-19 15:21 UTC

    Verified independent EDB fallback Run 39273568420: five PG14–18 Windows canary jobs SUCCESS, each with actual installer original size/SHA256 check and real PostgreSQL initdb/server/SQL. This historic Run predates latest narrowly-scoped gateway classifier.

    Recovered pg_variables real PG14 feature evidence Run 39275675522: SUCCESS; actual SQL confirms live first backend retains variable while a concurrent second backend cannot see it. Source PR #1 has corrected tagged DO $pgextwin$ ... END $pgextwin$;, head 0fb14eac695b3aa530a7cfd18637c741157354f8. Its full five-major PR Run 39275557754 FAIL due Chocolatey HTTP 503 before feature tests; remains DRAFT, NOT accepted.

    Protected Draft build PR #142 now narrows fallback to observed exact Chocolatey community V2 HTTP 502, 503, or 504 on each of three bounded attempts; no 404/non-feed failures or EXE byte/hash/version drift accepted. This addresses a fresh original PG15 Run where gateway errors went 503,503,504 and strict 503-only classifier correctly DENIED. Current head bb92f6411fe6d115f94bf964b77164095b7f0ad3: required Validate 39276523696 SUCCESS; exact-head Windows five-PG canary 39276523443 and separate pg_variables live check 39276523570 IN PROGRESS. Do not merge until successful.

    pgTAP and pg_store_plans original protected main merges remain valid; postmerge failed external Chocolatey fetch and cannot be credited. Created isolated branches fix/windows-edb-503-resilience in both protected repos; will pin exact postmerge build SHA through new required-checked PRs after PR #142 is accepted. No changes to original successful source, no promotion or published Release, no Catalog/Website. Existing signed publication and Issue #75 GO B/G4/G5 restrictions unchanged.

  8. ShutenOishi commented on Oct 19, 2026

    @ShutenOishi
    ShutenOishi
    on Oct 19, 2026 – with ChatGPT Codex Connector
    ContributorAuthor

    Verified exact-head recovery feature canary 39276523570 SUCCESS (PG14 real Windows, source head bb92f6411fe6d115f94bf964b77164095b7f0ad3, pg_variables source exact 0fb14eac695b3aa530a7cfd18637c741157354f8). This supplements independently successful earlier 39275675522. The latest fail-closed V2 HTTP 502/503/504 EDB fallback canary 39276523443 has PG14 and PG15 SUCCESS, PG16/17 running, PG18 queued (at evidence snapshot); required Validate 39276523696 SUCCESS. Do not promote current head until full five-major result accepted and protected PR merged.

  9. ShutenOishi commented on Oct 19, 2026

    @ShutenOishi
    ShutenOishi
    on Oct 19, 2026 – with ChatGPT Codex Connector
    ContributorAuthor

    2026-10-19 15:42 UTC — PR #142 safely merged; 3 dedicated recovery PR checks launched

    • build PR #142 MERGED by protected squash, build/main=a25419dc28026960ac5776e747e3760d19b5cd27 (GET-verified protected=true). Previous exact source head bb92f6411fe6d115f94bf964b77164095b7f0ad3 has Windows canary Run 39276523443 COMPLETED SUCCESS, PG14–18 5/5, each App15368 check conclusion SUCCESS. Required Validate Run 39276523696 SUCCESS and real pg_variables PG14 concurrent backend Run 39276523570 SUCCESS. PG14 logs witness 503/503/503 before original EDB EXE size/SHA256 PASS and live server/SQL PASS. This does not authorize a Release or replace third-wave postmerge.
    • New build/main push postmerge Validate Run 39279650204 QUEUED at this snapshot; verify separately before final accept.
    • Pinned exactly one workflow SHA per dedicated extension to immutable new build/main a25419dc28026960ac5776e747e3760d19b5cd27, preserving original feature tests, packaging, gates, permissions and prior failures. pgTAP Draft PR #2 head d493c736f1a5e23d05357e4a56206b5a4217f624, new Run 39279858282 QUEUED. pg_store_plans Draft PR #2 head 1e2f4a36f3d56726499a0a00f5849ad59805facc, new Run 39279865438 QUEUED. pg_variables Draft PR #1 updated head 6cecb39e82c4c1024692def2572a8b9a557149c2, new Run 39279829460 QUEUED.
    • Required next acceptance: successful exact-head 5/5 dedicated Windows checks + Windows required summary per extension; mark ready and protected merge; independent main push postmerge; then separate manual signed candidate/Promotion receipt and Release authorization before publication. No Release/Catalog/Website completed. Prior failed Run 39271994163 / 39272028396 / 39275557754 remain FAILURE; Issue Eliminate Work-only Dispatch: Chat-authorized Release trigger and automatic Catalog proposal #75 GO B/G4/G5 NO-GO and all existing publisher gates unchanged.

  10. ShutenOishi commented on Oct 19, 2026

    @ShutenOishi
    ShutenOishi
    on Oct 19, 2026 – with ChatGPT Codex Connector
    ContributorAuthor

    2026-10-19 15:50 UTC — staging superseded, asynchronous CI queue remains

    Closed obsolete nonmerged build Draft PR #140 with supersession note; its historical 15-matrix failed pilot is preserved but stale staging templates must not be merged into live build. The dedicated repos own current source, and merged build PR #142 owns the tested Chocolatey outage recovery.

    Latest repeated GET shows build postmerge Validate 39279650204, pgtap PR #2 Run 39279858282, pg_variables PR #1 Run 39279829460, and pg_store_plans PR #2 Run 39279865438 all QUEUED, with all fifteen Windows major jobs created; no new PASS/FAIL claim, no rerun or check bypass. Retain Drafts until exact-head jobs and Windows required summary complete; independently verify protected postmerge on each main.

    Current local config/release-promotion.json in all three extension repositories has enabled: false and releasePolicy: manual-dispatch; operator candidate/receipt/PUBLISH gates do not yet hold. Therefore formal Release/Catalog/Website remains DENY regardless of earlier CI evidence. No policy change, Secrets, runner/budget, branch protection, publisher or Issue #75 GO B/G4/G5 gate changed.

  11. ShutenOishi commented on Oct 19, 2026

    @ShutenOishi
    ShutenOishi
    on Oct 19, 2026 – with ChatGPT Codex Connector
    ContributorAuthor

    2026-10-20 JST — exact-head CI queue audit / upstream GitHub Actions incident

    Latest fresh GET of protected current PRs and runs:

    GitHub's official status at https://www.githubstatus.com/ reports an active Incident with Actions and Pages (investigating since 2026-10-19 15:49 UTC), with Actions and Pages degraded and Webhooks degraded by 15:50 UTC. This is consistent with the persistent queue backlog, though it does not independently prove each run's scheduling cause. No failing job logs or new source defect yet. Avoid duplicate reruns and unproven fixes; await actual job conclusions then advance each PR independently through protected required CI, exact-head merge and postmerge. All three PRs remain Draft/unmerged. No Release, Catalog or Website. Preserve disabled/manual-only Promotion and Issue #75 GO B/G4/G5 NO-GO. Previous successful #142 exact-head canary and protected merge unchanged.

  12. ShutenOishi commented on Oct 19, 2026

    @ShutenOishi
    ShutenOishi
    on Oct 19, 2026 – with ChatGPT Codex Connector
    ContributorAuthor

    Third wave protected merges complete — 2026-10-20 JST

    Latest GET independently confirms all four previously pending validation runs are now COMPLETED SUCCESS: build/main postmerge Validate 39279650204 exact head a25419dc28026960ac5776e747e3760d19b5cd27 (push, attempt 1, resolver SUCCESS; PR-only jobs SKIPPED and not counted), and each dedicated full PG14–18 Windows run has 5/5 SUCCESS plus Windows required summary SUCCESS, all GitHub Actions App 15368: pgtap 39279858282, head d493c736f1a5e23d05357e4a56206b5a4217f624; pg_variables 39279829460, head 6cecb39e82c4c1024692def2572a8b9a557149c2; pg_store_plans 39279865438, head 1e2f4a36f3d56726499a0a00f5849ad59805facc.

    After fresh exact-head GET and protected=true checks, all three Draft PRs were marked ready and merged with GitHub's expected_head_sha CAS and squash strategy. GET confirmed PR state MERGED, main protected=true, and main HEAD equals merge result in each repository:

    Not yet postmerge accepted: all three fresh main push runs must independently complete PG14–18 5/5 SUCCESS plus Windows required summary. Do not treat earlier PR checks as main push evidence. Previously failed old postmerge Runs remain FAILURE. config/release-promotion.json is enabled:false, releasePolicy:manual-dispatch for each extension; manual candidate/Promotion, signature, origin, independent signed publication and Issue #75 GO B/G4/G5 NO-GO remain untouched. No Release, Catalog, Website authorization or claim until gates actually met.

  13. ShutenOishi commented on Oct 19, 2026

    @ShutenOishi
    ShutenOishi
    on Oct 19, 2026 – with ChatGPT Codex Connector
    ContributorAuthor

    2026-10-20 JST — third-wave Windows protected merges and independent postmerge ACCEPTED

    All three third-wave extension repositories have completed protected PR merge and independent main/push postmerge Windows CI, without rerunning prior successful jobs or waiving any failed runs.

    Prerequisite: common build/main=a25419dc28026960ac5776e747e3760d19b5cd27 protected merge PR #142, postmerge Validate Run 39279650204 COMPLETED SUCCESS. Exact-head shared installer Windows PG14–18 canary 39276523443 5/5 SUCCESS; pg_variables concurrent-backend feature recovery 39276523570 SUCCESS.

    Extension Protected ready+merge Protected main SHA after GET Independent main/push postmerge Run PG14–18 Windows Windows required summary 5 postmerge job artifacts
    pgTAP PR #2 MERGED 72ddb050cb65d529321c5001d4ef817164f56c78 39329554117 SUCCESS 5/5 SUCCESS SUCCESS pgtap-pg14...pg18-windows-x64 present and unexpired
    pg_variables PR #1 MERGED f3bbe5f707f20fe1d4a6057b6547ce109128cdf4 39329574676 SUCCESS 5/5 SUCCESS SUCCESS pg_variables-pg14...pg18-windows-x64 present and unexpired
    pg_store_plans PR #2 MERGED d855046fed3de95cda0fb69164d8f5fe93f76f1c 39329563882 SUCCESS 5/5 SUCCESS SUCCESS pg_store_plans-pg14...pg18-windows-x64 present and unexpired

    All 15 Windows postmerge jobs + three App15368 Windows required summary checks were GET-verified conclusion=success; each parent Run is event=push, status=completed, conclusion=success, head_sha matches current protected main. Five distinct GitHub Actions artifacts returned per repo (total 15). These are unsigned CI artifacts, not published signed Releases.

    Prior failing runs remain historic failures and are not converted: pgtap 39271994163, pg_store_plans 39272028396, pg_variables 39275557754. The newer successful postmerge runs independently supersede those failures for current main.

    Remaining separate publication gates (DENY until fulfilled): All three config/candidate-build.json currently have enabled:false, releasePolicy:manual-only, and config/release-promotion.json have enabled:false, releasePolicy:manual-dispatch. GitHub Releases list was empty in all three when GET-checked. No independent signed release ZIP, original-byte SHA256, signature/provenance/attestation proof, Catalog record or bilingual Website publication is accepted from these CI-only results. Existing exact candidate approval, operator manual PUBLISH, signer/publisher permissions and Issue #75 GO B/G4/G5 NO-GO remain unchanged. Do not bypass any formal gate or report Release/Catalog/Website completed. The Windows build/feature/postmerge portion is now COMPLETE.

  14. ShutenOishi commented on Oct 19, 2026

    @ShutenOishi
    ShutenOishi
    on Oct 19, 2026 – with ChatGPT Codex Connector
    ContributorAuthor

    Third-wave central candidate fleet — protected merge and postmerge verified (2026-10-20 JST)

    Result: pgextwin/build PR #143 was marked ready and successfully squash-merged with expected_head_sha=21663520d75d40d920b7614661cf9eeb5fa6b482. Main branch is protected and GET now confirms f1ae00aa01e677eca9818f7f2206f8a598f4b3d1.

    Remaining gating: safe separate local candidate opt-in and signed immutable candidate decision/audit, independent release identity/publisher migration and authorization, Issue #75 GO B/G4/G5 NO-GO, explicit authenticated human PUBLISH, verified signed public assets and Catalog/Website promotion. Formal Release remains DENY / not published.

  15. ShutenOishi commented on Oct 19, 2026

    @ShutenOishi
    ShutenOishi
    on Oct 19, 2026 – with ChatGPT Codex Connector
    ContributorAuthor

    Third-wave local candidate opt-in: all three protected merges + postmerge 15/15 SUCCESS (2026-10-20 JST)

    Each change is limited to config/candidate-build.json enabled:false -> true, retaining releasePolicy:manual-only, existing manually dispatched update-watch.yml (human UPDATE/exact SHA) and local formal Promotion enabled:false. Central formal operator-PUBLISH allowlist remains exactly 14, without any new formal Release authority.

    Repo Protected candidate opt-in PR Premerge Windows required summary Protected squash main SHA Exact-main postmerge Windows run
    pgextwin/pgtap pgextwin/pgtap#3 https://github.com/pgextwin/pgtap/actions/runs/39337086551 SUCCESS PG14–18 5/5 + App15368 required summary 0a59b2cf33001b162277064a58cfb30843b702e7 https://github.com/pgextwin/pgtap/actions/runs/39337807839 COMPLETED/SUCCESS attempt1, push, PG14–18 5/5 + App15368 summary SUCCESS
    pgextwin/pg_variables pgextwin/pg_variables#2 https://github.com/pgextwin/pg_variables/actions/runs/39337093551 SUCCESS PG14–18 5/5 + App15368 required summary 5c60e509de1bbba093d64a2be7b4dcf1f3925579 https://github.com/pgextwin/pg_variables/actions/runs/39337815311 COMPLETED/SUCCESS attempt1, push, PG14–18 5/5 + App15368 summary SUCCESS
    pgextwin/pg_store_plans pgextwin/pg_store_plans#3 https://github.com/pgextwin/pg_store_plans/actions/runs/39337098222 SUCCESS PG14–18 5/5 + App15368 required summary bec5eb32b720758efc62646d6991b9206116fcb8 https://github.com/pgextwin/pg_store_plans/actions/runs/39337890971 COMPLETED/SUCCESS attempt1, push, PG14–18 5/5 + App15368 summary SUCCESS

    Central prerequisite build PR #143 protected/postmerge complete: #141 (comment).

    Catalog first-release preparation: pgextwin/catalog#133 remains in progress. Initial Validate run https://github.com/pgextwin/catalog/actions/runs/39338388530 FAILED (not waived): unintentional interaction with the historical published-14 audit and one pg_store_plans synthetic preload mismatch. Subsequent commits separate historical ALLOWED 14 from verification-only INTAKE_ALLOWED 17, retaining historical immutable gates, and fix the fixture; the new exact-head CI is pending verification.

    Security state: No candidate dispatch / no immutable candidate audit / no explicit human formal PUBLISH, no signed public third-wave Release (GitHub Releases GET returned 0/3), no genuine ZIP/attestation public validation, no Catalog/Website publication. Issue #75 GO B/G4/G5 NO-GO stays in force; formal Release DENY.

  16. 129 remaining items

  17. ShutenOishi
    added sub-issues on Oct 31, 2026
  18. ShutenOishi
    removed sub-issues on Oct 31, 2026
  19. ShutenOishi
    added a sub-issue on Oct 31, 2026
  20. ShutenOishi
    removed sub-issues on Oct 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions