Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update goreleaser/goreleaser-action action to v5.1.0 #324

Merged
merged 1 commit into from
May 10, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 10, 2024

Mend Renovate

This PR contains the following updates:

Package Type Update Change
goreleaser/goreleaser-action action minor v5.0.0 -> v5.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: Enabled.

Rebasing: Whenever PR is behind base branch, 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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot added the renovate Changes by renovate label May 10, 2024
@renovate renovate bot enabled auto-merge (squash) May 10, 2024 18:32
@renovate renovate bot merged commit 224b28f into main May 10, 2024
4 checks passed
@renovate renovate bot deleted the renovate/goreleaser-goreleaser-action-5.x branch May 10, 2024 18:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
renovate Changes by renovate
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants