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

Update semantic-release monorepo #1298

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 8, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@semantic-release/commit-analyzer 11.0.0 -> 11.1.0 age adoption passing confidence
@semantic-release/github 9.2.1 -> 9.2.6 age adoption passing confidence
@semantic-release/npm 11.0.0 -> 11.0.3 age adoption passing confidence
@semantic-release/release-notes-generator 12.0.0 -> 12.1.0 age adoption passing confidence

Release Notes

semantic-release/commit-analyzer (@​semantic-release/commit-analyzer)

v11.1.0

Compare Source

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

v9.2.6

Compare Source

Bug Fixes

v9.2.5

Compare Source

Bug Fixes

v9.2.4

Compare Source

Bug Fixes

v9.2.3

Compare Source

Bug Fixes

v9.2.2

Compare Source

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

v11.0.3

Compare Source

Bug Fixes

even though our existing range allowed anyone to update as soon as the new npm version was available, this will encourage being on a version that does not report the ip vulnerability a bit more forcefully

v11.0.2

Compare Source

Bug Fixes
  • deps: update dependency npm to v10.2.5 (42b5dec)

v11.0.1

Compare Source

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

v12.1.0

Compare Source

Features

v12.0.1

Compare Source

Bug Fixes

Configuration

📅 Schedule: Branch creation - "after 9am on Wednesday" in timezone Europe/London, 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 added change: dependencies Updates to dependencies only release: skip Skips the release step when this pr is merged labels Nov 8, 2023
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch 3 times, most recently from 41f1398 to ab10138 Compare November 10, 2023 11:43
@AndrewLeedham AndrewLeedham removed their assignment Nov 10, 2023
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from ab10138 to c9cdf1c Compare November 29, 2023 22:23
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from c9cdf1c to a6256d8 Compare December 7, 2023 18:05
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from a6256d8 to abc46ed Compare December 22, 2023 22:44
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from abc46ed to 9cfd3a3 Compare March 1, 2024 23:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
change: dependencies Updates to dependencies only release: skip Skips the release step when this pr is merged
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant