-
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 semantic-release monorepo (major) #81
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 13:53
0ec80e8
to
877fa3f
Compare
renovate
bot
changed the title
chore(deps): update dependency travis-deploy-once to v5
chore(deps): update semantic-release monorepo (major)
Jan 18, 2020
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
February 8, 2020 12:57
877fa3f
to
f34790f
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
February 16, 2020 05:59
f34790f
to
befd95f
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
March 10, 2020 13:58
befd95f
to
636a169
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
April 26, 2020 08:59
636a169
to
71debf3
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
June 30, 2020 12:57
71debf3
to
2c639e3
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
October 25, 2020 17:58
2c639e3
to
1aced4c
Compare
renovate
bot
changed the title
chore(deps): update semantic-release monorepo (major)
chore(deps): update dependency travis-deploy-once to v5
Nov 24, 2020
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
January 5, 2021 13:49
1aced4c
to
d46e29b
Compare
renovate
bot
changed the title
chore(deps): update dependency travis-deploy-once to v5
chore(deps): update semantic-release monorepo (major)
Jan 5, 2021
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
January 23, 2021 14:58
d46e29b
to
1f430c4
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
February 10, 2021 11:43
1f430c4
to
8eb5c3d
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
April 26, 2021 16:30
8eb5c3d
to
e2c66e5
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
May 15, 2021 19:29
e2c66e5
to
50c6002
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
October 19, 2021 01:00
50c6002
to
ea1c7be
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
March 7, 2022 17:29
ea1c7be
to
ae5e335
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
June 18, 2022 19:45
ae5e335
to
afe201c
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
September 25, 2022 20:13
afe201c
to
845c4b8
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
March 16, 2023 23:48
845c4b8
to
b6610f4
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
March 24, 2023 23:27
b6610f4
to
db1b9a8
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
April 3, 2023 09:23
db1b9a8
to
e810319
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
June 2, 2023 22:50
56aeb99
to
6ae3f9f
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
June 10, 2023 00:48
03a7060
to
aef5a9c
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
July 5, 2023 01:35
14a4679
to
6f5c073
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
August 20, 2023 04:58
01e5815
to
4ededbf
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
August 24, 2023 16:38
b9bab4a
to
47920b5
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
5 times, most recently
from
September 23, 2023 02:28
6a2a13a
to
c7ab260
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
September 24, 2023 19:31
c7ab260
to
d454348
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
November 3, 2023 21:44
c97d756
to
7382ce9
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
November 17, 2023 04:15
7382ce9
to
8dd3303
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
3 times, most recently
from
December 12, 2023 00:04
e923613
to
15c039b
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
December 12, 2023 06:17
15c039b
to
fd0635b
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
January 13, 2024 00:37
fd0635b
to
497e02f
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
February 7, 2024 15:27
3fa3699
to
72f1e1e
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
3 times, most recently
from
March 18, 2024 15:09
d5a37ac
to
31de768
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
March 24, 2024 15:54
31de768
to
69dcbc2
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
2 times, most recently
from
April 9, 2024 21:41
8a5f4ec
to
48cd3dd
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
May 10, 2024 20:07
48cd3dd
to
0a4b94e
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
June 1, 2024 02:53
0a4b94e
to
6cc96a5
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
August 17, 2024 14:20
6cc96a5
to
236cfcb
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
September 11, 2024 06:57
236cfcb
to
e989e46
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
September 27, 2024 19:57
e989e46
to
8b03935
Compare
renovate
bot
force-pushed
the
renovate/major-semantic-release-monorepo
branch
from
October 19, 2024 01:16
8b03935
to
d2eca62
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:
15.13.3
->24.1.3
4.4.1
->5.0.11
Release Notes
semantic-release/semantic-release (semantic-release)
v24.1.3
Compare Source
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:/semantic-release/env-ci/releases/tag/v11.0.0 for more information
related to https:/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:/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:/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:Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.