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): semantic-release@24.1.1 #233

Merged
merged 1 commit into from
Sep 19, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 20, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
semantic-release ^24.0.0 -> ^24.1.1 age adoption passing confidence

Release Notes

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

v24.1.1

Compare Source

v24.1.0

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 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the deps label Aug 20, 2024
@renovate renovate bot requested a review from kenany August 20, 2024 15:52
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from db961be to f7d5be0 Compare September 14, 2024 04:37
@renovate renovate bot changed the title chore(deps): semantic-release@24.1.0 chore(deps): semantic-release@24.1.1 Sep 14, 2024
@kenany kenany merged commit bd7dc62 into master Sep 19, 2024
5 checks passed
@renovate renovate bot deleted the renovate/semantic-release-monorepo branch September 19, 2024 13:33
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