-
Notifications
You must be signed in to change notification settings - Fork 109
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 v22 #504
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-monorepo
branch
from
September 18, 2021 05:28
e0e03c8
to
d9a5e93
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
October 2, 2021 07:36
d9a5e93
to
01c8f5a
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
October 9, 2021 08:03
01c8f5a
to
d2fb461
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
3 times, most recently
from
October 23, 2021 08:36
9cfce5f
to
ce64fa8
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
October 23, 2021 08:50
ce64fa8
to
d066586
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
October 30, 2021 09:37
d848d7c
to
6c75a33
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
November 6, 2021 09:28
6c75a33
to
3d21667
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
November 20, 2021 09:01
13fbf3e
to
c015b6d
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
5 times, most recently
from
November 30, 2021 21:11
a747504
to
94d15a6
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
December 4, 2021 08:22
94d15a6
to
4deffab
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v18
chore(deps): update dependency semantic-release to v19
Jan 22, 2022
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
January 22, 2022 05:30
4deffab
to
918d8ed
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
4 times, most recently
from
May 16, 2022 02:38
0b26fc3
to
0ea3472
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
May 28, 2022 05:59
0ea3472
to
7f5ba81
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
June 11, 2022 04:52
7f5ba81
to
9f97dfa
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
July 23, 2022 05:22
9f97dfa
to
91a1b09
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
September 25, 2022 11:14
91a1b09
to
a95ab88
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v19
chore(deps): update dependency semantic-release to v20
Mar 18, 2023
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
March 18, 2023 04:51
a95ab88
to
3e94efe
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
May 13, 2023 05:06
cbf09d5
to
c0a2d23
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
May 27, 2023 05:10
2a86a4f
to
b0d15e2
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
June 3, 2023 08:08
b0d15e2
to
f7c03a8
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
June 17, 2023 04:43
f7c03a8
to
e444172
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
July 8, 2023 07:17
3e4583c
to
0456616
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
July 15, 2023 07:27
0456616
to
dfd1f95
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
August 12, 2023 04:15
b429c0d
to
861b885
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
3 times, most recently
from
August 26, 2023 04:56
f3cf082
to
217bb40
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
September 9, 2023 06:48
217bb40
to
37eb291
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
September 16, 2023 07:18
37eb291
to
b08e339
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v21
chore(deps): update dependency semantic-release to v22
Sep 16, 2023
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
September 23, 2023 06:15
35aa434
to
b2a95fb
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
September 24, 2023 19:25
b2a95fb
to
16ed539
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
October 7, 2023 07:31
16ed539
to
b4ae16b
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
3 times, most recently
from
October 15, 2023 17:45
65fc4bd
to
0186d01
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
November 4, 2023 07:19
63d063f
to
c4cac54
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
November 11, 2023 06:09
c4cac54
to
733ae86
Compare
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |
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:
17.4.7
->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)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
v19.0.5
Compare Source
Reverts
v19.0.4
Compare Source
Bug Fixes
v19.0.3
Compare Source
Bug Fixes
v19.0.2
Compare Source
Bug Fixes
v19.0.1
Compare Source
Bug Fixes
v19.0.0
Compare Source
Bug Fixes
marked
to resolve ReDos vulnerability (#2330) (d9e5bc0)BREAKING CHANGES
@semantic-release/npm
has also dropped support for node v15marked
andmarked-terminal
that resolved the ReDoS vulnerability. removal of support of this node version should be low since it was not an LTS version and has been EOL for several months already.v18.0.1
Compare Source
Bug Fixes
v18.0.0
Compare Source
This is a maintenance release. An increasing amount of dependencies required a node version higher than the Node 10 version supported by
semantic-release@17
. We decided to go straight to a recent Node LTS version because the release build is usually independent of others, requiring a higher node version is less disruptive to users, but helps us reduce the maintenance overhead.If you use GitHub Actions and need to bump the node version set up by
actions/node-setup
, you can useoctoherd-script-bump-node-version-in-workflows
BREAKING CHANGES
node-version: the minimum required version of node is now v14.17
Configuration
📅 Schedule: Branch creation - "every weekend" in timezone America/New_York, 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 has been generated by Mend Renovate. View repository job log here.