Update dev dependencies #77
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]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #77 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 3 3
Lines 1438 1438
Branches 85 85
=========================================
Hits 1438 1438 ☔ View full report in Codecov by Sentry. |
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:
^20.11.0->^20.12.2^6.18.1->^7.5.0^6.18.1->^7.5.0^0.19.11->^0.20.2^8.56.0->^8.57.0^3.0.2->^3.1.0^21.0.1->^22.0.0^0.25.7->^0.25.12Release Notes
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v7.5.0Compare Source
🩹 Fixes
eslint-plugin: [no-floating-promises] handle TaggedTemplateExpression
eslint-plugin: [no-unnecessary-type-assertion] handle exactOptionalPropertyTypes compiler option
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v7.4.0Compare Source
🚀 Features
eslint-plugin: [consistent-type-imports] ignore files with decorators, experimentalDecorators, and emitDecoratorMetadata
eslint-plugin: [no-unnecessary-type-arguments] handle tagged templates
eslint-plugin: deprecate no-throw-literal and add a renamed only-throw-error
🩹 Fixes
eslint-plugin: [prefer-optional-chain] address multipart nullish checks false positive
eslint-plugin: [prefer-optional-chain] properly disambiguate between
booleanandfalseeslint-plugin: [no-unnecessary-type-assertion] avoid remove const casting on template literals with expressions inside
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v7.3.1Compare Source
🩹 Fixes
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v7.3.0Compare Source
🚀 Features
eslint-plugin: [restrict-template-expressions] add
allowArrayoptioneslint-plugin: add meta.docs.recommended setting for strict config options
eslint-plugin: add rule
use-unknown-in-catch-callback-variableseslint-plugin: [prefer-reduce-type-parameter] supports tuple, union, intersection
🩹 Fixes
correct
engines.nodeconstraints inpackage.jsoneslint-plugin: [unbound-method] check method definition in object literal using longhand form
eslint-plugin: [consistent-type-imports] handle imports without specifiers
eslint-plugin: [no-redundant-type-constituents] incorrectly marks & string as redundant
eslint-plugin: [no-unnecessary-qualifier] handle merge namespace with enum
eslint-plugin: [no-unused-expressions] false negatives when using assertions
eslint-plugin: [ban-ts-comment] more accurate handling of multiline comments
eslint-plugin: [explicit-function-return-type, explicit-module-boundary-types] improved checking for allowHigherOrderFunctions option
eslint-plugin: [class-literal-property-style] ignore property assigned in constructor
eslint-plugin: [no-unnecessary-type-assertion] fix false negative for const variable declarations
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v7.2.0Compare Source
🚀 Features
support TS 5.4
eslint-plugin: [prefer-string-starts-ends-with] add allowSingleElementEquality option
🩹 Fixes
eslint-plugin: expose *-type-checked-only configs for extension
eslint-plugin: [member-ordering] report alphabetical sorting for all groups instead of just the first failing group
eslint-plugin: [no-var-requires, no-require-imports] support template literal
eslint-plugin: [no-useless-template-literals] detect TemplateLiteral
eslint-plugin: [no-unnecessary-condition] handle union array and tuple type
eslint-plugin: [prefer-find] support ternary branches in prefer-find
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v7.1.1Compare Source
This was a version bump only for eslint-plugin to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v7.1.0Compare Source
🚀 Features
eslint-plugin: add *-type-checked-only configs
eslint-plugin: [naming-convention] support the auto-accessor syntax
eslint-plugin: [consistent-return] add new rule
🩹 Fixes
eslint-plugin: [prefer-optional-chan] allow typeof for avoiding reference error
eslint-plugin: [no-misused-promises] improve check union types
eslint-plugin: [no-use-before-define] fix false positive type reference in as, satisfies
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v7.0.2Compare Source
🩹 Fixes
@types/eslintincompatibilities, add tests❤️ Thank You
You can read about our versioning strategy and releases on our website.
v7.0.1Compare Source
🩹 Fixes
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v7.0.0Compare Source
🚀 Features
add support for flat configs
🩹 Fixes
❤️ Thank You
You can read about our versioning strategy and releases on our website.
6.21.0 (2024-02-05)
🚀 Features
export plugin metadata
allow
parserOptions.project: falseeslint-plugin: add rule prefer-find
🩹 Fixes
eslint-plugin: [no-unused-vars] don't report on types referenced in export assignment expression
eslint-plugin: [switch-exhaustiveness-check] better support for intersections, infinite types, non-union values
eslint-plugin: [consistent-type-imports] dont report on types used in export assignment expressions
eslint-plugin: [no-unnecessary-condition] handle left-hand optional with exactOptionalPropertyTypes option
eslint-plugin: [class-literal-property-style] allow getter when same key setter exists
eslint-plugin: [no-unnecessary-type-assertion] provide valid fixes for assertions with extra tokens before
askeyword❤️ Thank You
You can read about our versioning strategy and releases on our website.
6.20.0 (2024-01-29)
🚀 Features
🩹 Fixes
eslint-plugin: [no-useless-template-literals] incorrect bigint autofix result
eslint-plugin: [prefer-nullish-coalescing] treat any/unknown as non-nullable
eslint-plugin: [no-useless-template-literals] report Infinity & NaN
eslint-plugin: [prefer-readonly] disable checking accessors
❤️ Thank You
You can read about our versioning strategy and releases on our website.
6.19.1 (2024-01-22)
🩹 Fixes
type-utils: preventing isUnsafeAssignment infinite recursive calls
eslint-plugin: [no-unnecessary-condition] fix false positive for type variable
❤️ Thank You
You can read about our versioning strategy and releases on our website.
6.19.0 (2024-01-15)
🚀 Features
eslint-plugin: [prefer-promise-reject-errors] add rule
eslint-plugin: [no-array-delete] add new rule
eslint-plugin: [no-useless-template-literals] add fix suggestions
🩹 Fixes
eslint-plugin: [no-unnecessary-type-assertion] detect unnecessary non-null-assertion on a call expression
eslint-plugin: [no-unnecesary-type-assertion] treat unknown/any as nullable
❤️ Thank You
You can read about our versioning strategy and releases on our website.
6.18.1 (2024-01-08)
🩹 Fixes
eslint-plugin: [no-non-null-assertion] provide valid fix when member access is on next line
eslint-plugin: [no-unnecessary-condition] improve checking optional callee
eslint-plugin: [prefer-readonly] support modifiers of unions and intersections
eslint-plugin: [switch-exhaustiveness-check] fix new allowDefaultCaseForExhaustiveSwitch option
❤️ Thank You
You can read about our versioning strategy and releases on our website.
6.18.0 (2024-01-06)
🚀 Features
typescript-estree: throw on invalid update expressions
eslint-plugin: [no-var-requires, no-require-imports] allow option
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v6.21.0Compare Source
🚀 Features
export plugin metadata
allow
parserOptions.project: falseeslint-plugin: add rule prefer-find
🩹 Fixes
eslint-plugin: [no-unused-vars] don't report on types referenced in export assignment expression
eslint-plugin: [switch-exhaustiveness-check] better support for intersections, infinite types, non-union values
eslint-plugin: [consistent-type-imports] dont report on types used in export assignment expressions
eslint-plugin: [no-unnecessary-condition] handle left-hand optional with exactOptionalPropertyTypes option
eslint-plugin: [class-literal-property-style] allow getter when same key setter exists
eslint-plugin: [no-unnecessary-type-assertion] provide valid fixes for assertions with extra tokens before
askeyword❤️ Thank You
You can read about our versioning strategy and releases on our website.
v6.20.0Compare Source
🚀 Features
🩹 Fixes
eslint-plugin: [no-useless-template-literals] incorrect bigint autofix result
eslint-plugin: [prefer-nullish-coalescing] treat any/unknown as non-nullable
eslint-plugin: [no-useless-template-literals] report Infinity & NaN
eslint-plugin: [prefer-readonly] disable checking accessors
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v6.19.1Compare Source
🩹 Fixes
type-utils: preventing isUnsafeAssignment infinite recursive calls
eslint-plugin: [no-unnecessary-condition] fix false positive for type variable
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v6.19.0Compare Source
🚀 Features
eslint-plugin: [prefer-promise-reject-errors] add rule
eslint-plugin: [no-array-delete] add new rule
eslint-plugin: [no-useless-template-literals] add fix suggestions
🩹 Fixes
eslint-plugin: [no-unnecessary-type-assertion] detect unnecessary non-null-assertion on a call expression
eslint-plugin: [no-unnecesary-type-assertion] treat unknown/any as nullable
❤️ Thank You
You can read about our versioning strategy and releases on our website.
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
v7.5.0Compare Source
🩹 Fixes
errorOnTypeScriptSyntacticAndSemanticIssues❤️ Thank You
You can read about our versioning strategy and releases on our website.
v7.4.0Compare Source
v7.3.1Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v7.3.0Compare Source
🩹 Fixes
engines.nodeconstraints inpackage.json❤️ Thank You
You can read about our versioning strategy and releases on our website.
v7.2.0Compare Source
🚀 Features
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v7.1.1Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v7.1.0Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v7.0.2Compare Source
🩹 Fixes
@types/eslintincompatibilities, add tests❤️ Thank You
You can read about our versioning strategy and releases on our website.
v7.0.1Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v7.0.0Compare Source
🚀 Features
add support for flat configs
❤️ Thank You
You can read about our versioning strategy and releases on our website.
6.21.0 (2024-02-05)
🚀 Features
parserOptions.project: false❤️ Thank You
You can read about our versioning strategy and releases on our website.
6.20.0 (2024-01-29)
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
6.19.1 (2024-01-22)
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
6.19.0 (2024-01-15)
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
6.18.1 (2024-01-08)
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
6.18.0 (2024-01-06)
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v6.21.0Compare Source
🚀 Features
parserOptions.project: false❤️ Thank You
You can read about our versioning strategy and releases on our website.
v6.20.0Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v6.19.1Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v6.19.0Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
evanw/esbuild (esbuild)
v0.20.2Compare Source
Support TypeScript experimental decorators on
abstractclass fields (#3684)With this release, you can now use TypeScript experimental decorators on
abstractclass fields. This was silently compiled incorrectly in esbuild 0.19.7 and below, and was an error from esbuild 0.19.8 to esbuild 0.20.1. Code such as the following should now work correctly:JSON loader now preserves
__proto__properties (#3700)Copying JSON source code into a JavaScript file will change its meaning if a JSON object contains the
__proto__key. A literal__proto__property in a JavaScript object literal sets the prototype of the object instead of adding a property named__proto__, while a literal__proto__property in a JSON object literal just adds a property named__proto__. With this release, esbuild will now work around this problem by converting JSON to JavaScript with a computed property key in this case:Improve dead code removal of
switchstatements (#3659)With this release, esbuild will now remove
switchstatements in branches when minifying if they are known to never be evaluated:Empty enums should behave like an object literal (#3657)
TypeScript allows you to create an empty enum and add properties to it at run time. While people usually use an empty object literal for this instead of a TypeScript enum, esbuild's enum transform didn't anticipate this use case and generated
undefinedinstead of{}for an empty enum. With this release, you can now use an empty enum to generate an empty object literal.Handle Yarn Plug'n'Play edge case with
tsconfig.json(#3698)Previously a
tsconfig.jsonfile thatextendsanother file in a package with anexportsmap failed to work when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release.Work around issues with Deno 1.31+ (#3682)
Version 0.20.0 of esbuild changed how the esbuild child process is run in esbuild's API for Deno. Previously it used
Deno.runbut that API is being removed in favor ofDeno.Command. As part of this change, esbuild is now calling the newunreffunction on esbuild's long-lived child process, which is supposed to allow Deno to exit when your code has finished running even though the child process is still around (previously you had to explicitly call esbuild'sstop()function to terminate the child process for Deno to be able to exit).However, this introduced a problem for Deno's testing API which now fails some tests that use esbuild with
error: Promise resolution is still pending but the event loop has already resolved. It's unclear to me why this is happening. The call tounrefwas recommended by someone on the Deno core team, and calling Node's equivalentunrefAPI has been working fine for esbuild in Node for a long time. It could be that I'm using it incorrectly, or that there's some reference counting and/or garbage collection bug in Deno's internals, or that Deno'sunrefjust works differently than Node'sunref. In any case, it's not good for Deno tests that use esbuild to be failing.In this release, I am removing the call to
unrefto fix this issue. This means that you will now have to call esbuild'sstop()function to allow Deno to exit, just like you did before esbuild version 0.20.0 when this regression was introduced.Note: This regression wasn't caught earlier because Deno doesn't seem to fail tests that have outstanding
setTimeoutcalls, which esbuild's test harness was using to enforce a maximum test runtime. Adding asetTimeoutwas allowing esbuild's Deno tests to succeed. So this regression doesn't necessarily apply to all people using tests in Deno.v0.20.1Compare Source
Fix a bug with the CSS nesting transform (#3648)
This release fixes a bug with the CSS nesting transform for older browsers where the generated CSS could be incorrect if a selector list contained a pseudo element followed by another selector. The bug was caused by incorrectly mutating the parent rule's selector list when filtering out pseudo elements for the child rules:
Constant folding for JavaScript inequality operators (#3645)
This release introduces constant folding for the
< > <= >=operators. The minifier will now replace these operators withtrueorfalsewhen both sides are compile-time numeric or string constants:Better handling of
__proto__edge cases (#3651)JavaScript object literal syntax contains a special case where a non-computed property with a key of
__proto__sets the prototype of the object. This does not apply to computed properties or to properties that use the shorthand property syntax introduced in ES6. Previously esbuild didn't correctly preserve the "sets the prototype" status of properties inside an object literal, meaning a property that sets the prototype could accidentally be transformed into one that doesn't and vice versa. This has now been fixed:Fix cross-platform non-determinism with CSS color space transformations (#3650)
The Go compiler takes advantage of "fused multiply and add" (FMA) instructions on certain processors which do the operation
x*y + zwithout intermediate rounding. This causes esbuild's CSS color space math to differ on different processors (currentlyppc64leands390x), which breaks esbuild's guarantee of deterministic output. To avoid this, esbuild's color space math now inserts afloat64()cast around every single math operation. This tells the Go compiler not to use the FMA optimization.Fix a crash when resolving a path from a directory that doesn't exist (#3634)
This release fixes a regression where esbuild could crash when resolving an absolute path if the source directory for the path resolution operation doesn't exist. While this situation doesn't normally come up, it could come up when running esbuild concurrently with another operation that mutates the file system as esbuild is doing a build (such as using
gitto switch branches). The underlying problem was a regression that was introduced in version 0.18.0.v0.20.0Compare Source
This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of
esbuildin yourpackage.jsonfile (recommended) or be using a version range syntax that only accepts patch upgrades such as^0.19.0or~0.19.0. See npm's documentation about semver for more information.This time there is only one breaking change, and it only matters for people using Deno. Deno tests that use esbuild will now fail unless you make the change described below.
Work around API deprecations in Deno 1.40.x (#3609, #3611)
Deno 1.40.0 was just released and introduced run-time warnings about certain APIs that esbuild uses. With this release, esbuild will work around these run-time warnings by using newer APIs if they are present and falling back to the original APIs otherwise. This should avoid the warnings without breaking compatibility with older versions of Deno.
Unfortunately, doing this introduces a breaking change. The newer child process APIs lack a way to synchronously terminate esbuild's child process, so calling
esbuild.stop()from within a Deno test is no longer sufficient to prevent Deno from failing a test that uses esbuild's API (Deno fails tests that create a child process without killing it before the test ends). To work around this, esbuild'sstop()function has been changed to return a promise, and you now have to changeesbuild.stop()toawait esbuild.stop()in all of your Deno tests.Reorder implicit file extensions within
node_modules(#3341, #3608)In version 0.18.0, esbuild changed the behavior of implicit file extensions within
node_modulesdirectories (i.e. in published packages) to prefer.jsover.tseven when the--resolve-extensions=order prefers.tsover.js(which it does by default). However, doing that also accidentally made esbuild prefer.cssover.ts, which caused problems for people that published packages containing both TypeScript and CSS in files with the same name.With this release, esbuild will reorder TypeScript file extensions immediately after the last JavaScript file extensions in the implicit file extension order instead of putting them at the end of the order. Specifically the default implicit file extension order is
.tsx,.ts,.jsx,.js,.css,.jsonwhich used to become.jsx,.js,.css,.json,.tsx,.tsinnode_modulesdirectories. With this release it will now become.jsx,.js,.tsx,.ts,.css,.jsoninstead.Why even rewrite the implicit file extension order at all? One reason is because the
.jsfile is more likely to behave correctly than the.tsfile. The behavior of the.tsfile may depend ontsconfig.jsonand thetsconfig.jsonfile may not even be published, or may useextendsto refer to a basetsconfig.jsonfile that wasn't published. People can get into this situation when they forget to add all.tsfiles to their.npmignorefile before publishing to npm. Picking.jsover.tshelps make it more likely that resulting bundle will behave correctly.v0.19.12Compare Source
The "preserve" JSX mode now preserves JSX text verbatim (#3605)
The JSX specification deliberately doesn't specify how JSX text is supposed to be interpreted and there is no canonical way to interpret JSX text. Two most popular interpretations are Babel and TypeScript. Yes they are different (esbuild deliberately follows TypeScript by the way).
Previously esbuild normalized text to the TypeScript interpretation when the "preserve" JSX mode is active. However, "preserve" should arguably reproduce the original JSX text verbatim so that whatever JSX transform runs after esbuild is free to interpret it however it wants. So with this release, esbuild will now pass JSX text through unmodified:
Allow JSX elements as JSX attribute values
JSX has an obscure feature where you can use JSX elements in attribute position without surrounding them with
{...}. It looks like this:I think I originally didn't implement it even though it's part of the JSX specification because it previously didn't work in TypeScript (and potentially also in Babel?). However, support for it was silently added in TypeScript 4.8 without me noticing and Babel has also since fixed their bugs regarding this feature. So I'm adding it to esbuild too now that I know it's widely supported.
Keep in mind that there is some ongoing discussion about removing this feature from JSX. I agree that the syntax seems out of place (it does away with the elegance of "JSX is basically just XML with
{...}escapes" for something arguably harder to read, which doesn't seem like a good trade-off), but it's in the specification and TypeScript and Babel both implement it so I'm going to have esbuild implement it too. However, I reserve the right to remove it from esbuild if it's ever removed from the specification in the future. So use it with caution.Fix a bug with TypeScript type parsing (#3574)
This release fixes a bug with esbuild's TypeScript parser where a conditional type containing a union type that ends with an infer type that ends with a constraint could fail to parse. This was caused by the "don't parse a conditional type" flag not getting passed through the union type parser. Here's an example of valid TypeScript code that previously failed to parse correctly:
eslint/eslint (eslint)
v8.57.0Compare Source
Features
1120b9bfeat: Add loadESLint() API method for v8 (#18098) (Nicholas C. Zakas)dca7d0ffeat: Enableeslint.config.mjsandeslint.config.cjs(#18066) (Nitin Kumar)Bug Fixes
2196d97fix: handle absolute file paths inFlatRuleTester(#18064) (Nitin Kumar)69dd1d1fix: Ensure config keys are printed for config errors (#18067) (Nitin Kumar)9852a31fix: deep merge behavior in flat config (#18065) (Nitin Kumar)4c7e9b0fix: allow circular references in config (#18056) (Milos Djermanovic)Documentation
84922d0docs: Show prerelease version in dropdown (#18139) (Nicholas C. Zakas)5b8c363docs: Switch to Ethical Ads (#18117) (Milos Djermanovic)77dbfd9docs: show NEXT in version selectors (#18052) (Milos Djermanovic)Chores
1813aecchore: upgrade @eslint/js@8.57.0 (#18143) (Milos Djermanovic)5c356bbchore: package.json update for @eslint/js release (Jenkins)f4a1fe2test: add more tests for ignoring files and directories (#18068) (Nitin Kumar)42c0aefci: Enable CI forv8.xbranch (#18047) (Milos Djermanovic)remy/nodemon (nodemon)
v3.1.0Compare Source
Features
v3.0.3Compare Source
Bug Fixes
dsherret/ts-morph (ts-morph)
v22.0.0Compare Source
What's Changed
Node.prototype.forgetDescendants()no longer returns self by @dsherret in https://github.com/dsherret/ts-morph/pull/1515Type.prototype.isAssignableToby @dsherret in https://github.com/dsherret/ts-morph/pull/1517TypeChecker.prototype.resolveNameby @dsherret in https://github.com/dsherret/ts-morph/pull/1518CodeBlockWriter 13.0.1
People may have been working around these bugs in the past:
.quote()- should include newline on newline (https://github.com/dsherret/code-block-writer/pull/47).quote()- escape characters were not always being escaped (https://github.com/dsherret/code-block-writer/pull/46)New Contributors
Full Changelog: dsherret/ts-morph@21.0.1...22.0.0
TypeStrong/TypeDoc (typedoc)
v0.25.12Compare Source
Bug Fixes
Configuration
📅 Schedule: Branch creation - "every 3 months on the first day of the month" (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 has been generated by Mend Renovate. View repository job log here.