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

build(deps): update dependency semantic-release to v24.2.3 (main) #34399

Merged
merged 1 commit into from
Feb 22, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 22, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
semantic-release 24.2.2 -> 24.2.3 age adoption passing confidence

Release Notes

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

v24.2.3

Compare Source

Bug Fixes

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

| datasource | package          | from   | to     |
| ---------- | ---------------- | ------ | ------ |
| npm        | semantic-release | 24.2.2 | 24.2.3 |
@renovate renovate bot enabled auto-merge February 22, 2025 21:02
@renovate renovate bot added this pull request to the merge queue Feb 22, 2025
Merged via the queue into main with commit 19f6ab8 Feb 22, 2025
40 checks passed
@renovate renovate bot deleted the renovate/main-semantic-release-monorepo branch February 22, 2025 21:21
@renovate-release
Copy link
Collaborator

🎉 This PR is included in version 39.177.0 🎉

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
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant