GitHub Actions OIDC token remains valid after job sleep period – unexpected authentication behavior
Goal To determine whether the OIDC identity token that GitHub Actions supplies is automatically refreshed when a single job contains a long‑running step that exceeds the token’s nominal lifetime. Scenario A workflow obtains an OIDC token, exchanges it for AWS STS credentials, sleeps for 12 minutes, and then makes a second AWS API call. Constraints The token