ci: replace stale dependabot guards with renovate#2661
Conversation
The repo uses Renovate (see .github/renovate.json), so the `github.actor != 'dependabot[bot]'` guards in our workflows no longer match the bot opening PRs. Update ci.yml to skip the sign-plugin, Knip report, and release steps for `renovate[bot]` instead, and drop the dependabot guard from check-labels.yml so the action runs on Renovate PRs (its JS already handles `renovate[bot]` internally).
|
Hello! 👋 This repository uses Auto for releasing packages using PR labels. ✨ This PR can be merged. It will not be considered when calculating future versions of the npm packages and will not appear in the changelogs. |
There was a problem hiding this comment.
Pull request overview
Replaces stale dependabot[bot] actor guards with renovate[bot] in CI workflows, and drops a now-redundant job-level guard in check-labels.yml since the inner action already has a Renovate code path. Intended to restore the original protective intent of these guards after the repo switched from Dependabot to Renovate.
Changes:
- Update three actor guards in
.github/workflows/ci.yml(sign-plugin step, Frontend Knip Report step, release job) fromdependabot[bot]torenovate[bot]. - Remove the job-level
dependabot[bot]guard in.github/workflows/check-labels.yml, deferring to the action's internal Renovate handling.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| .github/workflows/ci.yml | Swap dependabot actor guards for renovate on sign-plugin, Knip report, and release job |
| .github/workflows/check-labels.yml | Drop job-level dependabot guard; rely on action's built-in Renovate path |
Concern: Recent repo history (CHANGELOG.md, README.md, .autorc) indicates the active Renovate bot identity is renovate-sh-app[bot], not renovate[bot]. If so, the new guards will be no-ops (same problem as before), and the check-labels removal will surface missing-label errors on Renovate PRs.
The active Renovate identity in this repo is `renovate-sh-app[bot]` (verified against recent PRs #2634, #2625, #2623); `renovate[bot]` only appears in older history. The previous patch using `renovate[bot]` alone would have been a no-op for current Renovate PRs. Match both identities in the sign-plugin, Frontend Knip Report, and release-job guards in ci.yml so the original protective intent works for the active bot while staying backward-compatible with the legacy identity.
The active Renovate bot in this repo is `renovate-sh-app[bot]`, so the existing `userName === 'renovate[bot]'` fast-path never matched and Renovate PRs were falling through to the missing-semver-label error path. Match both identities so the auto-labelling logic (no-changelog for lock-only changes, patch otherwise) actually runs for current Renovate PRs while remaining backward-compatible with the legacy `renovate[bot]` identity. Required follow-up to PR #2661, which dropped the workflow-level dependabot guard and exposed this pre-existing bug.
What changed?
Replaced the stale
github.actor != 'dependabot[bot]'guards in our GitHub workflows withrenovate[bot]- I think this makes sense as we don't rely on dependabot for things like this now?