-
-
Notifications
You must be signed in to change notification settings - Fork 66
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 dependency semantic-release to v24 #125
base: master
Are you sure you want to change the base?
Conversation
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/semantic-release@21.1.2 |
366f154
to
df0873b
Compare
ae96bc6
to
b806f2a
Compare
b806f2a
to
78d6744
Compare
8eedf3f
to
8dd2a51
Compare
8dd2a51
to
7a09928
Compare
7a09928
to
d994b4d
Compare
87fd64e
to
25dce50
Compare
45002f7
to
74cc29f
Compare
74cc29f
to
e37dc3e
Compare
a6aa3bd
to
300ca14
Compare
300ca14
to
977ef70
Compare
977ef70
to
1ce83ec
Compare
1ce83ec
to
dca61c9
Compare
dca61c9
to
734e09b
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 obfuscated code?Obfuscated files are intentionally packed to hide their behavior. This could be a sign of malware. Packages should not obfuscate their code. Consider not using packages with obfuscated code 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
|
This PR contains the following updates:
21.1.2
->24.1.1
Release Notes
semantic-release/semantic-release (semantic-release)
v24.1.1
Compare Source
v24.1.0
Compare Source
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
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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.