Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jan 3, 2025

This PR contains the following updates:

Package Change Age Confidence
semantic-release 24.2.0 -> 24.2.9 age confidence

Release Notes

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

v24.2.9

Compare Source

Bug Fixes

v24.2.8

Compare Source

Bug Fixes

v24.2.7

Compare Source

Performance Improvements

v24.2.6

Compare Source

Bug Fixes

v24.2.5

Compare Source

Bug Fixes
  • deps: raise the minimum of the defined range for marked-terminal (#​3742) (fb1ccd4)

v24.2.4

Compare Source

Bug Fixes

v24.2.3

Compare Source

Bug Fixes

v24.2.2

Compare Source

Bug Fixes

v24.2.1

Compare Source

Bug Fixes

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.

🔕 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 changed the title chore(deps): update dependency semantic-release to v24.2.1 chore(deps): update dependency semantic-release to v24.2.2 Feb 9, 2025
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 3d97680 to f0c85f5 Compare February 9, 2025 14:35
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v24.2.2 chore(deps): update dependency semantic-release to v24.2.3 Feb 15, 2025
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from f0c85f5 to fb82b12 Compare February 15, 2025 22:14
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v24.2.3 chore(deps): update dependency semantic-release to v24.2.4 May 16, 2025
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from fb82b12 to d9ca926 Compare May 16, 2025 22:19
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v24.2.4 chore(deps): update dependency semantic-release to v24.2.5 May 24, 2025
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from d9ca926 to 012ba95 Compare May 24, 2025 01:29
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 012ba95 to bc2dd5f Compare June 29, 2025 16:43
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v24.2.5 chore(deps): update dependency semantic-release to v24.2.6 Jun 29, 2025
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from bc2dd5f to 836517c Compare July 11, 2025 20:32
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v24.2.6 chore(deps): update dependency semantic-release to v24.2.7 Jul 11, 2025
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 836517c to ad7d120 Compare September 19, 2025 16:09
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v24.2.7 chore(deps): update dependency semantic-release to v24.2.8 Sep 19, 2025
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from ad7d120 to c9da57a Compare September 19, 2025 21:57
@renovate renovate bot changed the title chore(deps): update dependency semantic-release to v24.2.8 chore(deps): update dependency semantic-release to v24.2.9 Sep 19, 2025
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from c9da57a to bea9a4a Compare September 25, 2025 16:50
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from bea9a4a to 7fae737 Compare October 21, 2025 23:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

0 participants