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): [email protected] #45

Merged
merged 1 commit into from
Jun 11, 2024
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 14, 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: 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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot added the deps label May 14, 2024
@renovate renovate bot requested a review from kenany May 14, 2024 01:05
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 8a116b6 to 6facc71 Compare May 20, 2024 05:17
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 6facc71 to 6bf4e41 Compare June 2, 2024 19:17
@kenany kenany merged commit 6583395 into master Jun 11, 2024
13 checks passed
@renovate renovate bot deleted the renovate/semantic-release-monorepo branch June 11, 2024 23:15
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