fix(deps): bump github.com/urfave/cli/v3 from 3.9.1 to 3.10.1 - #80
Merged
github-actions[bot] merged 1 commit intoJul 29, 2026
Merged
Conversation
Bumps [github.com/urfave/cli/v3](https://github.com/urfave/cli) from 3.9.1 to 3.10.1. - [Release notes](https://github.com/urfave/cli/releases) - [Changelog](https://github.com/urfave/cli/blob/main/docs/CHANGELOG.md) - [Commits](urfave/cli@v3.9.1...v3.10.1) --- updated-dependencies: - dependency-name: github.com/urfave/cli/v3 dependency-version: 3.10.1 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
github-actions
Bot
deleted the
dependabot/go_modules/github.com/urfave/cli/v3-3.10.1
branch
July 29, 2026 00:45
dantech2000
added a commit
that referenced
this pull request
Jul 29, 2026
Auto-merge worked, but merged with secrets.GITHUB_TOKEN. GitHub deliberately does not trigger workflows from pushes made with GITHUB_TOKEN -- it is the built-in recursion guard -- so every auto-merged dependency bump landed on main with no Test run, no Lint run, and no Release Please run. Two consequences, both silent. main went untested after each bump: #80, #81, #86, #88, #90 and #95 all merged with zero workflow runs against the resulting commits. And `fix(deps)` commits never cut a release, which defeats the whole point of 59d889c -- the prefix was right, but the workflow that acts on it was never invoked. Confirmed via `gh pr view 81 --json mergedBy` -> app/github-actions, and `gh run list --commit <sha>` returning empty for every auto-merged commit. Switch only the merge step to GH_PAT so the merge is attributed to a real user and downstream workflows fire. release-please.yml already uses GH_PAT for this exact reason. The other four steps stay on the scoped, auto-rotating GITHUB_TOKEN: they only read Dependabot metadata and check results, so there is no reason to widen their credentials. Verified current main locally in the meantime, since CI never did: task dev:full passes and govulncheck reports no vulnerabilities.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps github.com/urfave/cli/v3 from 3.9.1 to 3.10.1.
Release notes
Sourced from github.com/urfave/cli/v3's releases.
Commits
c5f123bMerge pull request #2322 from lihan3238/fix-22498449859Merge branch 'main' into fix-224902bdfb0Merge pull request #2374 from urfave/fix/completion-subcommand-order49e84c0Merge pull request #2330 from c-tonneslan/fix/version-alias-conflict-with-use...54d38c9v3: yield the version flag's -v alias to a user-defined flag0242574Merge pull request #2369 from urfave/fix/gfmrun-count-and-examples80f2625test: explain why completionShells is mutated in completion error tests0045bbdfix: keep completion subcommand order deterministic in help outputf980ca8Merge pull request #2371 from urfave/dependabot/github_actions/actions/checko...b5e4348chore(deps): bump actions/checkout from 6 to 7Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)