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 cloudposse/github-action-major-release-tagger action to v2 #78

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 1, 2024

This PR contains the following updates:

Package Type Update Change
cloudposse/github-action-major-release-tagger action major v1 -> v2

Release Notes

cloudposse/github-action-major-release-tagger (cloudposse/github-action-major-release-tagger)

v2

Compare Source


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 requested review from a team as code owners April 1, 2024 22:03
@renovate renovate bot requested review from jamengual and joe-niland April 1, 2024 22:03
@renovate renovate bot force-pushed the renovate/cloudposse-github-action-major-release-tagger-2.x branch from c00e7ec to e179ba9 Compare May 8, 2024 22:32
@renovate renovate bot changed the title Update cloudposse/github-action-major-release-tagger action to v2 chore(deps): update cloudposse/github-action-major-release-tagger action to v2 May 8, 2024
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