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 dependency semantic-release to v23.1.1 #963

Merged
merged 1 commit into from
May 11, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 10, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
semantic-release 23.0.8 -> 23.1.1 age adoption passing confidence

Release Notes

semantic-release/semantic-release (semantic-release)

v23.1.1

Compare Source

v23.1.0

Compare Source


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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.

@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v23.1.0 chore(deps): update dependency semantic-release to v23.1.1 May 10, 2024
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 5fdeb35 to 34d3871 Compare May 10, 2024 21:05
@renovate renovate bot merged commit e8dca4a into main May 11, 2024
3 checks passed
@renovate renovate bot deleted the renovate/semantic-release-monorepo branch May 11, 2024 00:36
@KengoTODA
Copy link
Owner

🎉 This PR is included in version 1.2.3 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant