This fixes a regression with a change in the previous release that tries to more accurately parse TypeScript arrow functions inside the ?: operator. The regression specifically involves parsing an arrow function containing a #private identifier inside the middle of a ?: ternary operator inside a class body. This was fixed by propagating private identifier state into the parser clone used to speculatively parse the arrow function body. Here is an example of some affected code:
Fix a regression with the parsing of source phase imports
The change in the previous release to parse source phase imports failed to properly handle the following cases:
import source from 'bar'
import source from from 'bar'
import source type foo from 'bar'
Parsing for these cases should now be fixed. The first case was incorrectly treated as a syntax error because esbuild was expecting the second case. And the last case was previously allowed but is now forbidden. TypeScript hasn't added this feature yet so it remains to be seen whether the last case will be allowed, but it's safer to disallow it for now. At least Babel doesn't allow the last case when parsing TypeScript, and Babel was involved with the source phase import specification.
v0.25.7
Parse and print JavaScript imports with an explicit phase (#4238)
This release adds basic syntax support for the defer and source import phases in JavaScript:
defer
This is a stage 3 proposal for an upcoming JavaScript feature that will provide one way to eagerly load but lazily initialize imported modules. The imported module is automatically initialized on first use. Support for this syntax will also be part of the upcoming release of TypeScript 5.9. The syntax looks like this:
import defer * as foo from "<specifier>";
const bar = await import.defer("<specifier>");
Note that this feature deliberately cannot be used with the syntax import defer foo from "<specifier>" or import defer { foo } from "<specifier>".
source
This is a stage 3 proposal for an upcoming JavaScript feature that will provide another way to eagerly load but lazily initialize imported modules. The imported module is returned in an uninitialized state. Support for this syntax may or may not be a part of TypeScript 5.9 (see this issue for details). The syntax looks like this:
import source foo from "<specifier>";
const bar = await import.source("<specifier>");
This fixes a regression with a change in the previous release that tries to more accurately parse TypeScript arrow functions inside the ?: operator. The regression specifically involves parsing an arrow function containing a #private identifier inside the middle of a ?: ternary operator inside a class body. This was fixed by propagating private identifier state into the parser clone used to speculatively parse the arrow function body. Here is an example of some affected code:
Fix a regression with the parsing of source phase imports
The change in the previous release to parse source phase imports failed to properly handle the following cases:
import source from 'bar'
import source from from 'bar'
import source type foo from 'bar'
Parsing for these cases should now be fixed. The first case was incorrectly treated as a syntax error because esbuild was expecting the second case. And the last case was previously allowed but is now forbidden. TypeScript hasn't added this feature yet so it remains to be seen whether the last case will be allowed, but it's safer to disallow it for now. At least Babel doesn't allow the last case when parsing TypeScript, and Babel was involved with the source phase import specification.
0.25.7
Parse and print JavaScript imports with an explicit phase (#4238)
This release adds basic syntax support for the defer and source import phases in JavaScript:
defer
This is a stage 3 proposal for an upcoming JavaScript feature that will provide one way to eagerly load but lazily initialize imported modules. The imported module is automatically initialized on first use. Support for this syntax will also be part of the upcoming release of TypeScript 5.9. The syntax looks like this:
import defer * as foo from "<specifier>";
const bar = await import.defer("<specifier>");
Note that this feature deliberately cannot be used with the syntax import defer foo from "<specifier>" or import defer { foo } from "<specifier>".
source
This is a stage 3 proposal for an upcoming JavaScript feature that will provide another way to eagerly load but lazily initialize imported modules. The imported module is returned in an uninitialized state. Support for this syntax may or may not be a part of TypeScript 5.9 (see this issue for details). The syntax looks like this:
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
@dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
@dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
@dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
@dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
@dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/fosrl/pangolin/pull/1261
**Author:** [@dependabot[bot]](https://github.com/apps/dependabot)
**Created:** 8/12/2025
**Status:** ❌ Closed
**Base:** `main` ← **Head:** `dependabot/npm_and_yarn/dev-patch-updates-0e14fa6bb5`
---
### 📝 Commits (1)
- [`e4b1efe`](https://github.com/fosrl/pangolin/commit/e4b1efee2d66fbee354d91f7034a04cf9b828314) Bump the dev-patch-updates group across 1 directory with 5 updates
### 📊 Changes
**2 files changed** (+185 additions, -185 deletions)
<details>
<summary>View changed files</summary>
📝 `package-lock.json` (+181 -181)
📝 `package.json` (+4 -4)
</details>
### 📄 Description
Bumps the dev-patch-updates group with 5 updates in the / directory:
| Package | From | To |
| --- | --- | --- |
| [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) | `24.2.0` | `24.2.1` |
| [@types/pg](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/pg) | `8.15.4` | `8.15.5` |
| [@types/react](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/react) | `19.1.9` | `19.1.10` |
| [esbuild](https://github.com/evanw/esbuild) | `0.25.6` | `0.25.8` |
| [typescript-eslint](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/typescript-eslint) | `8.39.0` | `8.39.1` |
Updates `@types/node` from 24.2.0 to 24.2.1
<details>
<summary>Commits</summary>
<ul>
<li>See full diff in <a href="https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node">compare view</a></li>
</ul>
</details>
<br />
Updates `@types/pg` from 8.15.4 to 8.15.5
<details>
<summary>Commits</summary>
<ul>
<li>See full diff in <a href="https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/pg">compare view</a></li>
</ul>
</details>
<br />
Updates `@types/react` from 19.1.9 to 19.1.10
<details>
<summary>Commits</summary>
<ul>
<li>See full diff in <a href="https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/react">compare view</a></li>
</ul>
</details>
<br />
Updates `esbuild` from 0.25.6 to 0.25.8
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/evanw/esbuild/releases">esbuild's releases</a>.</em></p>
<blockquote>
<h2>v0.25.8</h2>
<ul>
<li>
<p>Fix another TypeScript parsing edge case (<a href="https://redirect.github.com/evanw/esbuild/issues/4248">#4248</a>)</p>
<p>This fixes a regression with a change in the previous release that tries to more accurately parse TypeScript arrow functions inside the <code>?:</code> operator. The regression specifically involves parsing an arrow function containing a <code>#private</code> identifier inside the middle of a <code>?:</code> ternary operator inside a class body. This was fixed by propagating private identifier state into the parser clone used to speculatively parse the arrow function body. Here is an example of some affected code:</p>
<pre lang="ts"><code>class CachedDict {
#has = (a: string) => dict.has(a);
has = window
? (word: string): boolean => this.#has(word)
: this.#has;
}
</code></pre>
</li>
<li>
<p>Fix a regression with the parsing of source phase imports</p>
<p>The change in the previous release to parse <a href="https://github.com/tc39/proposal-source-phase-imports">source phase imports</a> failed to properly handle the following cases:</p>
<pre lang="ts"><code>import source from 'bar'
import source from from 'bar'
import source type foo from 'bar'
</code></pre>
<p>Parsing for these cases should now be fixed. The first case was incorrectly treated as a syntax error because esbuild was expecting the second case. And the last case was previously allowed but is now forbidden. TypeScript hasn't added this feature yet so it remains to be seen whether the last case will be allowed, but it's safer to disallow it for now. At least Babel doesn't allow the last case when parsing TypeScript, and Babel was involved with the source phase import specification.</p>
</li>
</ul>
<h2>v0.25.7</h2>
<ul>
<li>
<p>Parse and print JavaScript imports with an explicit phase (<a href="https://redirect.github.com/evanw/esbuild/issues/4238">#4238</a>)</p>
<p>This release adds basic syntax support for the <code>defer</code> and <code>source</code> import phases in JavaScript:</p>
<ul>
<li>
<p><code>defer</code></p>
<p>This is a <a href="https://github.com/tc39/proposal-defer-import-eval">stage 3 proposal</a> for an upcoming JavaScript feature that will provide one way to eagerly load but lazily initialize imported modules. The imported module is automatically initialized on first use. Support for this syntax will also be part of the upcoming release of <a href="https://devblogs.microsoft.com/typescript/announcing-typescript-5-9-beta/#support-for-import-defer">TypeScript 5.9</a>. The syntax looks like this:</p>
<pre lang="js"><code>import defer * as foo from "<specifier>";
const bar = await import.defer("<specifier>");
</code></pre>
<p>Note that this feature deliberately cannot be used with the syntax <code>import defer foo from "<specifier>"</code> or <code>import defer { foo } from "<specifier>"</code>.</p>
</li>
<li>
<p><code>source</code></p>
<p>This is a <a href="https://github.com/tc39/proposal-source-phase-imports">stage 3 proposal</a> for an upcoming JavaScript feature that will provide another way to eagerly load but lazily initialize imported modules. The imported module is returned in an uninitialized state. Support for this syntax may or may not be a part of TypeScript 5.9 (see <a href="https://redirect.github.com/microsoft/TypeScript/issues/61216">this issue</a> for details). The syntax looks like this:</p>
<pre lang="js"><code>import source foo from "<specifier>";
const bar = await import.source("<specifier>");
</code></pre>
</li>
</ul>
</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/evanw/esbuild/blob/main/CHANGELOG.md">esbuild's changelog</a>.</em></p>
<blockquote>
<h2>0.25.8</h2>
<ul>
<li>
<p>Fix another TypeScript parsing edge case (<a href="https://redirect.github.com/evanw/esbuild/issues/4248">#4248</a>)</p>
<p>This fixes a regression with a change in the previous release that tries to more accurately parse TypeScript arrow functions inside the <code>?:</code> operator. The regression specifically involves parsing an arrow function containing a <code>#private</code> identifier inside the middle of a <code>?:</code> ternary operator inside a class body. This was fixed by propagating private identifier state into the parser clone used to speculatively parse the arrow function body. Here is an example of some affected code:</p>
<pre lang="ts"><code>class CachedDict {
#has = (a: string) => dict.has(a);
has = window
? (word: string): boolean => this.#has(word)
: this.#has;
}
</code></pre>
</li>
<li>
<p>Fix a regression with the parsing of source phase imports</p>
<p>The change in the previous release to parse <a href="https://github.com/tc39/proposal-source-phase-imports">source phase imports</a> failed to properly handle the following cases:</p>
<pre lang="ts"><code>import source from 'bar'
import source from from 'bar'
import source type foo from 'bar'
</code></pre>
<p>Parsing for these cases should now be fixed. The first case was incorrectly treated as a syntax error because esbuild was expecting the second case. And the last case was previously allowed but is now forbidden. TypeScript hasn't added this feature yet so it remains to be seen whether the last case will be allowed, but it's safer to disallow it for now. At least Babel doesn't allow the last case when parsing TypeScript, and Babel was involved with the source phase import specification.</p>
</li>
</ul>
<h2>0.25.7</h2>
<ul>
<li>
<p>Parse and print JavaScript imports with an explicit phase (<a href="https://redirect.github.com/evanw/esbuild/issues/4238">#4238</a>)</p>
<p>This release adds basic syntax support for the <code>defer</code> and <code>source</code> import phases in JavaScript:</p>
<ul>
<li>
<p><code>defer</code></p>
<p>This is a <a href="https://github.com/tc39/proposal-defer-import-eval">stage 3 proposal</a> for an upcoming JavaScript feature that will provide one way to eagerly load but lazily initialize imported modules. The imported module is automatically initialized on first use. Support for this syntax will also be part of the upcoming release of <a href="https://devblogs.microsoft.com/typescript/announcing-typescript-5-9-beta/#support-for-import-defer">TypeScript 5.9</a>. The syntax looks like this:</p>
<pre lang="js"><code>import defer * as foo from "<specifier>";
const bar = await import.defer("<specifier>");
</code></pre>
<p>Note that this feature deliberately cannot be used with the syntax <code>import defer foo from "<specifier>"</code> or <code>import defer { foo } from "<specifier>"</code>.</p>
</li>
<li>
<p><code>source</code></p>
<p>This is a <a href="https://github.com/tc39/proposal-source-phase-imports">stage 3 proposal</a> for an upcoming JavaScript feature that will provide another way to eagerly load but lazily initialize imported modules. The imported module is returned in an uninitialized state. Support for this syntax may or may not be a part of TypeScript 5.9 (see <a href="https://redirect.github.com/microsoft/TypeScript/issues/61216">this issue</a> for details). The syntax looks like this:</p>
<pre lang="js"><code>import source foo from "<specifier>";
</code></pre>
</li>
</ul>
</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/evanw/esbuild/commit/8c71947edbe5a158fec3a6d1cbfea1e8d5cdee70"><code>8c71947</code></a> publish 0.25.8 to npm</li>
<li><a href="https://github.com/evanw/esbuild/commit/0508f2444569ba105fa38e6e9fa9e1f2ed6d95b2"><code>0508f24</code></a> some parsing fixes for source phase imports</li>
<li><a href="https://github.com/evanw/esbuild/commit/6e4be2fad3c898ea2f4d9c2fd0be7bbcd79f5206"><code>6e4be2f</code></a> js parser: recover from bad <code>#private</code> identifiers</li>
<li><a href="https://github.com/evanw/esbuild/commit/c9c6357a8dbf43b9ec2896bd92e25df2f0677b45"><code>c9c6357</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/4248">#4248</a>: <code>#private</code> ids in arrow fn body in <code>?:</code></li>
<li><a href="https://github.com/evanw/esbuild/commit/9b42f68f9b1fecf16e72dbcfc5c46504239d6fe6"><code>9b42f68</code></a> publish 0.25.7 to npm</li>
<li><a href="https://github.com/evanw/esbuild/commit/9ba01d1c1faf6f157d614c64144193dbfe88db97"><code>9ba01d1</code></a> abs-paths: js api and tests</li>
<li><a href="https://github.com/evanw/esbuild/commit/ca196c9c4a270ff61181bc8d61886b947bbc2612"><code>ca196c9</code></a> fix for parser backtracking crash</li>
<li><a href="https://github.com/evanw/esbuild/commit/2979b846fd7e5899a57f412bb3ce8ee0c8c150f3"><code>2979b84</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/4241">#4241</a>: ts arrow function type backtrack (hack)</li>
<li><a href="https://github.com/evanw/esbuild/commit/1180410e335f49eb8a4b33be4357bf15b185475e"><code>1180410</code></a> fix an unused variable warning</li>
<li><a href="https://github.com/evanw/esbuild/commit/fc3da579557d775c022dbfc4e68843d34cab9fb5"><code>fc3da57</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/4238">#4238</a>: add <code>defer</code> and <code>source</code> import phases</li>
<li>Additional commits viewable in <a href="https://github.com/evanw/esbuild/compare/v0.25.6...v0.25.8">compare view</a></li>
</ul>
</details>
<br />
Updates `typescript-eslint` from 8.39.0 to 8.39.1
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/typescript-eslint/typescript-eslint/releases">typescript-eslint's releases</a>.</em></p>
<blockquote>
<h2>v8.39.1</h2>
<h2>8.39.1 (2025-08-11)</h2>
<h3>🩹 Fixes</h3>
<ul>
<li><strong>typescript-eslint:</strong> handle <code>file://</code> urls in stack trace when inferring <code>tsconfigRootDir</code> (<a href="https://redirect.github.com/typescript-eslint/typescript-eslint/pull/11464">#11464</a>)</li>
</ul>
<h3>❤️ Thank You</h3>
<ul>
<li>Kirk Waiblinger <a href="https://github.com/kirkwaiblinger"><code>@kirkwaiblinger</code></a></li>
</ul>
<p>You can read about our <a href="https://main--typescript-eslint.netlify.app/users/versioning">versioning strategy</a> and <a href="https://main--typescript-eslint.netlify.app/users/releases">releases</a> on our website.</p>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/typescript-eslint/CHANGELOG.md">typescript-eslint's changelog</a>.</em></p>
<blockquote>
<h2>8.39.1 (2025-08-11)</h2>
<h3>🩹 Fixes</h3>
<ul>
<li><strong>typescript-eslint:</strong> handle <code>file://</code> urls in stack trace when inferring <code>tsconfigRootDir</code> (<a href="https://redirect.github.com/typescript-eslint/typescript-eslint/pull/11464">#11464</a>)</li>
</ul>
<h3>❤️ Thank You</h3>
<ul>
<li>Kirk Waiblinger <a href="https://github.com/kirkwaiblinger"><code>@kirkwaiblinger</code></a></li>
</ul>
<p>You can read about our <a href="https://main--typescript-eslint.netlify.app/users/versioning">versioning strategy</a> and <a href="https://main--typescript-eslint.netlify.app/users/releases">releases</a> on our website.</p>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/typescript-eslint/typescript-eslint/commit/b2ee794265c4c727009e65a4eb5f06fad9686cf8"><code>b2ee794</code></a> chore(release): publish 8.39.1</li>
<li><a href="https://github.com/typescript-eslint/typescript-eslint/commit/7319bad3a5022be2adfbcb331451cfd85d1d786a"><code>7319bad</code></a> fix(typescript-eslint): handle <code>file://</code> urls in stack trace when inferring `...</li>
<li>See full diff in <a href="https://github.com/typescript-eslint/typescript-eslint/commits/v8.39.1/packages/typescript-eslint">compare view</a></li>
</ul>
</details>
<br />
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore <dependency name> major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
- `@dependabot ignore <dependency name> minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
- `@dependabot ignore <dependency name>` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
- `@dependabot unignore <dependency name>` will remove all of the ignore conditions of the specified dependency
- `@dependabot unignore <dependency name> <ignore condition>` will remove the ignore condition of the specified dependency and ignore conditions
</details>
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/fosrl/pangolin/pull/1261
Author: @dependabot[bot]
Created: 8/12/2025
Status: ❌ Closed
Base:
main← Head:dependabot/npm_and_yarn/dev-patch-updates-0e14fa6bb5📝 Commits (1)
e4b1efeBump the dev-patch-updates group across 1 directory with 5 updates📊 Changes
2 files changed (+185 additions, -185 deletions)
View changed files
📝
package-lock.json(+181 -181)📝
package.json(+4 -4)📄 Description
Bumps the dev-patch-updates group with 5 updates in the / directory:
24.2.024.2.18.15.48.15.519.1.919.1.100.25.60.25.88.39.08.39.1Updates
@types/nodefrom 24.2.0 to 24.2.1Commits
Updates
@types/pgfrom 8.15.4 to 8.15.5Commits
Updates
@types/reactfrom 19.1.9 to 19.1.10Commits
Updates
esbuildfrom 0.25.6 to 0.25.8Release notes
Sourced from esbuild's releases.
... (truncated)
Changelog
Sourced from esbuild's changelog.
... (truncated)
Commits
8c71947publish 0.25.8 to npm0508f24some parsing fixes for source phase imports6e4be2fjs parser: recover from bad#privateidentifiersc9c6357fix #4248:#privateids in arrow fn body in?:9b42f68publish 0.25.7 to npm9ba01d1abs-paths: js api and testsca196c9fix for parser backtracking crash2979b84fix #4241: ts arrow function type backtrack (hack)1180410fix an unused variable warningfc3da57fix #4238: adddeferandsourceimport phasesUpdates
typescript-eslintfrom 8.39.0 to 8.39.1Release notes
Sourced from typescript-eslint's releases.
Changelog
Sourced from typescript-eslint's changelog.
Commits
b2ee794chore(release): publish 8.39.17319badfix(typescript-eslint): handlefile://urls in stack trace when inferring `...Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.