Skip to content

chore(deps): update semantic-release monorepo#836

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/semantic-release-monorepo
Open

chore(deps): update semantic-release monorepo#836
renovate[bot] wants to merge 1 commit intomainfrom
renovate/semantic-release-monorepo

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented May 10, 2025

This PR contains the following updates:

Package Change Age Confidence
@semantic-release/exec 7.0.37.1.0 age confidence
@semantic-release/github 11.0.211.0.6 age confidence
@semantic-release/npm 12.0.112.0.2 age confidence
@semantic-release/release-notes-generator 14.0.314.1.0 age confidence
semantic-release 24.2.324.2.9 age confidence

Release Notes

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

v7.1.0

Compare Source

Features
  • error: print more useful error for non-process failure (#​449) (a285bc5)
semantic-release/github (@​semantic-release/github)

v11.0.6

Compare Source

Bug Fixes

v11.0.5

Compare Source

Bug Fixes

v11.0.4

Compare Source

Bug Fixes

v11.0.3

Compare Source

Bug Fixes
semantic-release/npm (@​semantic-release/npm)

v12.0.2

Compare Source

Bug Fixes
semantic-release/release-notes-generator (@​semantic-release/release-notes-generator)

v14.1.0

Compare Source

Features
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

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.

👻 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 requested a review from a team as a code owner May 10, 2025 19:22
@renovate renovate bot changed the title chore(deps): update dependency @semantic-release/exec to v7.1.0 chore(deps): update semantic-release monorepo May 17, 2025
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch 2 times, most recently from 7a4b25f to 1af7060 Compare May 24, 2025 11:46
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch 3 times, most recently from e159e10 to 5bed8ee Compare June 6, 2025 13:00
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch 7 times, most recently from 3d3dc69 to 96d6492 Compare June 10, 2025 14:47
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch 2 times, most recently from 2dd943b to 96155d0 Compare June 17, 2025 13:09
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch 2 times, most recently from 013ee13 to daf2d18 Compare June 29, 2025 17:39
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from daf2d18 to 6be504d Compare July 11, 2025 23:03
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch 2 times, most recently from e4518a0 to 650feeb Compare August 11, 2025 01:41
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 650feeb to d96759d Compare August 19, 2025 14:16
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch 2 times, most recently from 44ab243 to 55dc6f7 Compare September 5, 2025 21:38
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch 5 times, most recently from 0a74da7 to 2809eb5 Compare September 17, 2025 13:13
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 2809eb5 to 359fa83 Compare September 19, 2025 21:55
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 359fa83 to c0106da Compare September 25, 2025 16:04
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from c0106da to 4994cef Compare October 21, 2025 11:08
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 4994cef to 412f0b3 Compare November 11, 2025 01:18
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 412f0b3 to 445aa54 Compare November 18, 2025 20:10
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch 4 times, most recently from ce7dab1 to bb47784 Compare December 4, 2025 08:53
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from bb47784 to 1c14c0b Compare December 4, 2025 10:51
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch 2 times, most recently from 85ef2d1 to 6a6c6fe Compare January 7, 2026 15:38
@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud bot commented Jan 7, 2026

@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 6a6c6fe to 0c190fb Compare February 12, 2026 10:03
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 0c190fb to 5cd8bb0 Compare March 5, 2026 17:42
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 5cd8bb0 to 62cebc4 Compare March 13, 2026 14:05
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch 3 times, most recently from a490065 to f8fa894 Compare April 3, 2026 10:56
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from f8fa894 to f684499 Compare April 3, 2026 11:03
@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud bot commented Apr 3, 2026

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