-
Notifications
You must be signed in to change notification settings - Fork 5
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 semantic-release to v22 #312
Closed
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
force-pushed
the
renovate/major-semantic-release
branch
from
April 1, 2023 10:40
8510bab
to
e37ff87
Compare
Error SyntaxError
Dangerfile
|
renovate
bot
force-pushed
the
renovate/major-semantic-release
branch
from
April 1, 2023 16:38
e37ff87
to
5be161d
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release
branch
3 times, most recently
from
April 15, 2023 10:05
ac9251b
to
366d195
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release
branch
2 times, most recently
from
April 29, 2023 00:55
f84b1d7
to
6a288f2
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release
branch
from
May 6, 2023 02:25
6a288f2
to
56b328b
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release
branch
3 times, most recently
from
June 3, 2023 04:38
7f8d7e5
to
20f40e8
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release
branch
3 times, most recently
from
June 10, 2023 00:15
1b6cf81
to
29b76c9
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release
branch
2 times, most recently
from
June 29, 2023 01:37
d0ececc
to
ee1fbe8
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release
branch
from
July 5, 2023 04:22
ee1fbe8
to
e698d60
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release
branch
2 times, most recently
from
July 15, 2023 06:09
7340e92
to
7eab59f
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release
branch
from
July 22, 2023 03:51
7eab59f
to
c7b9909
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release
branch
2 times, most recently
from
August 5, 2023 03:36
07edc83
to
215aa0c
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release
branch
from
August 12, 2023 03:12
215aa0c
to
63d3934
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release
branch
5 times, most recently
from
August 26, 2023 04:18
4aa9ce4
to
6fb5f2c
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release
branch
2 times, most recently
from
September 16, 2023 03:44
259258b
to
601b7e5
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release
branch
from
September 16, 2023 07:09
601b7e5
to
2e69947
Compare
renovate
bot
changed the title
chore(deps): update semantic-release to v21
chore(deps): update semantic-release to v22
Sep 16, 2023
renovate
bot
force-pushed
the
renovate/major-semantic-release
branch
4 times, most recently
from
September 23, 2023 03:32
8fb0c5c
to
24d8ca8
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release
branch
2 times, most recently
from
September 30, 2023 04:46
8af38ef
to
e9f12fd
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release
branch
4 times, most recently
from
October 21, 2023 11:10
8bcad9a
to
4b3244e
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release
branch
5 times, most recently
from
November 4, 2023 03:09
013d375
to
858f0a7
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release
branch
2 times, most recently
from
November 11, 2023 06:28
7852bf2
to
bdcdf48
Compare
| datasource | package | from | to | | ---------- | ---------------- | ------ | ------ | | npm | semantic-release | 20.1.3 | 22.0.7 |
renovate
bot
force-pushed
the
renovate/major-semantic-release
branch
from
November 12, 2023 06:47
bdcdf48
to
2d3634d
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:
20.1.3
->22.0.7
Release Notes
semantic-release/semantic-release (semantic-release)
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)Configuration
📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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 has been generated by Mend Renovate. View repository job log here.