-
Notifications
You must be signed in to change notification settings - Fork 2
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 #16
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/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
renovate
bot
force-pushed
the
renovate/semantic-release-monorepo
branch
5 times, most recently
from
November 6, 2023 02:23
ad0e895
to
7c453fd
Compare
renovate
bot
force-pushed
the
renovate/semantic-release-monorepo
branch
from
November 17, 2023 02:15
7c453fd
to
4b437ca
Compare
renovate
bot
force-pushed
the
renovate/semantic-release-monorepo
branch
4 times, most recently
from
December 12, 2023 00:41
d901ee3
to
944e840
Compare
renovate
bot
force-pushed
the
renovate/semantic-release-monorepo
branch
from
December 12, 2023 06:57
944e840
to
c9640b1
Compare
renovate
bot
force-pushed
the
renovate/semantic-release-monorepo
branch
from
January 13, 2024 00:23
c9640b1
to
e0f0614
Compare
renovate
bot
force-pushed
the
renovate/semantic-release-monorepo
branch
2 times, most recently
from
February 7, 2024 15:30
9a4803f
to
064cdec
Compare
renovate
bot
force-pushed
the
renovate/semantic-release-monorepo
branch
from
March 2, 2024 01:26
064cdec
to
fd78951
Compare
renovate
bot
force-pushed
the
renovate/semantic-release-monorepo
branch
4 times, most recently
from
March 18, 2024 14:57
3ae8df5
to
21ec2ce
Compare
renovate
bot
force-pushed
the
renovate/semantic-release-monorepo
branch
2 times, most recently
from
March 24, 2024 17:53
43879eb
to
60bf843
Compare
renovate
bot
force-pushed
the
renovate/semantic-release-monorepo
branch
2 times, most recently
from
April 9, 2024 21:35
186fdad
to
f89814b
Compare
renovate
bot
force-pushed
the
renovate/semantic-release-monorepo
branch
2 times, most recently
from
May 10, 2024 19:48
04ee26c
to
3e1ee40
Compare
renovate
bot
force-pushed
the
renovate/semantic-release-monorepo
branch
from
June 1, 2024 02:43
3e1ee40
to
a2d7158
Compare
renovate
bot
force-pushed
the
renovate/semantic-release-monorepo
branch
from
June 22, 2024 07:52
a2d7158
to
96370fb
Compare
renovate
bot
force-pushed
the
renovate/semantic-release-monorepo
branch
from
August 17, 2024 13:46
96370fb
to
3e8ba5e
Compare
renovate
bot
force-pushed
the
renovate/semantic-release-monorepo
branch
from
September 11, 2024 08:07
3e8ba5e
to
5b22c41
Compare
renovate
bot
force-pushed
the
renovate/semantic-release-monorepo
branch
from
September 27, 2024 18:02
5b22c41
to
0054e30
Compare
renovate
bot
force-pushed
the
renovate/semantic-release-monorepo
branch
from
October 19, 2024 00:43
0054e30
to
d1499eb
Compare
renovate
bot
force-pushed
the
renovate/semantic-release-monorepo
branch
from
October 25, 2024 23:11
d1499eb
to
db9e181
Compare
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:
10.0.4
->12.0.1
11.0.4
->14.0.1
21.0.7
->24.2.0
Release Notes
semantic-release/npm (@semantic-release/npm)
v12.0.1
Compare Source
Bug Fixes
v12.0.0
Compare Source
Features
exports
to point at ./index.js (9e193c2)BREAKING CHANGES
exports
has been defined, which prevents access to private apis (which arentintended for consumption anyway)
v11.0.3
Compare Source
Bug Fixes
even though our existing range allowed anyone to update as soon as the new npm version was available, this will encourage being on a version that does not report the ip vulnerability a bit more forcefully
v11.0.2
Compare Source
Bug Fixes
v11.0.1
Compare Source
Bug Fixes
v11.0.0
Compare Source
Bug Fixes
Features
BREAKING CHANGES
v10.0.6
Compare Source
Bug Fixes
v10.0.5
Compare Source
Bug Fixes
semantic-release/release-notes-generator (@semantic-release/release-notes-generator)
v14.0.1
Compare Source
Bug Fixes
v14.0.0
Compare Source
Features
BREAKING CHANGES
v13.0.0
Compare Source
Features
exports
to point at ./index.js (5655b18)BREAKING CHANGES
exports
has been defined, which prevents access to private apis (which arentintended for consumption anyway)
v12.1.0
Compare Source
Features
v12.0.1
Compare Source
Bug Fixes
v12.0.0
Compare Source
Bug Fixes
Features
BREAKING CHANGES
v11.0.7
Compare Source
Bug Fixes
v11.0.6
Compare Source
Reverts
v11.0.5
Compare Source
Bug Fixes
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
Configuration
📅 Schedule: Branch creation - "before 4am on the first day of the month" in timezone Europe/Berlin, 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.