镜像站点 · 本页由第三方 GitHub 只读镜像提供,非 GitHub 官方站点,不接受任何登录或凭据输入。前往 github.com
Skip to content

chore(deps): bump actions/setup-go from 4 to 6 - #717

Merged
nieblara merged 3 commits into
mainfrom
dependabot/github_actions/actions/setup-go-6
Oct 13, 2026
Merged

nieblara merged 3 commits into
mainfrom
dependabot/github_actions/actions/setup-go-6

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 23, 2026 •

Copy link
Copy Markdown
Contributor

Bumps actions/setup-go from 4 to 6.

Release notes

Sourced from actions/setup-go's releases.

v6.0.0

What's Changed

Breaking Changes

Make sure your runner is on version v2.327.1 or later to ensure compatibility with this release. See Release Notes

Dependency Upgrades

New Contributors

Full Changelog: actions/setup-go@v5...v6.0.0

v5.6.0

What's Changed

Full Changelog: actions/setup-go@v5...v5.6.0

v5.5.0

What's Changed

Bug fixes:

Dependency updates:

New Contributors

Full Changelog: actions/setup-go@v5...v5.5.0

... (truncated)

Commits

Dependabot compatibility score

You can trigger a rebase of this PR by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note

Overview
Updates GitHub Actions to use actions/setup-go@v6 in the Dependency Scan (generate-go-sbom) and Go build jobs, replacing v5 and v4 respectively.

go-version-file: go.mod is unchanged, so the Go version installed in CI should still follow the module pin; the main effect is adopting setup-go v6’s toolchain and runner behavior (including its Node 24 runtime and stricter toolchain handling per upstream release notes).

Reviewed by Cursor Bugbot for commit f79c4a0. Bugbot is set up for automated code reviews on this repo. Configure here.

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

