Skip to content

Update semantic-release monorepo #15

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

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 24, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@semantic-release/github 11.0.2 -> 11.0.3 age adoption passing confidence
semantic-release 24.2.4 -> 24.2.5 age adoption passing confidence

Release Notes

semantic-release/github (@​semantic-release/github)

v11.0.3

Compare Source

Bug Fixes
semantic-release/semantic-release (semantic-release)

v24.2.5

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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • 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 force-pushed the renovate/semantic-release-monorepo branch from 55f62d0 to b90ecb2 Compare May 25, 2025 16:49
@renovate renovate bot changed the title Update dependency semantic-release to v24.2.5 Update semantic-release monorepo May 25, 2025
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from b90ecb2 to 6f27dcf Compare May 28, 2025 10:54
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