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

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

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 29, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@semantic-release/github 9.2.3 -> 9.2.6 age adoption passing confidence
@semantic-release/npm 11.0.1 -> 11.0.3 age adoption passing confidence
semantic-release 22.0.8 -> 22.0.12 age adoption passing confidence

Release Notes

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
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)
semantic-release/semantic-release (semantic-release)

v22.0.12

Compare Source

Bug Fixes
  • Revert "fix(deps): update dependency cosmiconfig to v9" (#​3104) (f6f1bf1)

v22.0.11

Compare Source

Bug Fixes
  • deps: update dependency cosmiconfig to v9 (b38cd2e)

v22.0.10

Compare Source

Bug Fixes
  • revert updating cosmiconfig to v9 (88efead)

v22.0.9

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.

👻 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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 3f926bb to a0e9112 Compare December 3, 2023 09:40
@renovate renovate bot changed the title chore(deps): update dependency @semantic-release/github to v9.2.4 chore(deps): update semantic-release monorepo Dec 5, 2023
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch 4 times, most recently from bb03beb to 433f1fb Compare December 12, 2023 01:14
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 433f1fb to 825b5a9 Compare December 12, 2023 07:06
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 825b5a9 to 2f77d1f Compare December 22, 2023 21:46
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 2f77d1f to 6957928 Compare January 28, 2024 09:49
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 6957928 to 22ba039 Compare February 4, 2024 10:48
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch 2 times, most recently from c8bc833 to 84a2290 Compare March 2, 2024 00:44
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 84a2290 to e59567e Compare March 12, 2024 10:05
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch 2 times, most recently from a0e5f0c to 6b408e8 Compare March 24, 2024 13:25
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 6b408e8 to 6649d56 Compare April 14, 2024 09:59
@renovate renovate bot force-pushed the renovate/semantic-release-monorepo branch from 6649d56 to fc791fd Compare April 25, 2024 12:05
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.

None yet

0 participants