-
Notifications
You must be signed in to change notification settings - Fork 12
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 @favware/cliff-jumper to v4 - autoclosed #366
Closed
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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #366 +/- ##
=======================================
Coverage 69.02% 69.02%
=======================================
Files 4 4
Lines 3548 3548
Branches 265 265
=======================================
Hits 2449 2449
Misses 1035 1035
Partials 64 64 ☔ View full report in Codecov by Sentry. |
renovate
bot
force-pushed
the
renovate/favware-cliff-jumper-4.x
branch
3 times, most recently
from
June 16, 2024 04:22
766b920
to
36c63cc
Compare
renovate
bot
force-pushed
the
renovate/favware-cliff-jumper-4.x
branch
3 times, most recently
from
June 23, 2024 03:18
55f622e
to
5b3fb13
Compare
renovate
bot
force-pushed
the
renovate/favware-cliff-jumper-4.x
branch
2 times, most recently
from
June 30, 2024 04:49
344b362
to
977dbf2
Compare
renovate
bot
force-pushed
the
renovate/favware-cliff-jumper-4.x
branch
2 times, most recently
from
July 7, 2024 06:09
7fce9cd
to
48d4378
Compare
renovate
bot
force-pushed
the
renovate/favware-cliff-jumper-4.x
branch
3 times, most recently
from
July 21, 2024 04:35
0628c02
to
5530550
Compare
renovate
bot
force-pushed
the
renovate/favware-cliff-jumper-4.x
branch
3 times, most recently
from
July 28, 2024 05:16
ba86962
to
b75387c
Compare
renovate
bot
force-pushed
the
renovate/favware-cliff-jumper-4.x
branch
5 times, most recently
from
August 4, 2024 07:14
92b1ab3
to
c9a40d6
Compare
renovate
bot
force-pushed
the
renovate/favware-cliff-jumper-4.x
branch
3 times, most recently
from
August 11, 2024 07:10
86ba732
to
39d2a33
Compare
renovate
bot
force-pushed
the
renovate/favware-cliff-jumper-4.x
branch
3 times, most recently
from
August 18, 2024 12:04
3c2e47d
to
d416d44
Compare
renovate
bot
force-pushed
the
renovate/favware-cliff-jumper-4.x
branch
4 times, most recently
from
August 25, 2024 11:16
73e6a65
to
e10ac50
Compare
renovate
bot
force-pushed
the
renovate/favware-cliff-jumper-4.x
branch
2 times, most recently
from
September 1, 2024 07:17
092f052
to
30c4c94
Compare
renovate
bot
force-pushed
the
renovate/favware-cliff-jumper-4.x
branch
3 times, most recently
from
September 15, 2024 03:48
659ed25
to
b4685e1
Compare
renovate
bot
force-pushed
the
renovate/favware-cliff-jumper-4.x
branch
3 times, most recently
from
September 22, 2024 03:53
4e24be3
to
8ef91ba
Compare
renovate
bot
force-pushed
the
renovate/favware-cliff-jumper-4.x
branch
3 times, most recently
from
September 29, 2024 07:29
aada04a
to
b3b1079
Compare
renovate
bot
force-pushed
the
renovate/favware-cliff-jumper-4.x
branch
2 times, most recently
from
October 6, 2024 07:02
46fce18
to
be5402b
Compare
renovate
bot
force-pushed
the
renovate/favware-cliff-jumper-4.x
branch
from
October 13, 2024 04:08
be5402b
to
c51935a
Compare
renovate
bot
force-pushed
the
renovate/favware-cliff-jumper-4.x
branch
from
October 13, 2024 06:58
c51935a
to
8c4f41b
Compare
renovate
bot
changed the title
chore(deps): update dependency @favware/cliff-jumper to v4
chore(deps): update dependency @favware/cliff-jumper to v4 - autoclosed
Oct 19, 2024
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:
^3.0.3
->^4.1.0
Release Notes
favware/cliff-jumper (@favware/cliff-jumper)
v4.1.0
Compare Source
🐛 Bug Fixes
🚀 Features
v4.0.3
Compare Source
🐛 Bug Fixes
--mode=update-lockfile
for yarn v2/v3/v4 (ef02496)v4.0.2
Compare Source
🐛 Bug Fixes
v4.0.1
Compare Source
🏠 Refactor
conventional-changelog-angular
and inlinewhatBump
code (684b29f)🐛 Bug Fixes
📝 Documentation
v4.0.0
Compare Source
🏠 Refactor
first-release
toskip-automatic-bump
(fe244a0)first-release
has been renamed toskip-automatic-bump
in order to better describe what it does
CI
env detection (775f02e)CI
env--skip-changelog
and--skip-tag
wereautomatically enabled. This is no longer the case, because the new GitHub releasing feature
makes it more appealing to run this tool in CI. To restore the old functionality for your
pipelines please explicitly add these tags to your command line.
conventional-recommended-bump
conventional-changelog-angular
is now used instead of a customization of it. This should not affect the semver resolution, but if it does please create a GitHub issue🐛 Bug Fixes
📝 Documentation
🚀 Features
--no-push-tag
to override config file for prereleases (6f5d748)--no-github-release
to override config file for prereleases (656c8ec)--changelog-prepend-file
to customize to which file the changelog is prepended (35e9731)--push-tag
and--github-release
to automatically push a Git tag and create a release on GitHub (b66bfa1)Configuration
📅 Schedule: Branch creation - "before 12pm on Sunday" (UTC), 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 was generated by Mend Renovate. View the repository job log.