-
-
Notifications
You must be signed in to change notification settings - Fork 1
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) #373
base: master
Are you sure you want to change the base?
Conversation
Hey! Changelogs info seems to be missing or might be in incorrect format. |
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. |
🏷️ [bumpr] Next version:v2.0.2 Changes:v2.0.1...AlexRogalskiy:renovate/major-semantic-release-monorepo |
93fa578
to
7dac948
Compare
Pull request by bot. No need to analyze |
7dac948
to
8d6d8d1
Compare
8d6d8d1
to
eede372
Compare
eede372
to
6406a58
Compare
6406a58
to
771ba47
Compare
771ba47
to
d2eea18
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
|
d2eea18
to
7e19e82
Compare
058fd90
to
7fa2467
Compare
7fa2467
to
e0b056a
Compare
84fbb71
to
b1e433d
Compare
b1e433d
to
f3c6b0d
Compare
f3c6b0d
to
2b39a4b
Compare
2b39a4b
to
4f282ae
Compare
f0c5ce9
to
0777c18
Compare
519de82
to
7a53bb3
Compare
4ba181a
to
97df497
Compare
97df497
to
51e2ed0
Compare
51e2ed0
to
f48bcff
Compare
562a7b3
to
6bfbc9e
Compare
6bfbc9e
to
0c9eb53
Compare
0280e1e
to
aca2791
Compare
aca2791
to
f715bbe
Compare
0454eee
to
810c1c7
Compare
f7c65b9
to
fc9113c
Compare
ae7a734
to
c167502
Compare
c167502
to
4779544
Compare
8a8a0bd
to
24f2333
Compare
24f2333
to
ea065a3
Compare
ea065a3
to
76c0c01
Compare
This PR contains the following updates:
^5.0.1
->^6.0.3
^8.0.1
->^13.0.0
^9.0.0
->^10.0.1
^7.2.0
->^10.3.5
^7.0.10
->^12.0.1
^9.0.1
->^14.0.1
Release Notes
semantic-release/changelog (@semantic-release/changelog)
v6.0.3
Compare Source
Bug Fixes
v6.0.2
Compare Source
Bug Fixes
v6.0.1
Compare Source
Bug Fixes
v6.0.0
Compare Source
Features
BREAKING CHANGES
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)
v11.1.0
Compare Source
Features
v11.0.0
Compare Source
Bug Fixes
Features
BREAKING CHANGES
v10.0.4
Compare Source
Bug Fixes
v10.0.3
Compare Source
Reverts
v10.0.2
Compare Source
Bug Fixes
v10.0.1
Compare Source
Bug Fixes
v10.0.0
Compare Source
Code Refactoring
Features
BREAKING CHANGES
loading ESM plugins
@semantic-release/commit-analyzer
is now a native ES Module. It has named exportsfor each plugin hook (
analyzeCommits
)v9.0.2
Compare Source
Bug Fixes
v9.0.1
Compare Source
Bug Fixes
v9.0.0
Compare Source
Features
BREAKING CHANGES
semantic-release/git (@semantic-release/git)
v10.0.1
Compare Source
Bug Fixes
v10.0.0
Compare Source
Features
BREAKING CHANGES
v9.0.1
Compare Source
Bug Fixes
semantic-release/github (@semantic-release/github)
v10.3.5
Compare Source
Bug Fixes
searchAPI
usage withGraphQL
infindSRIssue
util (#907) (7fb46a3)v10.3.4
Compare Source
v10.3.3
Compare Source
Bug Fixes
v10.3.2
Compare Source
Bug Fixes
"PullRequest".canBeRebased
field on GHES graphql api (#913) (4393578)v10.3.1
Compare Source
Bug Fixes
max_node_limit_exceeded
error when fetching associatedPRs (#912) (bb806af)v10.3.0
Compare Source
Features
v10.2.0
Compare Source
Features
v10.1.7
Compare Source
Bug Fixes
v10.1.6
Compare Source
v10.1.5
Compare Source
Bug Fixes
v10.1.4
Compare Source
Bug Fixes
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 Modulev8.1.0
Compare Source
Features
v8.0.9
Compare Source
Bug Fixes
v8.0.8
Compare Source
Bug Fixes
v8.0.7
Compare Source
Bug Fixes
v8.0.6
Compare Source
Bug Fixes
v8.0.5
Compare Source
Bug Fixes
v8.0.4
Compare Source
Bug Fixes
v8.0.3
Compare Source
Bug Fixes
v8.0.2
Compare Source
Bug Fixes
v8.0.1
Compare Source
Bug Fixes
v8.0.0
Compare Source
BREAKING CHANGES
v7.2.3
Compare Source
Bug Fixes
v7.2.2
Compare Source
Bug Fixes
v7.2.1
Compare Source
Bug Fixes
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
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
)v9.0.2
Compare Source
Bug Fixes
v9.0.1
Compare Source
Bug Fixes
preferLocal
option for execa call (#458) (c817a88)v9.0.0
Compare Source
Bug Fixes
preferLocal
option to allow execa to use local npm version (#445) (002439e)semantic-release
to the new stable version (575a5a4)semantic-release
to a version matching the engines definition of this package (2d1f5f2)BREAKING CHANGES
semantic-release
has been raised to match theengines.node
requirements of this packageCo-authored-by: Matt Travi programmer@travi.org
v8.0.3
Compare Source
Reverts
v8.0.2
Compare Source
Bug Fixes
v8.0.1
Compare Source
Bug Fixes
v8.0.0
Compare Source
Features
BREAKING CHANGES
Co-authored-by: Matt Travi programmer@travi.org
v7.1.3
Compare Source
Bug Fixes
v7.1.2
Compare Source
Bug Fixes
v7.1.1
Compare Source
Bug Fixes
v7.1.0
Compare Source
Features
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
](https://redirect.github.com/semConfiguration
📅 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 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 was generated by Mend Renovate. View the repository job log.