-
Notifications
You must be signed in to change notification settings - Fork 18
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 npm dependency semantic-release to v21.0.9 #112
Open
slauger
wants to merge
1
commit into
master
Choose a base branch
from
renovate/patch-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
slauger
force-pushed
the
renovate/patch-semantic-release-monorepo
branch
from
August 24, 2022 10:57
a27d0a4
to
9381d06
Compare
slauger
changed the title
fix(deps): update npm dependency semantic-release to v19.0.4
fix(deps): update npm dependency semantic-release to v19.0.5
Aug 24, 2022
slauger
changed the title
fix(deps): update npm dependency semantic-release to v19.0.5
fix(deps): update npm dependency semantic-release to v19.0.5 - autoclosed
Apr 25, 2023
slauger
changed the title
fix(deps): update npm dependency semantic-release to v19.0.5 - autoclosed
fix(deps): update npm dependency semantic-release to v19.0.5
May 1, 2023
slauger
force-pushed
the
renovate/patch-semantic-release-monorepo
branch
from
May 2, 2023 10:57
9381d06
to
f07be09
Compare
slauger
changed the title
fix(deps): update npm dependency semantic-release to v19.0.5
fix(deps): update npm dependency semantic-release to v21.0.2
May 2, 2023
slauger
force-pushed
the
renovate/patch-semantic-release-monorepo
branch
from
June 5, 2023 10:57
f07be09
to
e1162f4
Compare
slauger
changed the title
fix(deps): update npm dependency semantic-release to v21.0.2
fix(deps): update npm dependency semantic-release to v21.0.3
Jun 5, 2023
slauger
force-pushed
the
renovate/patch-semantic-release-monorepo
branch
from
June 12, 2023 10:57
e1162f4
to
a46128e
Compare
slauger
changed the title
fix(deps): update npm dependency semantic-release to v21.0.3
fix(deps): update npm dependency semantic-release to v21.0.5
Jun 12, 2023
slauger
force-pushed
the
renovate/patch-semantic-release-monorepo
branch
from
June 29, 2023 10:57
a46128e
to
21df1fc
Compare
slauger
changed the title
fix(deps): update npm dependency semantic-release to v21.0.5
fix(deps): update npm dependency semantic-release to v21.0.6
Jun 29, 2023
slauger
force-pushed
the
renovate/patch-semantic-release-monorepo
branch
from
July 5, 2023 11:01
21df1fc
to
8583c70
Compare
slauger
changed the title
fix(deps): update npm dependency semantic-release to v21.0.6
fix(deps): update npm dependency semantic-release to v21.0.7
Jul 5, 2023
slauger
force-pushed
the
renovate/patch-semantic-release-monorepo
branch
from
August 21, 2023 11:00
8583c70
to
dbd0fef
Compare
slauger
changed the title
fix(deps): update npm dependency semantic-release to v21.0.7
fix(deps): update npm dependency semantic-release to v21.0.9
Aug 21, 2023
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. ⚠ Warning: custom changes will be lost. |
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:
21.0.1
->21.0.9
Release Notes
semantic-release/semantic-release (semantic-release)
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
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 is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.