-
Notifications
You must be signed in to change notification settings - Fork 2
gha: bump actions/setup-go from 6.1.0 to 6.2.0 #841
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gha: bump actions/setup-go from 6.1.0 to 6.2.0 #841
Conversation
Bumps [actions/setup-go](https://github.com/actions/setup-go) from 6.1.0 to 6.2.0. - [Release notes](https://github.com/actions/setup-go/releases) - [Commits](actions/setup-go@4dc6199...7a3fe6c) --- updated-dependencies: - dependency-name: actions/setup-go dependency-version: 6.2.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Changed Files
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Important
Looks good to me! 👍
Reviewed everything up to 2e52ef0 in 1 minute and 34 seconds. Click for details.
- Reviewed
26lines of code in2files - Skipped
0files when reviewing. - Skipped posting
2draft comments. View those below. - Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
1. .github/workflows/build.yml:68
- Draft comment:
The commit hash has been updated to 7a3fe6cf4cb3a834922a1244abfce67bcef6a0c5, but the inline comment still states '# v2.1.5'. Consider updating this comment if the version label has changed, to avoid confusion. - Reason this comment was not posted:
Comment was on unchanged code.
2. .github/workflows/release.yml:67
- Draft comment:
The 'Set up Go' step now uses commit 7a3fe6cf4cb3a834922a1244abfce67bcef6a0c5 but the comment still reads '# v2.1.5'. Update the comment if the intended version label has changed. - Reason this comment was not posted:
Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 15% vs. threshold = 50% The comment is essentially asking "update the comment if the intended version label has changed" - this is speculative and asks the author to verify their intention. The rules explicitly state "Do NOT ask the PR author to confirm their intention, to explain, to double-check things, to ensure the behavior is intended" and "Do NOT make speculative comments". The comment doesn't definitively state that the version comment is wrong - it just suggests updating it "if" the version changed. Without knowing whether the new commit hash actually corresponds to a different version than v2.1.5, this is speculative. The PR author likely updated the commit hash for security/pinning reasons while staying on the same version, which is a common practice. It's possible that the commit hash does correspond to a different version and the comment is genuinely outdated. If the version comment is actually incorrect, that could be misleading for future maintainers. However, I don't have evidence that v2.1.5 is wrong for the new commit hash. Without definitive evidence that the version comment is incorrect, this comment is speculative and asks the author to verify/confirm their intention ("if the intended version label has changed"). This violates the rules against speculative comments and asking authors to confirm things. The comment should only be kept if there's strong evidence the version label is actually wrong. Delete this comment. It's speculative and asks the author to verify their intention rather than pointing out a definite issue. Without strong evidence that v2.1.5 is incorrect for the new commit hash, this violates the rules.
Workflow ID: wflow_XooIv3lCHw6I9CW0
You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.



Bumps actions/setup-go from 6.1.0 to 6.2.0.
Release notes
Sourced from actions/setup-go's releases.
Commits
7a3fe6cBump qs from 6.14.0 to 6.14.1 (#703)b9adafdBump actions/checkout from 5 to 6 (#686)d73f6bcREADME.md: correct to actions/checkout@v6 (#683)ae252eeBump@actions/cacheto v5 (#695)bf7446aBump js-yaml from 3.14.1 to 3.14.2 (#682)02aadfeFix Node.js version in action.yml (#691)4aaadf4Example for restore-only cache in documentation (#696)Dependabot 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 mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@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)Important
Bump
actions/setup-gofrom 6.1.0 to 6.2.0 inbuild.ymlandrelease.yml.actions/setup-gofrom 6.1.0 to 6.2.0 inbuild.ymlandrelease.yml.build.ymlandrelease.ymlto use the new version ofactions/setup-go.This description was created by
for 2e52ef0. You can customize this summary. It will automatically update as commits are pushed.