Bumps [actions/setup-go](https://github.com/actions/setup-go) from 4 to 6.
- [Release notes](https://github.com/actions/setup-go/releases)
- [Commits](actions/setup-go@v4...v6)

---
updated-dependencies:
- dependency-name: actions/setup-go
  dependency-version: '6'
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Jun 23, 2026
cursor Bot pushed a commit that referenced this pull request Oct 6, 2026
- verdict.jq: if each PR finding of a list check (actionlint,
  golangci-lint, prettier, actions-pinning, npm ls) also occurs on
  base, the failure is pre-existing. Before, a PR that removed one
  actionlint finding got a block (#717, #721).
- golangci-lint: run with --allow-parallel-runners. A non-zero exit
  with no finding is incomplete, not a failure with 0 findings.
- ui-npm-ci: take the conflict from npm error lines only. An npm warn
  line named the wrong peer on #729.
- deps.py: a package that already had an install script on base adds
  no new script (esbuild on #779).
- ui-dep-usage: join package names with "and".
- pr-state: for a conflicting PR, do not say that the checks ran on
  the PR merged into main.
- verify.sh: save the baseline profile. --phase generated and
  --phase render use it instead of the default profile.

Co-authored-by: Ramon Niebla <nieblara@users.noreply.github.com>
cursor Bot pushed a commit that referenced this pull request Oct 6, 2026
- classify.sh: when workflows pin an action at several old refs, record
  each ref that the PR replaces. The old version is the lowest of them.
  Before, #718 compared release-secrets v1.2.0 with itself, and #717
  compared only setup-go v5 with v6.
- actions_analysis.py: compare each replaced ref with the new ref. An
  output or input counts as removed only if an old action.yml declared
  it. release-please-action declares no outputs and sets them at run
  time, which gave a false block on #722.
- actions-coverage.sh: read fields with the unit separator. Tab is IFS
  whitespace, so empty fields collapsed and shifted the runtime into
  the wrong field (#717, #721). Show a missing default as "none".

Co-authored-by: Ramon Niebla <nieblara@users.noreply.github.com>
cursor Bot pushed a commit that referenced this pull request Oct 6, 2026
New fixtures: #717 safe-to-merge (setup-go from v4 and v5), #718 compares
release-secrets v1.0.1 with v1.2.0, #721 needs-human with the
python-version question, #722 needs-human (not block), and #779 block
with the undisclosed updates and no esbuild question. The #831 fixture
expects the new wording. The impact-review copies drop notes about the
old verifier bugs.

replay.sh supports pr_meta, decisions_exclude, and updates expectations.
run.sh adds 16 unit tests with stub tools: the findings subset rule,
golangci-lint lock contention, npm warn lines, install scripts on base,
pr-disclosure, pr-state wording, classify with mixed refs, and
actions-coverage with a stub gh.

Co-authored-by: Ramon Niebla <nieblara@users.noreply.github.com>
@cursor

cursor Bot commented Oct 6, 2026

Copy link
Copy Markdown

Dependency verification: SAFE TO MERGE

Risk tier high · ecosystems: github-actions · head c3c375a tested as merged into main @ 9197f92

Every required check ran and passed. No decision is necessary.

Updates

Package From To Change Ecosystem Tier
actions/setup-go v4 v6 major github-actions high

What the verifier checked

Check Result Summary
PR merges cleanly and changes only dependency files pass Merges cleanly into main; only dependency manifests changed
CI results on the PR head pass All 9 CI checks green on PR head c3c375a
No dependency goes to a lower version than base pass No downgrades
Upstream release notes and diff of each direct update pass (note) Upstream notes cover the full range for 1 of 1 direct update(s); notes mention: breaking (1), deprecation (1), requirements (1), security (1). The impact review must cover them
Third-party actions use a commit SHA (SEC-7924) pass All third-party actions pinned to commit SHAs
actionlint fails on base too actionlint reports 2 finding(s)
Updated actions: CI coverage, inputs, outputs, defaults, runtime, permissions pass Every usage runs on PR CI, and the inputs, outputs, and runtime match

Already failing on main (not caused by this PR)

  • actionlint: actionlint reports 2 finding(s)

Generated checks

A generated check counts only when it fails on the old version and passes on the new one. 0 of 1 proven.

Check Kind Base PR Outcome
setup-go selects Go only from the go directive in go.mod guard pass pass holds on both

Impact review

actions/setup-go moves from v4 (go.yml) and v5 (dependency-scan.yml) to v6. v5 moved to the node20 runtime, changed the cache service, and added the architecture to the cache key. v6 moves to node24, needs runner v2.327.1 or later, and prefers a go.mod toolchain directive when it selects Go. ldcli passes only go-version-file: go.mod, and go.mod has 'go 1.25' with no toolchain directive, so v6 selects the same Go. Both workflows run on PR CI on ubuntu-latest, and all 9 CI checks pass on the PR head.

  • actions/setup-go v4..v6: v5.0.0: node20 runtime. v5.1.0: architecture in the cache key (old cache keys stop matching). v5.3.0: new cache service (@actions/cache 4). v6.0.0: improved toolchain selection (Improve toolchain handling actions/setup-go#460, breaking), node24 runtime, runner v2.327.1 or later. (breaking) (source)
  • Used in: .github/workflows/go.yml, .github/workflows/dependency-scan.yml
  • Upstream behavior changes that reach ldcli: no
  • Note: The breaking toolchain change (Improve toolchain handling actions/setup-go#460) has no effect: go.mod has no toolchain directive, and each setup-go step passes only go-version-file: go.mod (guard). The cache-key change invalidates the Go cache one time. (Improve toolchain handling actions/setup-go#460, generated/setup-go-inputs-resolve-same-go.sh)
  • Note: PR CI runs both workflows. GitHub-hosted ubuntu-latest runners meet the v2.327.1 minimum, and the 9 CI checks on the PR head pass with v6. No composite action in .github/actions uses setup-go. (state/checks/ci-status, state/checks/actions-coverage)
Check details

pr-state

  • Branch is 51 commit(s) behind main. The checks ran on the PR merged into the current main.

ci-status

  • CI results are for the PR head c3c375a as pushed, which may be behind the base branch.

upstream-changes

actionlint

.github/workflows/go.yml:29:13: the runner of "actions/setup-python@v3" action is too old to run on GitHub Actions. update the action's version to fix this issue [action]
.github/workflows/release-please.yml:60:14: label "ubuntu-22.04-8core-32gb" is unknown. available labels are "windows-latest", "windows-latest-8-cores", "windows-2025", "windows-2022", "windows-2019", "ubuntu-latest", "ubuntu-latest-4-cores", "ubuntu-latest-8-cores", "ubuntu-latest-16-cores", "ubuntu-24.04", "ubuntu-24.04-arm", "ubuntu-22.04", "ubuntu-22.04-arm", "ubuntu-20.04", "macos-latest", "macos-latest-xl", "macos-latest-xlarge", "macos-latest-large", "macos-15-xlarge", "macos-15-large", "macos-15", "macos-14-xl", "macos-14-xlarge", "macos-14-large", "macos-14", "macos-13-xl", "macos-13-xlarge", "macos-13-large", "macos-13", "self-hosted", "x64", "arm", "arm64", "linux", "macos", "windows". if it is a custom label for self-hosted runner, set list of labels in actionlint.yaml config file [runner-label]

actions-coverage

Action Change Used in Runs on PR CI? Upstream action.yml
actions/setup-go v4, v5 → v6 .github/workflows/dependency-scan.yml, .github/workflows/go.yml yes inputs used: go-version-file; outputs read: none; runtime node16, node20 → node24

generated: setup-go-inputs-resolve-same-go

go.mod: go 1.25, no toolchain directive. Every setup-go step passes only go-version-file: go.mod.

Generated by scripts/dependency-pr/verify.sh (profile full) at 2026-10-06T22:07:41Z. The verifier does not approve or merge.

@nieblara
nieblara requested a review from a team as a code owner October 7, 2026 16:52
cursor Bot pushed a commit that referenced this pull request Oct 13, 2026
… head

The status-check rollup does not show a workflow run that failed before
any job started, or a run that waits in the queue. On #717, ci-status
counted only Bugbot, Semgrep, and the bot-oversight check, and passed.
The Go and dev-server UI runs had failed with 0 jobs, and Dependency Scan
was still queued.

ci-status now finds the workflows whose triggers match the PR (event,
branch, activity types, and path filters). It compares them with the runs
on the head commit. A missing, queued, in-progress, startup-failure, or
0-job run is incomplete. A result for another commit counts as not run.
ci-status is now a required check, so incomplete CI gives an incomplete
verdict.

Co-authored-by: rniebla <rniebla@launchdarkly.com>
@nieblara
nieblara merged commit fd8b684 into main Oct 13, 2026
10 checks passed
@nieblara
nieblara deleted the dependabot/github_actions/actions/setup-go-6 branch October 13, 2026 19:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants