-
Notifications
You must be signed in to change notification settings - Fork 0
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
fix(deps): update semantic-release monorepo (major) #35
base: main
Are you sure you want to change the base?
Conversation
Important Review skippedAuto reviews are limited to specific labels. Labels to auto review (1)
Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
41c8111
to
3b73a1a
Compare
3b73a1a
to
736e54a
Compare
fbe5898
to
7dc426f
Compare
7dc426f
to
ca44e12
Compare
ca44e12
to
ce807ee
Compare
ce807ee
to
574b4e3
Compare
This PR contains the following updates:
11.1.0
->13.0.0
9.2.6
->10.0.6
11.0.2
->12.0.1
12.1.0
->14.0.0
^23
->^24.0.0
23.0.2
->24.0.0
Release Notes
semantic-release/commit-analyzer (@semantic-release/commit-analyzer)
v13.0.0
Compare Source
Bug Fixes
Features
BREAKING CHANGES
dropping support for previous major versions of those packages due to the breaking changes between
majors. this only impacts your project if you are installing alongside semantic-release, so updating
those packages to latest version should be the only change you need for this update. no action
should be necessary if you are using default semantic-release config
v12.0.0
Compare Source
Features
exports
to point at ./index.js (f3358dd)BREAKING CHANGES
exports
has been defined, which prevents access to private apis (which arentintended for consumption anyway)
semantic-release/github (@semantic-release/github)
v10.0.6
Compare Source
v10.0.5
Compare Source
Bug Fixes
v10.0.4
Compare Source
Bug Fixes
v10.0.3
Compare Source
v10.0.2
Compare Source
Bug Fixes
v10.0.1
Compare Source
Bug Fixes
v10.0.0
Compare Source
Features
BREAKING CHANGES
semantic-release/npm (@semantic-release/npm)
v12.0.1
Compare Source
Bug Fixes
v12.0.0
Compare Source
Features
exports
to point at ./index.js (9e193c2)BREAKING CHANGES
exports
has been defined, which prevents access to private apis (which arentintended for consumption anyway)
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
semantic-release/release-notes-generator (@semantic-release/release-notes-generator)
v14.0.0
Compare Source
Features
BREAKING CHANGES
v13.0.0
Compare Source
Features
exports
to point at ./index.js (5655b18)BREAKING CHANGES
exports
has been defined, which prevents access to private apis (which arentintended for consumption anyway)
semantic-release/semantic-release (semantic-release)
v24.0.0
Compare Source
Configuration
📅 Schedule: Branch creation - "before 4am on Monday" in timezone Europe/Paris, 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.
This PR has been generated by Mend Renovate. View repository job log here.