[mrz1836]

What Changed

• Updated actions/setup-go in .github/actions/setup-go-with-cache/action.yml from v6.4.0 (4a3601121dd01d1626a1e23e37211e3254c1c06c) to v7.0.0 (b7ad1dad31e06c5925ef5d2fc7ad053ef454303e).
• Updated goreleaser/goreleaser-action in .github/actions/setup-goreleaser/action.yml from v7.2.3 (f06c13b6b1a9625abc9e6e439d9c05a8f2190e94) to v7.3.0 (a4f02ab5355a589de60d917a659ce617ed19b3de).
• Both actions remain pinned to full commit SHAs, with the version noted in a trailing comment. No other lines changed.

Why It Was Necessary

• Keeps the pinned third-party GitHub Actions used by the composite actions current with their latest releases.
• The automated sync brings these action references in line with the upstream source of truth.

Testing Performed

• Reviewed the diff and confirmed only the two uses: lines changed, each with an updated SHA and version comment.
• CI workflows that call the setup-go-with-cache and setup-goreleaser composite actions should be run to confirm Go setup and GoReleaser installation still work.
• No local tests were run, since the change only touches workflow action references.

Impact / Risk

• Risk: Low to moderate. actions/setup-go is a major version bump (v6.4.0 to v7.0.0), so there is a small chance of behavior differences in Go setup. The existing cache: false and go-version inputs are unchanged.
• GoReleaser: This is a minor bump (v7.2.3 to v7.3.0) and is expected to be backward compatible. It only affects the cache-miss install step.
• Breaking changes: None are expected for consumers of these composite actions, and no input or output interfaces were changed. Any CI failures after merge should be checked against the new action versions first.

[mrz1836]

LGTM!