-
Notifications
You must be signed in to change notification settings - Fork 0
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
fix(deps): update dependencies #93
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/dependencies
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.
Open
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/dependencies
branch
2 times, most recently
from
March 23, 2023 22:48
76a6d4f
to
bc0c9b0
Compare
renovate
bot
force-pushed
the
renovate/dependencies
branch
from
April 3, 2023 11:22
bc0c9b0
to
d146bdc
Compare
renovate
bot
force-pushed
the
renovate/dependencies
branch
from
April 17, 2023 11:26
d146bdc
to
eb9dbf6
Compare
renovate
bot
force-pushed
the
renovate/dependencies
branch
5 times, most recently
from
June 3, 2023 21:48
e233d13
to
eb261bf
Compare
renovate
bot
force-pushed
the
renovate/dependencies
branch
4 times, most recently
from
June 10, 2023 00:43
879ca1a
to
d539569
Compare
renovate
bot
force-pushed
the
renovate/dependencies
branch
3 times, most recently
from
June 19, 2023 10:19
9d627f0
to
fe33cc0
Compare
renovate
bot
force-pushed
the
renovate/dependencies
branch
2 times, most recently
from
July 4, 2023 17:23
c4dc758
to
396bbd0
Compare
renovate
bot
force-pushed
the
renovate/dependencies
branch
2 times, most recently
from
July 9, 2023 10:21
4efeac0
to
ee434bb
Compare
renovate
bot
force-pushed
the
renovate/dependencies
branch
3 times, most recently
from
July 19, 2023 12:39
328ad4e
to
fc8ce19
Compare
renovate
bot
force-pushed
the
renovate/dependencies
branch
2 times, most recently
from
August 1, 2023 15:14
ed2b2c2
to
2cd4ef7
Compare
renovate
bot
force-pushed
the
renovate/dependencies
branch
from
August 9, 2023 13:12
2cd4ef7
to
f08167f
Compare
renovate
bot
force-pushed
the
renovate/dependencies
branch
2 times, most recently
from
August 22, 2023 16:09
5d6e635
to
916b6da
Compare
renovate
bot
force-pushed
the
renovate/dependencies
branch
from
August 27, 2023 02:27
916b6da
to
51a0af8
Compare
renovate
bot
force-pushed
the
renovate/dependencies
branch
2 times, most recently
from
June 5, 2024 03:53
99c49b7
to
89433d6
Compare
renovate
bot
force-pushed
the
renovate/dependencies
branch
from
June 22, 2024 07:46
89433d6
to
ddcd9bb
Compare
renovate
bot
force-pushed
the
renovate/dependencies
branch
3 times, most recently
from
July 8, 2024 16:34
7323d9b
to
579803a
Compare
renovate
bot
force-pushed
the
renovate/dependencies
branch
4 times, most recently
from
July 26, 2024 04:14
f4e6106
to
bd7216d
Compare
renovate
bot
force-pushed
the
renovate/dependencies
branch
2 times, most recently
from
August 9, 2024 21:03
65597f6
to
30d67b9
Compare
renovate
bot
force-pushed
the
renovate/dependencies
branch
3 times, most recently
from
August 20, 2024 22:26
b97b080
to
595eba4
Compare
renovate
bot
force-pushed
the
renovate/dependencies
branch
3 times, most recently
from
September 3, 2024 20:20
4b94c1e
to
5662947
Compare
renovate
bot
force-pushed
the
renovate/dependencies
branch
2 times, most recently
from
September 5, 2024 22:51
b6b1d90
to
bad025c
Compare
renovate
bot
force-pushed
the
renovate/dependencies
branch
2 times, most recently
from
September 20, 2024 18:49
8fdf5df
to
10026c5
Compare
renovate
bot
force-pushed
the
renovate/dependencies
branch
from
September 24, 2024 23:19
10026c5
to
2962d88
Compare
renovate
bot
force-pushed
the
renovate/dependencies
branch
from
October 9, 2024 11:25
2962d88
to
1bfd409
Compare
renovate
bot
force-pushed
the
renovate/dependencies
branch
from
November 6, 2024 19:00
1bfd409
to
911f9bb
Compare
renovate
bot
force-pushed
the
renovate/dependencies
branch
3 times, most recently
from
December 8, 2024 23:24
a712dcc
to
215d9b7
Compare
renovate
bot
force-pushed
the
renovate/dependencies
branch
from
December 16, 2024 21:49
215d9b7
to
c1fca15
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:
6.0.1
->6.0.3
^9.0.2
->^13.0.0
^8.0.4
->^11.0.0
^9.0.1
->^12.0.0
^10.0.3
->^14.0.0
Release Notes
semantic-release/changelog (@semantic-release/changelog)
v6.0.3
Compare Source
Bug Fixes
v6.0.2
Compare Source
Bug Fixes
semantic-release/commit-analyzer (@semantic-release/commit-analyzer)
v13.0.0
Compare Source
Bug Fixes
Features
BREAKING CHANGES
dropping support for previous major versions of those packages due to the breaking changes between
majors. this only impacts your project if you are installing alongside semantic-release, so updating
those packages to latest version should be the only change you need for this update. no action
should be necessary if you are using default semantic-release config
v12.0.0
Compare Source
Features
exports
to point at ./index.js (f3358dd)BREAKING CHANGES
exports
has been defined, which prevents access to private apis (which arentintended for consumption anyway)
v11.1.0
Compare Source
Features
v11.0.0
Compare Source
Bug Fixes
Features
BREAKING CHANGES
v10.0.4
Compare Source
Bug Fixes
v10.0.3
Compare Source
Reverts
v10.0.2
Compare Source
Bug Fixes
v10.0.1
Compare Source
Bug Fixes
v10.0.0
Compare Source
Code Refactoring
Features
BREAKING CHANGES
loading ESM plugins
@semantic-release/commit-analyzer
is now a native ES Module. It has named exportsfor each plugin hook (
analyzeCommits
)semantic-release/github (@semantic-release/github)
v11.0.1
Compare Source
Bug Fixes
v11.0.0
Compare Source
chore
semantic-release
(95c7cdd)Code Refactoring
label
property data type. (718134a)Features
warn
infail
script (7a9914a)warn
insuccess
script (792720d)BREAKING CHANGES
label
prop is now an array of objects with more properties@semantic-release/github is now v24.1.0
v10.3.5
Compare Source
Bug Fixes
searchAPI
usage withGraphQL
infindSRIssue
util (#907) (7fb46a3)v10.3.4
Compare Source
v10.3.3
Compare Source
Bug Fixes
v10.3.2
Compare Source
Bug Fixes
"PullRequest".canBeRebased
field on GHES graphql api (#913) (4393578)v10.3.1
Compare Source
Bug Fixes
max_node_limit_exceeded
error when fetching associatedPRs (#912) (bb806af)v10.3.0
Compare Source
Features
v10.2.0
Compare Source
Features
v10.1.7
Compare Source
Bug Fixes
v10.1.6
Compare Source
v10.1.5
Compare Source
Bug Fixes
v10.1.4
Compare Source
Bug Fixes
v10.1.3
Compare Source
Bug Fixes
v10.1.2
Compare Source
Bug Fixes
v10.1.1
Compare Source
Bug Fixes
v10.1.0
Compare Source
Features
v10.0.7
Compare Source
Bug Fixes
v10.0.6
Compare Source
Bug Fixes
v10.0.5
Compare Source
Bug Fixes
v10.0.4
Compare Source
Bug Fixes
v10.0.3
Compare Source
v10.0.2
Compare Source
Bug Fixes
v10.0.1
Compare Source
Bug Fixes
v10.0.0
Compare Source
Features
BREAKING CHANGES
v9.2.6
Compare Source
Bug Fixes
v9.2.5
Compare Source
Bug Fixes
v9.2.4
Compare Source
Bug Fixes
v9.2.3
Compare Source
Bug Fixes
v9.2.2
Compare Source
Bug Fixes
v9.2.1
Compare Source
v9.2.0
Compare Source
Features
v9.1.0
Compare Source
Features
releaseNameTemplate
andreleaseBodyTemplate
options for customizing release body and name (#704) (9e2678c)v9.0.7
Compare Source
Bug Fixes
v9.0.6
Compare Source
Bug Fixes
v9.0.5
Compare Source
Bug Fixes
v9.0.4
Compare Source
Bug Fixes
v9.0.3
Compare Source
Bug Fixes
v9.0.2
Compare Source
Bug Fixes
v9.0.1
Compare Source
Bug Fixes
v9.0.0
Compare Source
BREAKING CHANGES
@semantic-release/github
is now a native ES Modulev8.1.0
Compare Source
Features
v8.0.9
Compare Source
Bug Fixes
v8.0.8
Compare Source
Bug Fixes
v8.0.7
Compare Source
Bug Fixes
v8.0.6
Compare Source
Bug Fixes
v8.0.5
Compare Source
Bug Fixes
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
v10.0.4
Compare Source
Bug Fixes
v10.0.3
Compare Source
Bug Fixes
v10.0.2
Compare Source
Bug Fixes
v10.0.1
Compare Source
Bug Fixes
v10.0.0
Compare Source
Bug Fixes
Code Refactoring
Features
BREAKING CHANGES
can be found at https://github.com/npm/cli/releases/tag/v9.0.0
raised to v20.1.0 in order to support loading of ESM plugins
errors
propertyNPM_USERNAME
andNPM_PASSWORD
is no longer supported. UseNPM_TOKEN
instead.@semantic-release/npm
is now a native ES Module. Ithas named exports for each plugin hook (
verifyConditions
,prepare
,publish
,addChannel
)v9.0.2
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
v11.0.4
Compare Source
Bug Fixes
v11.0.3
Compare Source
Bug Fixes
v11.0.2
Compare Source
Bug Fixes
v11.0.1
Compare Source
Bug Fixes
v11.0.0
Compare Source
Code Refactoring
Features
BREAKING CHANGES
@semantic-release/release-notes-generator
is now a native ES Module. It hasnamed exports for each plugin hook (
generateNotes
)Configuration
📅 Schedule: Branch creation - "every weekend" (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.
👻 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.