Update actions/setup-go action to v6

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
actions/setup-go	action	major	v3 -> v6

---

Release Notes

actions/setup-go (actions/setup-go)

v6

Compare Source

v5

Compare Source

v4

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to 4b1c155 in 45 seconds. Click for details.

• Reviewed 178 lines of code in 4 files
• Skipped 0 files when reviewing.
• Skipped posting 4 draft 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/main.yml:31

• Draft comment:
  Updated actions/setup-go from v3 to v6. Ensure that the 'go-version' parameter and its usage remain compatible with v6. Also, double-check the release notes for any breaking changes in v6 that might affect your workflow.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% The comment is asking the PR author to ensure compatibility and check for breaking changes, which violates the rule against asking the author to confirm or double-check things. It also relates to dependency changes, which should not be commented on unless there's a specific suggestion or issue identified.

2. .github/workflows/prerelease.yml:32

• Draft comment:
  The actions/setup-go version was bumped to v6. Verify that the v6 behavior (especially parameter handling) aligns with your needs and that there are no side effects from the major version upgrade.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is asking the PR author to verify the behavior of a dependency version change, which is against the rules. It doesn't provide a specific suggestion or point out a specific issue with the code.

3. .github/workflows/release.yml:29

• Draft comment:
  Changed actions/setup-go@v3 to v6. Confirm that any changes introduced in v6 (if any) — such as parameter defaults or new options — do not adversely affect the release process.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is asking the PR author to confirm changes related to a dependency update, which violates the rule against commenting on dependency changes or asking for confirmation of intentions. The comment does not provide a specific code suggestion or ask for a specific test to be written.

4. .github/workflows/run-acceptance-tests.yml:35

• Draft comment:
  Updated actions/setup-go from v3 to v6. Make sure that the specified 'go-version' input is correctly interpreted under v6 and that there are no unexpected behavioral changes in your acceptance tests workflow.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is asking the PR author to ensure that the 'go-version' input is correctly interpreted and that there are no unexpected behavioral changes. This falls under asking the author to double-check things and ensure behavior, which violates the rules.

Workflow ID: wflow_ln6yCujHfiUJj7ly

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}