GitHub announced a secret scanning audit log change taking effect on November 12, 2026. In affected secret_scanning_alert.* and secret_scanning_push_protection.bypass events, the business field will contain the enterprise slug instead of its display name.
Teams whose integrations filter events by display name should update them before rollout to accept both formats or use business_id. The business field will remain a string; event names and numeric business_id values will stay unchanged.
Separately, GitHub expanded its existing token revocation action to Base64-encoded PATs, OAuth tokens and GitHub App user access tokens. That capability remains in public preview and works in private and internal github.com repositories with secret scanning enabled.
Choose a sign-in method or comment as a guest below.