-
-
Notifications
You must be signed in to change notification settings - Fork 10
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(dev-deps): update semantic-release monorepo (major) #351
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
added
💙
Renovate
Type: Maintenance
Generic maintenance tasks, e.g., package updates.
labels
Apr 17, 2023
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #351 +/- ##
=======================================
Coverage 99.50% 99.50%
=======================================
Files 8 8
Lines 1224 1224
Branches 111 111
=======================================
Hits 1218 1218
Misses 6 6 ☔ View full report in Codecov by Sentry. |
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
10 times, most recently
from
April 17, 2023 04:07
d7ec036
to
4794e2c
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
April 29, 2023 01:14
46822ae
to
8caf424
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
4 times, most recently
from
June 3, 2023 22:29
cbe4e03
to
c824e69
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
5 times, most recently
from
June 10, 2023 03:50
eeb76cb
to
ff7200a
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
3 times, most recently
from
July 5, 2023 01:24
a1aa8c2
to
31c949f
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
July 7, 2023 04:15
31c949f
to
e5029e9
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
July 19, 2023 10:46
27f981c
to
af5d35a
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
November 9, 2023 21:09
aab7f69
to
14a70aa
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
November 17, 2023 02:16
14a70aa
to
266a1c2
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
4 times, most recently
from
December 7, 2023 18:32
9be8f00
to
2169b23
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
December 12, 2023 06:38
0ff7f1c
to
c1f6b07
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
December 22, 2023 22:22
c1f6b07
to
9c2d684
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
January 13, 2024 03:51
9c2d684
to
ca19afa
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
January 22, 2024 00:48
ca19afa
to
1ad198d
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
February 7, 2024 15:22
e719f77
to
c5ea869
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
March 2, 2024 00:05
c5ea869
to
750b35b
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
5 times, most recently
from
March 18, 2024 15:00
0feaca0
to
e158749
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
March 24, 2024 17:39
6087b7b
to
b8f2606
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
3 times, most recently
from
April 9, 2024 23:35
b2f19ce
to
1c5332c
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
May 10, 2024 20:03
ca39f4c
to
aea914a
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
May 16, 2024 02:04
aea914a
to
e7fd1ef
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
9.0.2
->12.0.0
8.0.7
->10.0.4
9.0.2
->12.0.1
10.0.3
->13.0.0
20.1.3
->23.1.1
Release Notes
semantic-release/commit-analyzer (@semantic-release/commit-analyzer)
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/github (@semantic-release/github)
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
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)
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)
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](https://togithub.com/semantic-release/semantic-release/commit/6f19d77e54e21ae3a4Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.