Skip to content

Update goreleaser/goreleaser-action action to v5.1.0#4

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/goreleaser-goreleaser-action-5.x
Open

Update goreleaser/goreleaser-action action to v5.1.0#4
renovate[bot] wants to merge 1 commit intomainfrom
renovate/goreleaser-goreleaser-action-5.x

Conversation

@renovate
Copy link

@renovate renovate bot commented Jul 6, 2025

This PR contains the following updates:

Package Type Update Change
goreleaser/goreleaser-action action minor v5.0.0v5.1.0

Release Notes

goreleaser/goreleaser-action (goreleaser/goreleaser-action)

v5.1.0

Compare Source

Important

This version changes the default behavior of latest to ~> v1.

The next major of this action (v6), will change this to ~> v2, and will be launched together with GoReleaser v2.

What's Changed

New Contributors

Full Changelog: goreleaser/goreleaser-action@v5.0.0...v5.1.0


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.

@renovate renovate bot force-pushed the renovate/goreleaser-goreleaser-action-5.x branch 2 times, most recently from 85f7cbb to 7897f3d Compare July 6, 2025 17:05
@renovate renovate bot changed the title chore(deps): update goreleaser/goreleaser-action action to v5.1.0 Update goreleaser/goreleaser-action action to v5.1.0 Jul 6, 2025
@renovate renovate bot force-pushed the renovate/goreleaser-goreleaser-action-5.x branch from 7897f3d to be30322 Compare August 3, 2025 12:14
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.

0 participants