-
Notifications
You must be signed in to change notification settings - Fork 32
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 v23 #310
Open
renovate
wants to merge
2
commits into
master
Choose a base branch
from
renovate/major-semantic-release-monorepo
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
2 times, most recently
from
January 8, 2023 07:39
29b7e5a
to
7aa43d3
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
January 28, 2023 06:13
7aa43d3
to
f07b544
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
March 19, 2023 02:10
f07b544
to
fce4557
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v20
chore(deps): update dependency semantic-release to v21
May 28, 2023
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
June 3, 2023 04:47
14f3dff
to
f14171b
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
June 10, 2023 04:26
f14171b
to
5e09023
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
July 8, 2023 04:44
392c69e
to
32cbd53
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
3 times, most recently
from
August 26, 2023 05:37
59426c7
to
9d8c35a
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
September 16, 2023 07:41
9d8c35a
to
193c990
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 04:54
a42b1f2
to
15b8760
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
September 24, 2023 16:56
15b8760
to
0d54502
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
November 4, 2023 04:38
0d54502
to
63eb2b5
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
November 18, 2023 06:58
63eb2b5
to
cf1ec53
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
December 16, 2023 06:33
10f91b4
to
1524ca4
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
January 13, 2024 08:00
1524ca4
to
1a52b51
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v22
chore(deps): update dependency semantic-release to v23
Jan 13, 2024
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
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:
19.0.5
->23.0.0
Release Notes
semantic-release/semantic-release (semantic-release)
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 - "every weekend" in timezone America/New_York, 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.