-
-
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
⬆️ Updates semantic-release monorepo (major) #1023
base: master
Are you sure you want to change the base?
Conversation
Pull request by bot. No need to analyze |
Thanks for the PR! This section of the codebase is owner by https://github.com/AlexRogalskiy/ - if they write a comment saying "LGTM" then it will be merged. |
Thanks for opening an issue! Make sure you've followed CONTRIBUTING.md. |
Hello from PR HelperIs your PR ready for review and processing? Mark the PR ready by including If you still have work to do, even after marking this ready. Put the PR on hold by including |
06539b3
to
29222c6
Compare
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎ To accept the risk, merge this PR and you will not be notified again.
Next stepsWhat is an install script?Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts. Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead. Take a deeper look at the dependencyTake a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev. Remove the packageIf you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency. Mark a package as acceptable riskTo ignore an alert, reply with a comment starting with
|
29222c6
to
99de791
Compare
99de791
to
d8e76dd
Compare
d8e76dd
to
8b5148a
Compare
8b5148a
to
1a4eac5
Compare
1a4eac5
to
ecc4a0f
Compare
ecc4a0f
to
dd3301c
Compare
dd3301c
to
16cff4d
Compare
16cff4d
to
8af2300
Compare
8af2300
to
38464e1
Compare
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
38464e1
to
b26a7da
Compare
This PR contains the following updates:
^8.0.4
->^10.0.0
^9.0.1
->^12.0.0
^10.0.3
->^14.0.0
^19.0.3
->^24.0.0
Release Notes
semantic-release/github (@semantic-release/github)
v10.1.3
Compare Source
Bug Fixes
v10.1.2
Compare Source
Bug Fixes
v10.1.1
Compare Source
Bug Fixes
v10.1.0
Compare Source
Features
v10.0.7
Compare Source
Bug Fixes
v10.0.6
Compare Source
Bug Fixes
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
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
v9.2.1
Compare Source
v9.2.0
Compare Source
Features
v9.1.0
Compare Source
Features
releaseNameTemplate
andreleaseBodyTemplate
options for customizing release body and name (#704) (9e2678c)v9.0.7
Compare Source
Bug Fixes
v9.0.6
Compare Source
Bug Fixes
v9.0.5
Compare Source
Bug Fixes
v9.0.4
Compare Source
Bug Fixes
v9.0.3
Compare Source
Bug Fixes
v9.0.2
Compare Source
Bug Fixes
v9.0.1
Compare Source
Bug Fixes
v9.0.0
Compare Source
BREAKING CHANGES
@semantic-release/github
is now a native ES Modulesemantic-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
v11.0.2
Compare Source
Bug Fixes
v11.0.1
Compare Source
Bug Fixes
v11.0.0
Compare Source
Bug Fixes
Features
BREAKING CHANGES
v10.0.6
Compare Source
Bug Fixes
v10.0.5
Compare Source
Bug Fixes
v10.0.4
Compare Source
Bug Fixes
v10.0.3
Compare Source
Bug Fixes
v10.0.2
Compare Source
Bug Fixes
v10.0.1
Compare Source
Bug Fixes
v10.0.0
Compare Source
Bug Fixes
Code Refactoring
Features
BREAKING CHANGES
can be found at https://github.com/npm/cli/releases/tag/v9.0.0
raised to v20.1.0 in order to support loading of ESM plugins
errors
propertyNPM_USERNAME
andNPM_PASSWORD
is no longer supported. UseNPM_TOKEN
instead.@semantic-release/npm
is now a native ES Module. Ithas named exports for each plugin hook (
verifyConditions
,prepare
,publish
,addChannel
)semantic-release/release-notes-generator (@semantic-release/release-notes-generator)
v14.0.1
Compare Source
Bug Fixes
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)
v12.1.0
Compare Source
Features
v12.0.1
Compare Source
Bug Fixes
v12.0.0
Compare Source
Bug Fixes
Features
BREAKING CHANGES
v11.0.7
Compare Source
Bug Fixes
v11.0.6
Compare Source
Reverts
v11.0.5
Compare Source
Bug Fixes
v11.0.4
Compare Source
Bug Fixes
v11.0.3
Compare Source
Bug Fixes
v11.0.2
Compare Source
Bug Fixes
v11.0.1
Compare Source
Bug Fixes
v11.0.0
Compare Source
Code Refactoring
Features
BREAKING CHANGES
@semantic-release/release-notes-generator
is now a native ES Module. It hasnamed exports for each plugin hook (
generateNotes
)semantic-release/semantic-release (semantic-release)
v24.0.0
Compare Source
Bug Fixes
BREAKING CHANGES
conventional-changelog packages. if you are installing any of these packages in addition to
semantic-release, be sure to update them as well
versions of conventional-changelog packages. if you are installing any of these packages in addition
to semantic-release, be sure to update them as well
v23.1.1
Compare Source
v23.1.0
Compare Source
v23.0.8
Compare Source
Bug Fixes
v23.0.7
Compare Source
v23.0.6
Compare Source
Bug Fixes
v23.0.5
Compare Source
v23.0.4
Compare Source
v23.0.3
Compare Source
v23.0.2
Compare Source
Bug Fixes
v23.0.1
Compare Source
Bug Fixes
v23.0.0
Compare Source
Bug Fixes
Features
BREAKING CHANGES
https://github.com/semantic-release/env-ci/releases/tag/v11.0.0 for more information
related to https://github.com/semantic-release/semantic-release/discussions/3088
release.config.js
as the name of your config file, it needs to be moved to a.config/
directory. see https://github.com/cosmiconfig/cosmiconfig/releases/tag/v9.0.0 for more detailv22.0.12
Compare Source
Bug Fixes
v22.0.11
Compare Source
Bug Fixes
v22.0.10
Compare Source
Bug Fixes
v22.0.9
Compare Source
Bug Fixes
v22.0.8
Compare Source
Bug Fixes
v22.0.7
Compare Source
Bug Fixes
Features
v22.0.6
Compare Source
Bug Fixes
v22.0.5
Compare Source
Bug Fixes
v22.0.4
Compare Source
Bug Fixes
v22.0.3
Compare Source
Bug Fixes
exports
definition for the time being (561e2d6), closes #2968. see https://github.com/semantic-release/semantic-release/issues/2978 for more information.v22.0.2
Compare Source
Bug Fixes
v22.0.1
Compare Source
Bug Fixes
release-notes-generator
andcommit-analyzer
plugins to stable versions (041e4f7), closes #2934v22.0.0
Compare Source
Bug Fixes
Features
BREAKING CHANGES
v20.6.1 to avoid a known node bug
v21.1.2
Compare Source
Bug Fixes
v21.1.1
Compare Source
Bug Fixes
v21.1.0
Compare Source
Features
v21.0.9
Compare Source
Bug Fixes
v21.0.8
Compare Source
Bug Fixes
v21.0.7
Compare Source
Bug Fixes
v21.0.6
Compare Source
Bug Fixes
v21.0.5
Compare Source
Bug Fixes
v21.0.4
Compare Source
Bug Fixes
v21.0.3
Compare Source
Bug Fixes
@semantic-release/commit-analyzer
tov10.0.0-beta.1
(4a6b31f)@semantic-release/github
to9.0.0-beta.2
(#2818) (6f19d77)v21.0.2
Compare Source
Bug Fixes
v21.0.1
Compare Source
Bug Fixes
v21.0.0
Compare Source
BREAKING CHANGES
NPM_USERNAME
andNPM_PASSWORD
is no longer supported. UseNPM_TOKEN
instead.Bug Fixes
@semantic-release/npm
to^10.0.0
(d647433)v20.1.3
Compare Source
Bug Fixes
v20.1.2
Compare Source
Bug Fixes
v20.1.1
Compare Source
Bug Fixes
v20.1.0
Compare Source
Features
[
v20.0.4
](https://togithub.com/semantic-release/semantic-rConfiguration
📅 Schedule: Branch creation - "after 10pm every weekday,before 5am every weekday,every weekend" in timezone Europe/Moscow, 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.
This PR was generated by Mend Renovate. View the repository job log.