Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

Copy link
Contributor

Copilot AI commented Dec 8, 2025

GoReleaser deployment workflow uses v1.17.1, but v2 has been stable since June 2024 (latest: v2.13.1).

Changes

Workflow updates (.github/workflows/deployment.yml):

  • Updated goreleaser-action from v5 (SHA e435ccd) to v6.0.0 (SHA 286f3b1) across linux, macos, and windows jobs
  • Changed version specifier from ~1.17.1 to ~> v2
  • Added version comments (# v6.0.0) to document the goreleaser-action version on each uses line

Config updates (.goreleaser.yml):

  • Added version: 2 directive (required for v2)
  • Removed rlcp: true from archives (default since v1.19, removed in v2)

References

Original prompt

Our goreleaser version in our deployment.yml workflow file is outdated. The newest version is ~v2. This might have resulted in a change to things in goreleaser config file in the root of the repository as well.

Produce a plan to upgrade to the latest goreleaser and execute that plan. The plan should be well researched and reasoned, each change backed up by real changelog posts that indicate that a config option should be changed.

Here is a reference documentation link to get started: https://goreleaser.com/blog/goreleaser-v2


✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

- Update goreleaser-action to v6.0.0 (commit 286f3b1) in all 3 workflow jobs
- Update goreleaser version from ~1.17.1 to ~v2 in deployment.yml
- Add version: 2 at top of .goreleaser.yml (required for v2)
- Remove rlcp: true from all 3 archives (now default behavior, deprecated since v1.19)

References:
- https://goreleaser.com/blog/goreleaser-v2/ - v2 requires version: 2 in config
- https://goreleaser.com/deprecations/ - rlcp removed in v2, now default since v1.19

Co-authored-by: BagToad <[email protected]>
Copilot AI changed the title [WIP] Update goreleaser version in deployment workflow Upgrade GoReleaser to v2 Dec 8, 2025
Copilot AI requested a review from BagToad December 8, 2025 17:20
@BagToad
Copy link
Member

BagToad commented Dec 8, 2025

@copilot I think you may have misunderstood the version key requirements from the doc at https://goreleaser.com/blog/goreleaser-v2

The doc says to use "~> v2" as the version value.

Can you please also add a comment to indicate what version of goreleaser-action we are using? Add the comment to the end of the line like this:

    uses: goreleaser/goreleaser-action@286f3b13b1b49da4ac219696163fb8c1c93e1200 #vX.X.X

- Change version from "~v2" to "~> v2" per goreleaser v2 docs
- Add "# v6.0.0" comment to all goreleaser-action uses lines

Co-authored-by: BagToad <[email protected]>
Copy link
Contributor Author

Copilot AI commented Dec 8, 2025

@copilot I think you may have misunderstood the version key requirements from the doc at https://goreleaser.com/blog/goreleaser-v2

The doc says to use "~> v2" as the version value....

Fixed in f90c64f:

  • Changed version syntax from "~v2" to "~> v2" in all 3 workflow jobs
  • Added # v6.0.0 comments to document the goreleaser-action version

@babakks
Copy link
Member

babakks commented Dec 15, 2025

Since Copilot didn't cover all the necessary changes, I'm closing this in favour of #12318.

@babakks babakks closed this Dec 15, 2025
@babakks babakks linked an issue Dec 15, 2025 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Upgrade to GoReleaser v2

3 participants