forked from chaijs/sinon-chai
-
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 #40
Open
renovate
wants to merge
1
commit 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
from
January 18, 2020 05:09
a96339b
to
48a9f4d
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
February 1, 2020 05:08
37a218f
to
cf16f65
Compare
renovate
bot
changed the title
Update dependency semantic-release to v16
Update dependency semantic-release to v17
Feb 1, 2020
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
February 15, 2020 05:08
cf16f65
to
3f00c21
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
April 26, 2020 07:59
3f00c21
to
15d88a5
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
July 5, 2020 23:04
15d88a5
to
fce4f1d
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
January 10, 2021 17:50
fce4f1d
to
d8a02a2
Compare
renovate
bot
changed the title
Update dependency semantic-release to v17
chore(deps): update dependency semantic-release to v17
Jan 10, 2021
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
February 13, 2021 06:24
d8a02a2
to
5757a49
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
March 6, 2021 05:16
dd09046
to
87d5eb5
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
March 13, 2021 06:29
87d5eb5
to
7165ca7
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
May 15, 2021 20:58
7165ca7
to
5a26675
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
March 26, 2022 15:20
5a26675
to
0402477
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v17
chore(deps): update dependency semantic-release to v19
Mar 26, 2022
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
June 18, 2022 16:15
0402477
to
74e0c83
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
September 25, 2022 16:13
74e0c83
to
9ea3340
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
November 20, 2022 17:58
9ea3340
to
22a8960
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
March 25, 2023 05:59
22a8960
to
a6f08f8
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v19
chore(deps): update dependency semantic-release to v21
Mar 25, 2023
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v21
chore(deps): update dependency semantic-release to v21 - autoclosed
Apr 4, 2023
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v21 - autoclosed
chore(deps): update dependency semantic-release to v21
Apr 4, 2023
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
June 3, 2023 04:24
d36f8a1
to
bc542f6
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
June 10, 2023 06:46
bc542f6
to
c579103
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:54
4e12475
to
7f2b123
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
September 24, 2023 18:53
7f2b123
to
684991a
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
November 4, 2023 07:20
684991a
to
0d1f93b
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
November 18, 2023 07:41
0d1f93b
to
f955807
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
December 9, 2023 06:20
f955807
to
006cf85
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
December 16, 2023 07:43
006cf85
to
5251dd6
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
January 13, 2024 06:35
5251dd6
to
1682122
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
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
February 10, 2024 07:55
1682122
to
cfb66db
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
March 23, 2024 04:34
865f7a3
to
4d79951
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
March 24, 2024 17:19
4d79951
to
d25772a
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
April 13, 2024 05:46
c267883
to
6159155
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
May 11, 2024 07:21
6159155
to
cf1a8c6
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
June 1, 2024 07:19
cf1a8c6
to
13b3205
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 13:49
13b3205
to
bfff524
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
September 14, 2024 04:39
bfff524
to
e42c963
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
September 28, 2024 06:21
e42c963
to
4ba1dd1
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
October 19, 2024 06:25
4ba1dd1
to
ffe1fe5
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
October 26, 2024 06:38
ffe1fe5
to
775585a
Compare
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v24
chore(deps): update dependency semantic-release to v24 - autoclosed
Dec 8, 2024
renovate
bot
changed the title
chore(deps): update dependency semantic-release to v24 - autoclosed
chore(deps): update dependency semantic-release to v24
Dec 14, 2024
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:
15.14.0
->24.2.0
Release Notes
semantic-release/semantic-release (semantic-release)
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
v17.4.4
Compare Source
Bug Fixes
v17.4.3
Compare Source
Bug Fixes
CVE-2021-23337
(#1931) (55194c1)v17.4.2
Compare Source
Bug Fixes
v17.4.1
Compare Source
Bug Fixes
marked-terminal
(#1829) (07f12b9)v17.4.0
Compare Source
Features
v17.3.9
Compare Source
Bug Fixes
v17.3.8
Compare Source
Bug Fixes
v17.3.7
Compare Source
Bug Fixes
v17.3.6
Compare Source
Bug Fixes
v17.3.5
Compare Source
Bug Fixes
v17.3.4
Compare Source
Bug Fixes
v17.3.3
Compare Source
Bug Fixes
v17.3.2
Compare Source
Bug Fixes
v17.3.1
Compare Source
Bug Fixes
v17.3.0
Compare Source
Features
v17.2.4
Compare Source
Bug Fixes
v17.2.3
Compare Source
Bug Fixes
v17.2.2
Compare Source
Bug Fixes
v17.2.1
Compare Source
Reverts
v17.2.0
Compare Source
Features
v17.1.2
Compare Source
Bug Fixes
v17.1.1
Compare Source
Bug Fixes
v17.1.0
Compare Source
Features
v17.0.8
Compare Source
Bug Fixes
v17.0.7
Compare Source
Bug Fixes
v17.0.6
Compare Source
Bug Fixes
v17.0.5
Compare Source
Bug Fixes
v17.0.4
Compare Source
Bug Fixes
repositoryUrl
in logs (55be0ba)v17.0.3
Compare Source
Bug Fixes
getGitAuthUrl
(e7bede1)v17.0.2
Compare Source
Bug Fixes
v17.0.1
Compare Source
Bug Fixes
v17.0.0
Compare Source
BREAKING CHANGES
v16.0.4
Compare Source
Bug Fixes
v16.0.3
Compare Source
Bug Fixes
--no-verify
when testing the Git permissions (b54b20d)v16.0.2
Compare Source
Bug Fixes
v16.0.1
Compare Source
Bug Fixes
v16.0.0
Compare Source
BREAKING CHANGES
v16.0.0@​beta
users only:In v16, a JSON object stored in a Git note is used to keep track of the channels on which a version has been released, the
@{channel}
suffix is no longer necessary.The tags formatted as v{version}@{channel} will now be ignored. If you have releases using this format you will have to upgrade them:
v{version}@​{channel}
{"channels":["channel1","channel2"]}
and usingnull
for the default channel (for example.{"channels":[null,"channel1","channel2"]}
)Require Node.js >= 10.13
Git CLI version 2.7.1 or higher is now required: The
--merge
option of thegit tag
command has been added in Git version 2.7.1 and is now used by semantic-releaseRegexp are not supported anymore for property matching in the
releaseRules
option.Regex are replaced by globs. For example
/core-.*/
should be changed to'core-*'
.The
branch
option has been removed in favor ofbranches
The new
branches
option expect either an Array or a single branch definition. To migrate your configuration:master
: nothing to changebranch
configuration and want to publish only from one braConfiguration
📅 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 was generated by Mend Renovate. View the repository job log.