Skip to content

ci: deploy shared Grype safety and read-only Release tag proposal (#235) - #20

Merged
ShutenOishi merged 1 commit into
mainfrom
feat/issue75-tag-grype-central235
Oct 23, 2026
Merged

ShutenOishi merged 1 commit into
mainfrom
feat/issue75-tag-grype-central235

Conversation

@ShutenOishi

Copy link
Copy Markdown
Contributor

Issue #75 — Deploy already-protected central build PR #234 Grype Critical/High/Unknown fail-closed risk classification and PR #235 read-only next Windows tag proposal as ONE atomic version update of existing shared signed-candidate read-only workflow. Central required CI and real main/push validated: build/main 304cd5d473b5b48e56d7988b55630e46d767f6d0. This is an immutable SHA-only caller change (plpgsql_check also updates exactly matching SHA regression). Original previous 17/17 #233 caller Windows postmerge accepted and NOT rerun. Existing policies and signing attestations unchanged. No automatic Publisher authorization, Tag or Release, no new App/Secret/GUI; PUBLISH_DENY and GO B/G4/G5 NO_GO preserved. Require App15368 real PG14–18 5/5, resolver, Windows required summary and normal protected merge + real postmerge.

@ShutenOishi
ShutenOishi merged commit 618f925 into main Oct 23, 2026
8 checks passed
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