github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-05-06 12:55:03 -05:00
Code Issues 564 Packages Projects Releases 72 Wiki Activity

[PR #1266] [MERGED] Bump the dev-patch-updates group across 1 directory with 6 updates #9277

New Issue
Closed
opened 2026-04-30 05:32:30 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-30 05:32:30 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/fosrl/pangolin/pull/1266
Author: @dependabot[bot]
Created: 8/13/2025
Status: ✅ Merged
Merged: 8/13/2025
Merged by: @oschwartz10612

Base: main ← Head: dependabot/npm_and_yarn/dev-patch-updates-eb33d068de

📝 Commits (1)

  • a4d460e Bump the dev-patch-updates group across 1 directory with 6 updates

📊 Changes

2 files changed (+190 additions, -190 deletions)

View changed files

📝 package-lock.json (+185 -185)
📝 package.json (+5 -5)

📄 Description

Bumps the dev-patch-updates group with 6 updates in the / directory:

Package From To
@types/node 24.2.0 24.2.1
@types/pg 8.15.4 8.15.5
@types/react 19.1.9 19.1.10
esbuild 0.25.6 0.25.9
tsx 4.20.3 4.20.4
typescript-eslint 8.39.0 8.39.1

Updates @types/node from 24.2.0 to 24.2.1

Commits

Updates @types/pg from 8.15.4 to 8.15.5

Commits

Updates @types/react from 19.1.9 to 19.1.10

Commits

Updates esbuild from 0.25.6 to 0.25.9

Release notes

Sourced from esbuild's releases.

v0.25.9

  • Better support building projects that use Yarn on Windows (#3131, #3663)

    With this release, you can now use esbuild to bundle projects that use Yarn Plug'n'Play on Windows on drives other than the C: drive. The problem was as follows:

    1. Yarn in Plug'n'Play mode on Windows stores its global module cache on the C: drive
    2. Some developers put their projects on the D: drive
    3. Yarn generates relative paths that use ../.. to get from the project directory to the cache directory
    4. Windows-style paths don't support directory traversal between drives via .. (so D:\.. is just D:)
    5. I didn't have access to a Windows machine for testing this edge case

    Yarn works around this edge case by pretending Windows-style paths beginning with C:\ are actually Unix-style paths beginning with /C:/, so the ../.. path segments are able to navigate across drives inside Yarn's implementation. This was broken for a long time in esbuild but I finally got access to a Windows machine and was able to debug and fix this edge case. So you should now be able to bundle these projects with esbuild.

  • Preserve parentheses around function expressions (#4252)

    The V8 JavaScript VM uses parentheses around function expressions as an optimization hint to immediately compile the function. Otherwise the function would be lazily-compiled, which has additional overhead if that function is always called immediately as lazy compilation involves parsing the function twice. You can read V8's blog post about this for more details.

    Previously esbuild did not represent parentheses around functions in the AST so they were lost during compilation. With this change, esbuild will now preserve parentheses around function expressions when they are present in the original source code. This means these optimization hints will not be lost when bundling with esbuild. In addition, esbuild will now automatically add this optimization hint to immediately-invoked function expressions. Here's an example:

    // Original code
const fn0 = () => 0
const fn1 = (() => 1)
console.log(fn0, function() { return fn1() }())

    // Old output
    
const fn0 = () => 0;
    
const fn1 = () => 1;
    
console.log(fn0, function() {
    
return fn1();
    
}());
    

    // New output
    
const fn0 = () => 0;
    
const fn1 = (() => 1);
    
console.log(fn0, (function() {
    
return fn1();
    
})());

    Note that you do not want to wrap all function expressions in parentheses. This optimization hint should only be used for functions that are called on initial load. Using this hint for functions that are not called on initial load will unnecessarily delay the initial load. Again, see V8's blog post linked above for details.

  • Update Go from 1.23.10 to 1.23.12 (#4257, #4258)

    This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain false positive reports (specifically CVE-2025-4674 and CVE-2025-47907) from vulnerability scanners that only detect which version of the Go compiler esbuild uses.

v0.25.8

  • Fix another TypeScript parsing edge case (#4248)

    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:

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.25.9

  • Better support building projects that use Yarn on Windows (#3131, #3663)

    With this release, you can now use esbuild to bundle projects that use Yarn Plug'n'Play on Windows on drives other than the C: drive. The problem was as follows:

    1. Yarn in Plug'n'Play mode on Windows stores its global module cache on the C: drive
    2. Some developers put their projects on the D: drive
    3. Yarn generates relative paths that use ../.. to get from the project directory to the cache directory
    4. Windows-style paths don't support directory traversal between drives via .. (so D:\.. is just D:)
    5. I didn't have access to a Windows machine for testing this edge case

    Yarn works around this edge case by pretending Windows-style paths beginning with C:\ are actually Unix-style paths beginning with /C:/, so the ../.. path segments are able to navigate across drives inside Yarn's implementation. This was broken for a long time in esbuild but I finally got access to a Windows machine and was able to debug and fix this edge case. So you should now be able to bundle these projects with esbuild.

  • Preserve parentheses around function expressions (#4252)

    The V8 JavaScript VM uses parentheses around function expressions as an optimization hint to immediately compile the function. Otherwise the function would be lazily-compiled, which has additional overhead if that function is always called immediately as lazy compilation involves parsing the function twice. You can read V8's blog post about this for more details.

    Previously esbuild did not represent parentheses around functions in the AST so they were lost during compilation. With this change, esbuild will now preserve parentheses around function expressions when they are present in the original source code. This means these optimization hints will not be lost when bundling with esbuild. In addition, esbuild will now automatically add this optimization hint to immediately-invoked function expressions. Here's an example:

    // Original code
const fn0 = () => 0
const fn1 = (() => 1)
console.log(fn0, function() { return fn1() }())

    // Old output
    
const fn0 = () => 0;
    
const fn1 = () => 1;
    
console.log(fn0, function() {
    
return fn1();
    
}());
    

    // New output
    
const fn0 = () => 0;
    
const fn1 = (() => 1);
    
console.log(fn0, (function() {
    
return fn1();
    
})());

    Note that you do not want to wrap all function expressions in parentheses. This optimization hint should only be used for functions that are called on initial load. Using this hint for functions that are not called on initial load will unnecessarily delay the initial load. Again, see V8's blog post linked above for details.

  • Update Go from 1.23.10 to 1.23.12 (#4257, #4258)

    This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain false positive reports (specifically CVE-2025-4674 and CVE-2025-47907) from vulnerability scanners that only detect which version of the Go compiler esbuild uses.

0.25.8

  • Fix another TypeScript parsing edge case (#4248)

... (truncated)

Commits

Updates tsx from 4.20.3 to 4.20.4

Release notes

Sourced from tsx's releases.

v4.20.4

4.20.4 (2025-08-12)

Bug Fixes

This release is also available on:

Commits

Updates typescript-eslint from 8.39.0 to 8.39.1

Release notes

Sourced from typescript-eslint's releases.

v8.39.1

8.39.1 (2025-08-11)

🩹 Fixes

  • typescript-eslint: handle file:// urls in stack trace when inferring tsconfigRootDir (#11464)

❤️ Thank You

You can read about our versioning strategy and releases on our website.

Changelog

Sourced from typescript-eslint's changelog.

8.39.1 (2025-08-11)

🩹 Fixes

  • typescript-eslint: handle file:// urls in stack trace when inferring tsconfigRootDir (#11464)

❤️ Thank You

You can read about our versioning strategy and releases on our website.

Commits
  • b2ee794 chore(release): publish 8.39.1
  • 7319bad fix(typescript-eslint): handle file:// urls in stack trace when inferring `...
  • See full diff in compare view

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/1266 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 8/13/2025 **Status:** ✅ Merged **Merged:** 8/13/2025 **Merged by:** [@oschwartz10612](https://github.com/oschwartz10612) **Base:** `main` ← **Head:** `dependabot/npm_and_yarn/dev-patch-updates-eb33d068de` --- ### 📝 Commits (1) - [`a4d460e`](https://github.com/fosrl/pangolin/commit/a4d460e8507bc98ced80aba048ddfee609caf1e1) Bump the dev-patch-updates group across 1 directory with 6 updates ### 📊 Changes **2 files changed** (+190 additions, -190 deletions) <details> <summary>View changed files</summary> 📝 `package-lock.json` (+185 -185) 📝 `package.json` (+5 -5) </details> ### 📄 Description Bumps the dev-patch-updates group with 6 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.9` | | [tsx](https://github.com/privatenumber/tsx) | `4.20.3` | `4.20.4` | | [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.9 <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.9</h2> <ul> <li> <p>Better support building projects that use Yarn on Windows (<a href="https://redirect.github.com/evanw/esbuild/issues/3131">#3131</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/3663">#3663</a>)</p> <p>With this release, you can now use esbuild to bundle projects that use Yarn Plug'n'Play on Windows on drives other than the <code>C:</code> drive. The problem was as follows:</p> <ol> <li>Yarn in Plug'n'Play mode on Windows stores its global module cache on the <code>C:</code> drive</li> <li>Some developers put their projects on the <code>D:</code> drive</li> <li>Yarn generates relative paths that use <code>../..</code> to get from the project directory to the cache directory</li> <li>Windows-style paths don't support directory traversal between drives via <code>..</code> (so <code>D:\..</code> is just <code>D:</code>)</li> <li>I didn't have access to a Windows machine for testing this edge case</li> </ol> <p>Yarn works around this edge case by pretending Windows-style paths beginning with <code>C:\</code> are actually Unix-style paths beginning with <code>/C:/</code>, so the <code>../..</code> path segments are able to navigate across drives inside Yarn's implementation. This was broken for a long time in esbuild but I finally got access to a Windows machine and was able to debug and fix this edge case. So you should now be able to bundle these projects with esbuild.</p> </li> <li> <p>Preserve parentheses around function expressions (<a href="https://redirect.github.com/evanw/esbuild/issues/4252">#4252</a>)</p> <p>The V8 JavaScript VM uses parentheses around function expressions as an optimization hint to immediately compile the function. Otherwise the function would be lazily-compiled, which has additional overhead if that function is always called immediately as lazy compilation involves parsing the function twice. You can read <a href="https://v8.dev/blog/preparser">V8's blog post about this</a> for more details.</p> <p>Previously esbuild did not represent parentheses around functions in the AST so they were lost during compilation. With this change, esbuild will now preserve parentheses around function expressions when they are present in the original source code. This means these optimization hints will not be lost when bundling with esbuild. In addition, esbuild will now automatically add this optimization hint to immediately-invoked function expressions. Here's an example:</p> <pre lang="js"><code>// Original code const fn0 = () =&gt; 0 const fn1 = (() =&gt; 1) console.log(fn0, function() { return fn1() }()) <p>// Old output<br /> const fn0 = () =&gt; 0;<br /> const fn1 = () =&gt; 1;<br /> console.log(fn0, function() {<br /> return fn1();<br /> }());</p> <p>// New output<br /> const fn0 = () =&gt; 0;<br /> const fn1 = (() =&gt; 1);<br /> console.log(fn0, (function() {<br /> return fn1();<br /> })());<br /> </code></pre></p> <p>Note that you do not want to wrap all function expressions in parentheses. This optimization hint should only be used for functions that are called on initial load. Using this hint for functions that are not called on initial load will unnecessarily delay the initial load. Again, see V8's blog post linked above for details.</p> </li> <li> <p>Update Go from 1.23.10 to 1.23.12 (<a href="https://redirect.github.com/evanw/esbuild/issues/4257">#4257</a>, <a href="https://redirect.github.com/evanw/esbuild/pull/4258">#4258</a>)</p> <p>This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain false positive reports (specifically CVE-2025-4674 and CVE-2025-47907) from vulnerability scanners that only detect which version of the Go compiler esbuild uses.</p> </li> </ul> <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> </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.9</h2> <ul> <li> <p>Better support building projects that use Yarn on Windows (<a href="https://redirect.github.com/evanw/esbuild/issues/3131">#3131</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/3663">#3663</a>)</p> <p>With this release, you can now use esbuild to bundle projects that use Yarn Plug'n'Play on Windows on drives other than the <code>C:</code> drive. The problem was as follows:</p> <ol> <li>Yarn in Plug'n'Play mode on Windows stores its global module cache on the <code>C:</code> drive</li> <li>Some developers put their projects on the <code>D:</code> drive</li> <li>Yarn generates relative paths that use <code>../..</code> to get from the project directory to the cache directory</li> <li>Windows-style paths don't support directory traversal between drives via <code>..</code> (so <code>D:\..</code> is just <code>D:</code>)</li> <li>I didn't have access to a Windows machine for testing this edge case</li> </ol> <p>Yarn works around this edge case by pretending Windows-style paths beginning with <code>C:\</code> are actually Unix-style paths beginning with <code>/C:/</code>, so the <code>../..</code> path segments are able to navigate across drives inside Yarn's implementation. This was broken for a long time in esbuild but I finally got access to a Windows machine and was able to debug and fix this edge case. So you should now be able to bundle these projects with esbuild.</p> </li> <li> <p>Preserve parentheses around function expressions (<a href="https://redirect.github.com/evanw/esbuild/issues/4252">#4252</a>)</p> <p>The V8 JavaScript VM uses parentheses around function expressions as an optimization hint to immediately compile the function. Otherwise the function would be lazily-compiled, which has additional overhead if that function is always called immediately as lazy compilation involves parsing the function twice. You can read <a href="https://v8.dev/blog/preparser">V8's blog post about this</a> for more details.</p> <p>Previously esbuild did not represent parentheses around functions in the AST so they were lost during compilation. With this change, esbuild will now preserve parentheses around function expressions when they are present in the original source code. This means these optimization hints will not be lost when bundling with esbuild. In addition, esbuild will now automatically add this optimization hint to immediately-invoked function expressions. Here's an example:</p> <pre lang="js"><code>// Original code const fn0 = () =&gt; 0 const fn1 = (() =&gt; 1) console.log(fn0, function() { return fn1() }()) <p>// Old output<br /> const fn0 = () =&gt; 0;<br /> const fn1 = () =&gt; 1;<br /> console.log(fn0, function() {<br /> return fn1();<br /> }());</p> <p>// New output<br /> const fn0 = () =&gt; 0;<br /> const fn1 = (() =&gt; 1);<br /> console.log(fn0, (function() {<br /> return fn1();<br /> })());<br /> </code></pre></p> <p>Note that you do not want to wrap all function expressions in parentheses. This optimization hint should only be used for functions that are called on initial load. Using this hint for functions that are not called on initial load will unnecessarily delay the initial load. Again, see V8's blog post linked above for details.</p> </li> <li> <p>Update Go from 1.23.10 to 1.23.12 (<a href="https://redirect.github.com/evanw/esbuild/issues/4257">#4257</a>, <a href="https://redirect.github.com/evanw/esbuild/pull/4258">#4258</a>)</p> <p>This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain false positive reports (specifically CVE-2025-4674 and CVE-2025-47907) from vulnerability scanners that only detect which version of the Go compiler esbuild uses.</p> </li> </ul> <h2>0.25.8</h2> <ul> <li>Fix another TypeScript parsing edge case (<a href="https://redirect.github.com/evanw/esbuild/issues/4248">#4248</a>)</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/evanw/esbuild/commit/195e05c16f03a341390feef38b8ebf17d3075e14"><code>195e05c</code></a> publish 0.25.9 to npm</li> <li><a href="https://github.com/evanw/esbuild/commit/3dac33f2a2ba60387fb9aaca96b3e80b9e0512e0"><code>3dac33f</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/3131">#3131</a>, fix <a href="https://redirect.github.com/evanw/esbuild/issues/3663">#3663</a>: yarnpnp + windows + D drive</li> <li><a href="https://github.com/evanw/esbuild/commit/0f2c5c8c11dc3fa2a4e9e82df202d0b607e59de4"><code>0f2c5c8</code></a> mock fs now supports multiple volumes on windows</li> <li><a href="https://github.com/evanw/esbuild/commit/100a51e791ce714a1a90557bc9e5133fa0d38692"><code>100a51e</code></a> split out yarnpnp snapshot tests</li> <li><a href="https://github.com/evanw/esbuild/commit/13aace38bd1243e440061d1611e90a46ef55029c"><code>13aace3</code></a> remove <code>C:</code> assumption from windows snapshot tests</li> <li><a href="https://github.com/evanw/esbuild/commit/f1f413f18bce15a53fa4251f11a4747be94075e0"><code>f1f413f</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/4252">#4252</a>: preserve parentheses around functions</li> <li><a href="https://github.com/evanw/esbuild/commit/1bc809190bdb68ad27fc0a6e6d385b4f635c90e2"><code>1bc8091</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/4257">#4257</a>, close <a href="https://redirect.github.com/evanw/esbuild/issues/4258">#4258</a>: go 1.23.10 =&gt; 1.23.12</li> <li><a href="https://github.com/evanw/esbuild/commit/bc52135d02f794f28777c8e00db91997e0d98cab"><code>bc52135</code></a> move the go compiler version to <code>go.version</code></li> <li><a href="https://github.com/evanw/esbuild/commit/a0af5d1037c6e2509531151d153e875093f426b6"><code>a0af5d1</code></a> makefile: use <code>ESBUILD_VERSION</code> consistently</li> <li><a href="https://github.com/evanw/esbuild/commit/8c71947edbe5a158fec3a6d1cbfea1e8d5cdee70"><code>8c71947</code></a> publish 0.25.8 to npm</li> <li>Additional commits viewable in <a href="https://github.com/evanw/esbuild/compare/v0.25.6...v0.25.9">compare view</a></li> </ul> </details> <br /> Updates `tsx` from 4.20.3 to 4.20.4 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/privatenumber/tsx/releases">tsx's releases</a>.</em></p> <blockquote> <h2>v4.20.4</h2> <h2><a href="https://github.com/privatenumber/tsx/compare/v4.20.3...v4.20.4">4.20.4</a> (2025-08-12)</h2> <h3>Bug Fixes</h3> <ul> <li>override Node's native TS formats (<a href="https://redirect.github.com/privatenumber/tsx/issues/733">#733</a>) (<a href="https://github.com/privatenumber/tsx/commit/a639836fad4e60dbda6498b7851b6890e0c60a08">a639836</a>)</li> </ul> <hr /> <p>This release is also available on:</p> <ul> <li><a href="https://www.npmjs.com/package/tsx/v/4.20.4"><code>npm package (@​latest dist-tag)</code></a></li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/privatenumber/tsx/commit/a639836fad4e60dbda6498b7851b6890e0c60a08"><code>a639836</code></a> fix: override Node's native TS formats (<a href="https://redirect.github.com/privatenumber/tsx/issues/733">#733</a>)</li> <li><a href="https://github.com/privatenumber/tsx/commit/bddd4f5332ff35a4766357a19bcde4e60f841d1f"><code>bddd4f5</code></a> chore(deps): update dependency node to v20.19.3 (<a href="https://redirect.github.com/privatenumber/tsx/issues/720">#720</a>)</li> <li>See full diff in <a href="https://github.com/privatenumber/tsx/compare/v4.20.3...v4.20.4">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>
GiteaMirror added the pull-request label 2026-04-30 05:32:30 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
authentication
bug
config
dependencies
docker
documentation
enhancement
good first issue
help wanted
Improvement
Look Into
needs investigating
networking
new feature
non-critical bug
potential bug
pull-request
Mirrored from GitHub Pull Request
 question
reverse proxy
Security
stale
ui
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#9277
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?