fix(deps): bump github.com/aws/aws-sdk-go-v2/service/cloudwatch from 1.59.0 to 1.66.0 - #95
Merged
github-actions[bot] merged 1 commit intoJul 29, 2026
Conversation
Bumps [github.com/aws/aws-sdk-go-v2/service/cloudwatch](https://github.com/aws/aws-sdk-go-v2) from 1.59.0 to 1.66.0. - [Release notes](https://github.com/aws/aws-sdk-go-v2/releases) - [Commits](aws/aws-sdk-go-v2@service/s3/v1.59.0...service/s3/v1.66.0) --- updated-dependencies: - dependency-name: github.com/aws/aws-sdk-go-v2/service/cloudwatch dependency-version: 1.66.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
github-actions
Bot
deleted the
dependabot/go_modules/github.com/aws/aws-sdk-go-v2/service/cloudwatch-1.66.0
branch
July 29, 2026 00:57
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 was referenced Jul 29, 2026
dantech2000
added a commit
that referenced
this pull request
Jul 29, 2026
The merge step failed for most Dependabot PRs: GraphQL: Auto merge is not allowed for this repository (enablePullRequestAutoMerge) GitHub's auto-merge feature is disabled on this repo (allow_auto_merge=false), so `gh pr merge --auto` only ever worked by accident: when a PR happened to be fully green and mergeable at that moment, gh merged it directly, and otherwise the call errored. That is exactly the observed mix of success and failure runs, and why #82-#95 piled up unmerged with autoMerge=no. Enabling the repo setting is the other possible fix, and it is the worse one. There is no branch protection here, so there are no REQUIRED status checks -- repo-wide auto-merge would merge any PR the moment it became mergeable, regardless of whether CI had run. That is a footgun well beyond Dependabot. We do not need it. The two wait-for-check gates above already block until "Run go test" and "Run golangci-lint" report success, and the step's `if` requires both. By the time we reach the merge, the checks have demonstrably passed, so a direct merge is equivalent in safety -- and it fails loudly on conflict rather than queueing silently forever. Combined with GH_PAT from ab21bd1, the full path now works: bump merged as a real user -> Test/Lint/Release Please fire on main -> `fix(deps)` cuts a patch release. Verified that ab21bd1 (merged manually as a user) triggered Lint, Test and Release Please, while 37f1d0f (auto-merged under the old token) triggered none.
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
1 participant
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/aws/aws-sdk-go-v2/service/cloudwatch from 1.59.0 to 1.66.0.
Commits
ebfeafaRelease 2024-10-16e0fa20eRegenerated Clientsccc6c9cUpdate API model09f35b4backfill@requiredon imagebuilder#LaunchTemplateConfiguration.SetDefaultVers...04e7acamake endpoint url integration test env-resilient (#2840)3cc4661add loadoptions to configure BaseEndpoint (#2837)8ed647aRelease 2024-10-15bf76f90Regenerated Clients37659a9Update endpoints model10d7754Update API modelDependabot 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)