-
Notifications
You must be signed in to change notification settings - Fork 1k
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 dependency listr2 to v6 #8105
Merged
Merged
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
added
the
release:chore
This PR is a chore (means nothing for users)
label
Apr 25, 2023
renovate
bot
force-pushed
the
renovate/listr2-6.x
branch
2 times, most recently
from
April 25, 2023 15:02
1bea251
to
91ef04c
Compare
renovate
bot
force-pushed
the
renovate/listr2-6.x
branch
from
April 25, 2023 15:07
91ef04c
to
447f0fa
Compare
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. |
16 replays were recorded for ea059f6. 16 PassedrequireAuth graphql checks
|
16 replays were recorded for 688f1a0. 1 FailedRBAC: Should not be able to delete contact as non-admin user
15 PassedrequireAuth graphql checks
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
fixture-ok
Override the test project fixture check
release:chore
This PR is a chore (means nothing for users)
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:
5.0.8
->6.3.1
Release Notes
listr2/listr2
v6.3.1
Compare Source
Bug Fixes
v6.3.0
Compare Source
Bug Fixes
Features
v6.2.0
Compare Source
Bug Fixes
Features
v6.1.0
Compare Source
Bug Fixes
Features
v6.0.4
Compare Source
Bug Fixes
v6.0.3
Compare Source
Bug Fixes
v6.0.2
Compare Source
Bug Fixes
v6.0.1
Compare Source
Bug Fixes
v6.0.0
Compare Source
Bug Fixes
Features
Performance Improvements
BREAKING CHANGES
collapse
tocollapseSubtasks
Listr
task list, conditions for fallback and silent renderer have been renamed.rendererSilent
has been renamed tosilentRendererCondition
.rendererFallback
has been renamed tofallbackRendererCondition
.verbose
tosimple
, sincesimple
can mostly handle non-tty at this point.false
fromminimal
, since this is the most hidden feature of them all, and it should be opt-in.wrap
.nonTTYRenderer
,nonTTYRendererOptions
in Listr tasks has been renamed tofallbackRenderer
andfallbackRendererOptions
respectively.To be honest this was staying for the original Listr compatability but since so much is refactored, it made sense to change it to match where the others are used.
Properly uses the ProcessOutputHook for Simpler Renderer. Hooks on prompts.
Moves the ProcessOutputBuffer logic in to its own class, where streams can be recorded.
Deprecated through has been ditched by using a basic WritableStream, idk why i did use it in the first place, I guess it was coming from the original Listr implementation.
Still uses ansi escape parsing to properly render the output, still limited by mostly the log-update but buffering output for bells and clear line or hide cursor charachters breaks stuff too much, so it is the safe way.
Now the renderers for things like timer and timestamps takes in pluggable components through the shared constants, which makes them user configurable.
The logger interface and logger itself has changed to handle all the common cases for any kind of renderer, eventhough it does not use all of them at the same time.
This is a big change that might make the user checkout the new README.
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.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Mend Renovate. View repository job log here.