Skip to content

fix: update token for bot_updater - #244

Merged
marcossevilla merged 1 commit into
mainfrom
fix/bot-updater-token
Oct 9, 2026
Merged

marcossevilla merged 1 commit into
mainfrom
fix/bot-updater-token

Conversation

@marcossevilla

Copy link
Copy Markdown
Member

Status

READY

Description

The bot_update_exclusions workflow has failed on 199 of its last 200 runs (the only success, on 2026-08-17, was a run with nothing to change):

##[error]Input 'token' not supplied. Unable to continue.

Both create-pull-request steps use ${{ steps.generate-token.outputs.token }}, but no step has id: generate-token (the reference came in with #178). The expression evaluates to an empty string. So whenever the bot found drift, it never opened a PR, and the README excluded-rules table went stale (fixed in #243). The deprecated-rules step comes after the failing step, so it never ran either.

This switches both steps to the org's VGV_BOT_PAT secret, which is what very_good_cli's bot workflows use.

Type of Change

  • ✨ New feature (non-breaking change which adds functionality)
  • 🛠️ Bug fix (non-breaking change which fixes an issue)
  • ❌ Breaking change (fix or feature that would cause existing functionality to change)
  • 🧹 Code refactor
  • ✅ Build configuration change
  • 📝 Documentation
  • 🗑️ Chore

The workflow referenced steps.generate-token.outputs.token, but no step with that id exists (introduced in #178). create-pull-request fails with "Input 'token' not supplied", so the excluded rules table and deprecated rules were never updated automatically.
@marcossevilla marcossevilla changed the title fix: use VGV_BOT_PAT in bot_updater workflow fix: update token for bot_updater Oct 9, 2026
@marcossevilla
marcossevilla merged commit bb0e340 into main Oct 9, 2026
5 checks passed
@marcossevilla
marcossevilla deleted the fix/bot-updater-token branch October 9, 2026 13:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Development

Successfully merging this pull request may close these issues.

2 participants