Skip to content

Fix immutable OIDC subjects for new repositories - #25

Merged
AppSolves merged 1 commit into
mainfrom
fix/immutable-oidc-subjects
Nov 15, 2026
Merged

AppSolves merged 1 commit into
mainfrom
fix/immutable-oidc-subjects

Conversation

@AppSolves

Copy link
Copy Markdown
Owner

New repositories use GitHub’s immutable default OIDC subject (repo:OWNER@OWNER_ID/REPO@REPO_ID:environment:ENV). A disposable live acceptance run failed both prepare and publish with oidc_subject_mismatch: repository OIDC metadata confirmed this new default, while the broker only accepted the legacy name-only format. No inference ran.

Accept exactly the documented immutable default alongside the legacy default. Derive both numeric IDs and names from the already verified expected tenant; keep exact Environment encoding and all issuer, audience, signature, caller/ref, immutable reusable workflow, actor/run and dispatch checks. Custom templates and wrong IDs remain rejected. No secret, session, migration, runner or reusable-workflow change; keep the synchronized trusted review SHA unchanged.

Validation: full Node 24 check (195 tests), including cryptographically signed immutable subjects for review/publish and encoded Environments, negative wrong owner/repository IDs and names, extra suffixes, stage and workflow mismatches. Full GitHub CI remains required before the authorized normal merge/deployment.

Official contract: https://docs.github.com/en/actions/reference/security/oidc#immutable-subject-claims

@AppSolves
AppSolves merged commit b15163e into main Nov 15, 2026
4 checks passed
@AppSolves
AppSolves deleted the fix/immutable-oidc-subjects branch November 15, 2026 02:41
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