{"version":"2.1.239","anchor":"github-actions-input-copies-of-secret-variables-are-now-scru","canonical_anchor":"github-actions-input-copies-of-secret-variables-are-now-scru","heading":"GitHub Actions input copies of secret variables are now scrubbed too","tier":"notice","area":"Secret Scrubbing","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/github-actions-input-copies-of-secret-variables-are-now-scru","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### GitHub Actions input copies of secret variables are now scrubbed too\n\nGitHub Actions INPUT_-prefixed copies of secret variables are now scrubbed too.\n\n**What**\n\nThe list of environment variables Claude Code refuses to expose now also covers the `INPUT_`-prefixed copy of each one, which is the form GitHub Actions uses when a secret is passed in as a workflow input.\n\n**Details**\n\n- The base list already included `ANTHROPIC_AUTH_TOKEN`, `AWS_SESSION_TOKEN`, `ACTIONS_RUNTIME_TOKEN` and `SSH_SIGNING_KEY` among others.\n- The prefixed names are built at runtime from the base list, so any future addition to the denylist is covered automatically.\n\n**Evidence**\n\n`ACTIONS_RUNTIME_TOKEN`\n\n- Area: Secret Scrubbing\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}