-
-
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
chore(npm): update semantic-release monorepo (major) #197
base: develop
Are you sure you want to change the base?
Conversation
b9b882f
to
53d68e6
Compare
e68fcab
to
272f14a
Compare
af729b4
to
c740fcb
Compare
c740fcb
to
ac9a208
Compare
ac9a208
to
2a50f41
Compare
cebe056
to
b3584f7
Compare
4416d3e
to
2cee04a
Compare
a9352c0
to
fe92485
Compare
fe92485
to
13c13e9
Compare
31fa3ea
to
f829dea
Compare
⚠ Artifact update problemRenovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below: File name: pnpm-lock.yaml
|
a684daa
to
1ebb5c1
Compare
1ebb5c1
to
ab5a864
Compare
2e2274e
to
3e5c673
Compare
b51054f
to
54f3092
Compare
dc3a9f6
to
db512ba
Compare
21dbe6c
to
5e092e6
Compare
5e092e6
to
84d1796
Compare
|
8f56402
to
65d910e
Compare
8722c92
to
f8e2409
Compare
f8e2409
to
0a5a7f4
Compare
This PR contains the following updates:
9.0.2
->13.0.0
9.0.2
->12.0.1
10.0.3
->14.0.0
19.0.5
->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)
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
)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
)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)
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
Compare Source
Bug Fixes
v20.0.3
Compare Source
Reverts
v20.0.2
Compare Source
Bug Fixes
v20.0.1
Compare Source
Bug Fixes
v20.0.0
Compare Source
BREAKING CHANGES
Features
Bug Fixes
Configuration
📅 Schedule: Branch creation - "after 8:00 pm" in timezone Asia/Tokyo, 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.