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 softprops/action-gh-release action to v2 #668

Merged
merged 1 commit into from
Apr 15, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 25, 2024

Mend Renovate

This PR contains the following updates:

Package Type Update Change
softprops/action-gh-release action major v0.1.15 -> v2.0.4

Release Notes

softprops/action-gh-release (softprops/action-gh-release)

v2.0.4

Compare Source

v2.0.3

Compare Source

v2.0.2

Compare Source

  • Revisit approach to #​384 making unresolved pattern failures opt-in #​417

v2.0.1

Compare Source

v2.0.0

Compare Source

  • update actions.yml declaration to node20 to address warnings

Configuration

📅 Schedule: Branch creation - "every 3 weeks on Monday" (UTC), 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 has been generated by Mend Renovate. View repository job log here.

@loosebazooka
Copy link
Member

I think this is non breaking, but I need to test it out somewhere.

@vlsi
Copy link
Collaborator

vlsi commented Apr 15, 2024

Let's bump it and revert in case it fails

@vlsi vlsi merged commit 59159af into main Apr 15, 2024
13 checks passed
@vlsi vlsi deleted the renovate/softprops-action-gh-release-2.x branch April 15, 2024 06:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants