-
Notifications
You must be signed in to change notification settings - Fork 3
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 v24 #48
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/major-semantic-release-monorepo
base: main
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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
August 20, 2023 01:19
d3c1a90
to
7162b20
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
August 20, 2023 03:55
7162b20
to
bcd05d6
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
August 24, 2023 01:37
bcd05d6
to
de0e808
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
August 24, 2023 16:57
de0e808
to
4e344b4
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
September 16, 2023 04:49
4e344b4
to
13bab83
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
from
September 16, 2023 23:04
13bab83
to
a34f583
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
September 21, 2023 14:29
a34f583
to
d45e0a7
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
September 23, 2023 02:22
d45e0a7
to
e9172e0
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
September 24, 2023 19:30
e9172e0
to
bb5575a
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
October 31, 2023 01:40
bb5575a
to
27cb3de
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
November 4, 2023 00:33
27cb3de
to
d7f760e
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
November 17, 2023 04:26
d7f760e
to
325562f
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
December 5, 2023 04:46
325562f
to
49cc539
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
March 16, 2024 08:00
4bbf119
to
ae40776
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
March 18, 2024 17:52
ae40776
to
4857602
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
March 24, 2024 18:52
4857602
to
4cbfc66
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
April 3, 2024 18:16
4cbfc66
to
84e0235
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
April 10, 2024 03:36
84e0235
to
0a9d8a3
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
May 10, 2024 18:53
0a9d8a3
to
1cc789b
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
May 10, 2024 22:37
1cc789b
to
166057e
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
June 1, 2024 02:39
166057e
to
454454f
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v23
chore(deps): update dependency semantic-release to v24
Jun 1, 2024
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
August 17, 2024 12:58
454454f
to
b6c6d45
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
September 11, 2024 04:58
b6c6d45
to
04307c5
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
September 27, 2024 22:48
04307c5
to
48411b4
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
October 19, 2024 00:09
48411b4
to
dba6024
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
October 25, 2024 20:08
dba6024
to
d16ef9c
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
January 3, 2025 04:22
d16ef9c
to
fa3e7cd
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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.4
->24.2.1
Release Notes
semantic-release/semantic-release (semantic-release)
v24.2.1
Compare Source
v24.2.0
Compare Source
Features
v24.1.3
Compare Source
Bug Fixes
v24.1.2
Compare Source
Bug Fixes
@semantic-release/github
tov11.0.0
(#3460) (43df51b)v24.1.1
Compare Source
v24.1.0
Compare Source
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
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
v17.4.7
Compare Source
Bug Fixes
v17.4.6
Compare Source
Bug Fixes
v17.4.5
Compare Source
Bug Fixes
Configuration
📅 Schedule: Branch creation - "every 3 months on the first day of the month" (UTC), 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 was generated by Mend Renovate. View the repository job log.