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

[PR #1033] [CLOSED] Bump the dev-patch-updates group across 1 directory with 4 updates #4355

New Issue
Closed
opened 2026-04-20 08:49:03 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-20 08:49:03 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/fosrl/pangolin/pull/1033
Author: @dependabot[bot]
Created: 7/8/2025
Status: ❌ Closed

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

📝 Commits (1)

  • 136829e Bump the dev-patch-updates group across 1 directory with 4 updates

📊 Changes

2 files changed (+164 additions, -163 deletions)

View changed files

📝 package-lock.json (+161 -160)
📝 package.json (+3 -3)

📄 Description

Bumps the dev-patch-updates group with 4 updates in the / directory: @types/node, drizzle-kit, esbuild and react-email.

Updates @types/node from 24.0.7 to 24.0.10

Commits

Updates drizzle-kit from 0.31.2 to 0.31.4

Release notes

Sourced from drizzle-kit's releases.

drizzle-kit@0.31.4

  • Fixed halfvec, bit and sparsevec type generation bug in drizzle-kit

drizzle-kit@0.31.3

  • Internal changes to Studio context. Added databaseName and packageName properties for Studio
Commits

Updates esbuild from 0.25.5 to 0.25.6

Release notes

Sourced from esbuild's releases.

v0.25.6

  • Fix a memory leak when cancel() is used on a build context (#4231)

    Calling rebuild() followed by cancel() in rapid succession could previously leak memory. The bundler uses a producer/consumer model internally, and the resource leak was caused by the consumer being termianted while there were still remaining unreceived results from a producer. To avoid the leak, the consumer now waits for all producers to finish before terminating.

  • Support empty :is() and :where() syntax in CSS (#4232)

    Previously using these selectors with esbuild would generate a warning. That warning has been removed in this release for these cases.

  • Improve tree-shaking of try statements in dead code (#4224)

    With this release, esbuild will now remove certain try statements if esbuild considers them to be within dead code (i.e. code that is known to not ever be evaluated). For example:

    // Original code
return 'foo'
try { return 'bar' } catch {}

    // Old output (with --minify)
return"foo";try{return"bar"}catch{}
    

    // New output (with --minify)
return"foo";

  • Consider negated bigints to have no side effects

    While esbuild currently considers 1, -1, and 1n to all have no side effects, it didn't previously consider -1n to have no side effects. This is because esbuild does constant folding with numbers but not bigints. However, it meant that unused negative bigint constants were not tree-shaken. With this release, esbuild will now consider these expressions to also be side-effect free:

    // Original code
let a = 1, b = -1, c = 1n, d = -1n

    // Old output (with --bundle --minify)
(()=>{var n=-1n;})();
    

    // New output (with --bundle --minify)
(()=>{})();

  • Support a configurable delay in watch mode before rebuilding (#3476, #4178)

    The watch() API now takes a delay option that lets you add a delay (in milliseconds) before rebuilding when a change is detected in watch mode. If you use a tool that regenerates multiple source files very slowly, this should make it more likely that esbuild's watch mode won't generate a broken intermediate build before the successful final build. This option is also available via the CLI using the --watch-delay= flag.

    This should also help avoid confusion about the watch() API's options argument. It was previously empty to allow for future API expansion, which caused some people to think that the documentation was missing. It's no longer empty now that the watch() API has an option.

  • Allow mixed array for entryPoints API option (#4223)

    The TypeScript type definitions now allow you to pass a mixed array of both string literals and object literals to the entryPoints API option, such as ['foo.js', { out: 'lib', in: 'bar.js' }]. This was always possible to do in JavaScript but the TypeScript type definitions were previously too restrictive.

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.25.6

  • Fix a memory leak when cancel() is used on a build context (#4231)

    Calling rebuild() followed by cancel() in rapid succession could previously leak memory. The bundler uses a producer/consumer model internally, and the resource leak was caused by the consumer being termianted while there were still remaining unreceived results from a producer. To avoid the leak, the consumer now waits for all producers to finish before terminating.

  • Support empty :is() and :where() syntax in CSS (#4232)

    Previously using these selectors with esbuild would generate a warning. That warning has been removed in this release for these cases.

  • Improve tree-shaking of try statements in dead code (#4224)

    With this release, esbuild will now remove certain try statements if esbuild considers them to be within dead code (i.e. code that is known to not ever be evaluated). For example:

    // Original code
return 'foo'
try { return 'bar' } catch {}

    // Old output (with --minify)
return"foo";try{return"bar"}catch{}
    

    // New output (with --minify)
return"foo";

  • Consider negated bigints to have no side effects

    While esbuild currently considers 1, -1, and 1n to all have no side effects, it didn't previously consider -1n to have no side effects. This is because esbuild does constant folding with numbers but not bigints. However, it meant that unused negative bigint constants were not tree-shaken. With this release, esbuild will now consider these expressions to also be side-effect free:

    // Original code
let a = 1, b = -1, c = 1n, d = -1n

    // Old output (with --bundle --minify)
(()=>{var n=-1n;})();
    

    // New output (with --bundle --minify)
(()=>{})();

  • Support a configurable delay in watch mode before rebuilding (#3476, #4178)

    The watch() API now takes a delay option that lets you add a delay (in milliseconds) before rebuilding when a change is detected in watch mode. If you use a tool that regenerates multiple source files very slowly, this should make it more likely that esbuild's watch mode won't generate a broken intermediate build before the successful final build. This option is also available via the CLI using the --watch-delay= flag.

    This should also help avoid confusion about the watch() API's options argument. It was previously empty to allow for future API expansion, which caused some people to think that the documentation was missing. It's no longer empty now that the watch() API has an option.

  • Allow mixed array for entryPoints API option (#4223)

    The TypeScript type definitions now allow you to pass a mixed array of both string literals and object literals to the entryPoints API option, such as ['foo.js', { out: 'lib', in: 'bar.js' }]. This was always possible to do in JavaScript but the TypeScript type definitions were previously too restrictive.

... (truncated)

Commits

Updates react-email from 4.0.16 to 4.0.17

Release notes

Sourced from react-email's releases.

react-email@4.0.17

Patch Changes

  • e352a67: fix <svg> not being flagged as incompatible
  • 8f64ebd: fix the forced color-scheme: dark for the preview
  • 6de4e9f: fix static file serving security issue with logging
  • b2e96d5: add support for hot reloading with tsconfig path aliases
  • 6b0cfd6: fix hot reloading with collapsed directories
  • 8c93330: fix prettier errors causing Next.js serialization error
  • a07eebf: pre-render email templates on hover

Full Changelog: https://github.com/resend/react-email/compare/react-email@4.0.16...react-email@4.0.17

Changelog

Sourced from react-email's changelog.

4.0.17

Patch Changes

  • e352a67: fix <svg> not being flagged as incompatible
  • 8f64ebd: fix the forced color-scheme: dark for the preview
  • 6de4e9f: fix static file serving security issue with logging
  • b2e96d5: Add support for hot reloading with tsconfig path aliases
  • 6b0cfd6: fix hot reloading with collapsed directories
  • 8c93330: Fix prettier errors causing NextJS serialization error
  • a07eebf: Pre-render email templates on hover
Commits
  • 11d4751 chore(root): Version packages (#2313)
  • 8f64ebd fix(preview-server): forced color-scheme: dark (#2271)
  • 6de4e9f fix(react-email): security issue with path for static files (#2289)
  • 6b0cfd6 fix(preview-server): hot reloading with collapsed directories (#2284)
  • e352a67 fix(preview-server): \<svg> not being flagged by compatibility checker (#2259)
  • 8c93330 fix(react-email): prettier errors causing NextJS serialization error (#2214)
  • cb83898 feat(react-email): TypeScript's path aliases support for hot reloading (#2215)
  • a07eebf chore(react-email): Pre-render email templates on hover (#2187)
  • b30dad1 feat(button): respect the user's order of padding properties (#2234)
  • 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/1033 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 7/8/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `dependabot/npm_and_yarn/dev-patch-updates-f7be44abd0` --- ### 📝 Commits (1) - [`136829e`](https://github.com/fosrl/pangolin/commit/136829eca13bb2a8c067cb30db8a9eb68fefc6b1) Bump the dev-patch-updates group across 1 directory with 4 updates ### 📊 Changes **2 files changed** (+164 additions, -163 deletions) <details> <summary>View changed files</summary> 📝 `package-lock.json` (+161 -160) 📝 `package.json` (+3 -3) </details> ### 📄 Description Bumps the dev-patch-updates group with 4 updates in the / directory: [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node), [drizzle-kit](https://github.com/drizzle-team/drizzle-orm), [esbuild](https://github.com/evanw/esbuild) and [react-email](https://github.com/resend/react-email/tree/HEAD/packages/react-email). Updates `@types/node` from 24.0.7 to 24.0.10 <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 `drizzle-kit` from 0.31.2 to 0.31.4 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/drizzle-team/drizzle-orm/releases">drizzle-kit's releases</a>.</em></p> <blockquote> <h2>drizzle-kit@0.31.4</h2> <ul> <li>Fixed <code>halfvec</code>, <code>bit</code> and <code>sparsevec</code> type generation bug in drizzle-kit</li> </ul> <h2>drizzle-kit@0.31.3</h2> <ul> <li>Internal changes to Studio context. Added <code>databaseName</code> and <code>packageName</code> properties for Studio</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/drizzle-team/drizzle-orm/commit/ac1dcd9d1c4b8f171479af4a5dd731db1e164f58"><code>ac1dcd9</code></a> Fix hakfvec (<a href="https://redirect.github.com/drizzle-team/drizzle-orm/issues/4689">#4689</a>)</li> <li><a href="https://github.com/drizzle-team/drizzle-orm/commit/5c6b3afbb70bcef96ca60b528de42ef09f39ca6f"><code>5c6b3af</code></a> Add <code>databaseName</code> and <code>packageName</code> properties for studio (<a href="https://redirect.github.com/drizzle-team/drizzle-orm/issues/4683">#4683</a>)</li> <li>See full diff in <a href="https://github.com/drizzle-team/drizzle-orm/compare/drizzle-kit@0.31.2...drizzle-kit@0.31.4">compare view</a></li> </ul> </details> <br /> Updates `esbuild` from 0.25.5 to 0.25.6 <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.6</h2> <ul> <li> <p>Fix a memory leak when <code>cancel()</code> is used on a build context (<a href="https://redirect.github.com/evanw/esbuild/issues/4231">#4231</a>)</p> <p>Calling <code>rebuild()</code> followed by <code>cancel()</code> in rapid succession could previously leak memory. The bundler uses a producer/consumer model internally, and the resource leak was caused by the consumer being termianted while there were still remaining unreceived results from a producer. To avoid the leak, the consumer now waits for all producers to finish before terminating.</p> </li> <li> <p>Support empty <code>:is()</code> and <code>:where()</code> syntax in CSS (<a href="https://redirect.github.com/evanw/esbuild/issues/4232">#4232</a>)</p> <p>Previously using these selectors with esbuild would generate a warning. That warning has been removed in this release for these cases.</p> </li> <li> <p>Improve tree-shaking of <code>try</code> statements in dead code (<a href="https://redirect.github.com/evanw/esbuild/issues/4224">#4224</a>)</p> <p>With this release, esbuild will now remove certain <code>try</code> statements if esbuild considers them to be within dead code (i.e. code that is known to not ever be evaluated). For example:</p> <pre lang="js"><code>// Original code return 'foo' try { return 'bar' } catch {} <p>// Old output (with --minify) return&quot;foo&quot;;try{return&quot;bar&quot;}catch{}</p> <p>// New output (with --minify) return&quot;foo&quot;; </code></pre></p> </li> <li> <p>Consider negated bigints to have no side effects</p> <p>While esbuild currently considers <code>1</code>, <code>-1</code>, and <code>1n</code> to all have no side effects, it didn't previously consider <code>-1n</code> to have no side effects. This is because esbuild does constant folding with numbers but not bigints. However, it meant that unused negative bigint constants were not tree-shaken. With this release, esbuild will now consider these expressions to also be side-effect free:</p> <pre lang="js"><code>// Original code let a = 1, b = -1, c = 1n, d = -1n <p>// Old output (with --bundle --minify) (()=&gt;{var n=-1n;})();</p> <p>// New output (with --bundle --minify) (()=&gt;{})(); </code></pre></p> </li> <li> <p>Support a configurable delay in watch mode before rebuilding (<a href="https://redirect.github.com/evanw/esbuild/issues/3476">#3476</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/4178">#4178</a>)</p> <p>The <code>watch()</code> API now takes a <code>delay</code> option that lets you add a delay (in milliseconds) before rebuilding when a change is detected in watch mode. If you use a tool that regenerates multiple source files very slowly, this should make it more likely that esbuild's watch mode won't generate a broken intermediate build before the successful final build. This option is also available via the CLI using the <code>--watch-delay=</code> flag.</p> <p>This should also help avoid confusion about the <code>watch()</code> API's options argument. It was previously empty to allow for future API expansion, which caused some people to think that the documentation was missing. It's no longer empty now that the <code>watch()</code> API has an option.</p> </li> <li> <p>Allow mixed array for <code>entryPoints</code> API option (<a href="https://redirect.github.com/evanw/esbuild/issues/4223">#4223</a>)</p> <p>The TypeScript type definitions now allow you to pass a mixed array of both string literals and object literals to the <code>entryPoints</code> API option, such as <code>['foo.js', { out: 'lib', in: 'bar.js' }]</code>. This was always possible to do in JavaScript but the TypeScript type definitions were previously too restrictive.</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.6</h2> <ul> <li> <p>Fix a memory leak when <code>cancel()</code> is used on a build context (<a href="https://redirect.github.com/evanw/esbuild/issues/4231">#4231</a>)</p> <p>Calling <code>rebuild()</code> followed by <code>cancel()</code> in rapid succession could previously leak memory. The bundler uses a producer/consumer model internally, and the resource leak was caused by the consumer being termianted while there were still remaining unreceived results from a producer. To avoid the leak, the consumer now waits for all producers to finish before terminating.</p> </li> <li> <p>Support empty <code>:is()</code> and <code>:where()</code> syntax in CSS (<a href="https://redirect.github.com/evanw/esbuild/issues/4232">#4232</a>)</p> <p>Previously using these selectors with esbuild would generate a warning. That warning has been removed in this release for these cases.</p> </li> <li> <p>Improve tree-shaking of <code>try</code> statements in dead code (<a href="https://redirect.github.com/evanw/esbuild/issues/4224">#4224</a>)</p> <p>With this release, esbuild will now remove certain <code>try</code> statements if esbuild considers them to be within dead code (i.e. code that is known to not ever be evaluated). For example:</p> <pre lang="js"><code>// Original code return 'foo' try { return 'bar' } catch {} <p>// Old output (with --minify) return&quot;foo&quot;;try{return&quot;bar&quot;}catch{}</p> <p>// New output (with --minify) return&quot;foo&quot;; </code></pre></p> </li> <li> <p>Consider negated bigints to have no side effects</p> <p>While esbuild currently considers <code>1</code>, <code>-1</code>, and <code>1n</code> to all have no side effects, it didn't previously consider <code>-1n</code> to have no side effects. This is because esbuild does constant folding with numbers but not bigints. However, it meant that unused negative bigint constants were not tree-shaken. With this release, esbuild will now consider these expressions to also be side-effect free:</p> <pre lang="js"><code>// Original code let a = 1, b = -1, c = 1n, d = -1n <p>// Old output (with --bundle --minify) (()=&gt;{var n=-1n;})();</p> <p>// New output (with --bundle --minify) (()=&gt;{})(); </code></pre></p> </li> <li> <p>Support a configurable delay in watch mode before rebuilding (<a href="https://redirect.github.com/evanw/esbuild/issues/3476">#3476</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/4178">#4178</a>)</p> <p>The <code>watch()</code> API now takes a <code>delay</code> option that lets you add a delay (in milliseconds) before rebuilding when a change is detected in watch mode. If you use a tool that regenerates multiple source files very slowly, this should make it more likely that esbuild's watch mode won't generate a broken intermediate build before the successful final build. This option is also available via the CLI using the <code>--watch-delay=</code> flag.</p> <p>This should also help avoid confusion about the <code>watch()</code> API's options argument. It was previously empty to allow for future API expansion, which caused some people to think that the documentation was missing. It's no longer empty now that the <code>watch()</code> API has an option.</p> </li> <li> <p>Allow mixed array for <code>entryPoints</code> API option (<a href="https://redirect.github.com/evanw/esbuild/issues/4223">#4223</a>)</p> <p>The TypeScript type definitions now allow you to pass a mixed array of both string literals and object literals to the <code>entryPoints</code> API option, such as <code>['foo.js', { out: 'lib', in: 'bar.js' }]</code>. This was always possible to do in JavaScript but the TypeScript type definitions were previously too restrictive.</p> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/evanw/esbuild/commit/d38c1f0bc580b4a8a93f23559d0cd9085d7ba31f"><code>d38c1f0</code></a> publish 0.25.6 to npm</li> <li><a href="https://github.com/evanw/esbuild/commit/11e547e2c7b4238a626c1fd10759e058c8477daa"><code>11e547e</code></a> missing <code>)</code> in release notes</li> <li><a href="https://github.com/evanw/esbuild/commit/cc8ac0a5f49589d9a0698728106ffa43d51aa1b3"><code>cc8ac0a</code></a> fix trailing comment whitespace</li> <li><a href="https://github.com/evanw/esbuild/commit/1e3fb57adcbd51b35712ea53e215f5368a8cd708"><code>1e3fb57</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/4178">#4178</a>: add the <code>--watch-delay=</code> option</li> <li><a href="https://github.com/evanw/esbuild/commit/c1f5f18e8308be3eaf064c0d059bfee00cc628e7"><code>c1f5f18</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/4209">#4209</a>: disable binary executable optimization on WASM platform (<a href="https://redirect.github.com/evanw/esbuild/issues/4210">#4210</a>)</li> <li><a href="https://github.com/evanw/esbuild/commit/3ed5ecce847ace6f016290d10fbae9359b0351d3"><code>3ed5ecc</code></a> fix incorrect locations in <code>CHANGELOG.md</code></li> <li><a href="https://github.com/evanw/esbuild/commit/248089c1a8398a219720e8ef5601d2b7001c64d4"><code>248089c</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/4224">#4224</a>: allow <code>try</code> statements to become dead</li> <li><a href="https://github.com/evanw/esbuild/commit/42f159cb52e1d7de826b5b52f307c45b587a5646"><code>42f159c</code></a> openharmony: keep makefile targets sorted</li> <li><a href="https://github.com/evanw/esbuild/commit/63256e12bedc47a7bd13d315e5c0712908f31a14"><code>63256e1</code></a> chore: fix some comments (<a href="https://redirect.github.com/evanw/esbuild/issues/4211">#4211</a>)</li> <li><a href="https://github.com/evanw/esbuild/commit/d803f72e64c900e6b007501c81b987832ffc3c81"><code>d803f72</code></a> add support for openharmony-arm64 platform (<a href="https://redirect.github.com/evanw/esbuild/issues/4212">#4212</a>)</li> <li>Additional commits viewable in <a href="https://github.com/evanw/esbuild/compare/v0.25.5...v0.25.6">compare view</a></li> </ul> </details> <br /> Updates `react-email` from 4.0.16 to 4.0.17 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/resend/react-email/releases">react-email's releases</a>.</em></p> <blockquote> <h2>react-email@4.0.17</h2> <h3>Patch Changes</h3> <ul> <li>e352a67: fix <code>&lt;svg&gt;</code> not being flagged as incompatible</li> <li>8f64ebd: fix the forced <code>color-scheme: dark</code> for the preview</li> <li>6de4e9f: fix static file serving security issue with logging</li> <li>b2e96d5: add support for hot reloading with tsconfig path aliases</li> <li>6b0cfd6: fix hot reloading with collapsed directories</li> <li>8c93330: fix prettier errors causing Next.js serialization error</li> <li>a07eebf: pre-render email templates on hover</li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/resend/react-email/compare/react-email@4.0.16...react-email@4.0.17">https://github.com/resend/react-email/compare/react-email@4.0.16...react-email@4.0.17</a></p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/resend/react-email/blob/canary/packages/react-email/CHANGELOG.md">react-email's changelog</a>.</em></p> <blockquote> <h2>4.0.17</h2> <h3>Patch Changes</h3> <ul> <li>e352a67: fix <code>&lt;svg&gt;</code> not being flagged as incompatible</li> <li>8f64ebd: fix the forced <code>color-scheme: dark</code> for the preview</li> <li>6de4e9f: fix static file serving security issue with logging</li> <li>b2e96d5: Add support for hot reloading with tsconfig path aliases</li> <li>6b0cfd6: fix hot reloading with collapsed directories</li> <li>8c93330: Fix prettier errors causing NextJS serialization error</li> <li>a07eebf: Pre-render email templates on hover</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/resend/react-email/commit/11d4751f1cd0897405972350c2f683c659492f43"><code>11d4751</code></a> chore(root): Version packages (<a href="https://github.com/resend/react-email/tree/HEAD/packages/react-email/issues/2313">#2313</a>)</li> <li><a href="https://github.com/resend/react-email/commit/8f64ebdc339a5a3b8c0198e2e31ef6af10a50872"><code>8f64ebd</code></a> fix(preview-server): forced <code>color-scheme: dark</code> (<a href="https://github.com/resend/react-email/tree/HEAD/packages/react-email/issues/2271">#2271</a>)</li> <li><a href="https://github.com/resend/react-email/commit/6de4e9f31879807e69f23149401e7021a42edf8f"><code>6de4e9f</code></a> fix(react-email): security issue with path for static files (<a href="https://github.com/resend/react-email/tree/HEAD/packages/react-email/issues/2289">#2289</a>)</li> <li><a href="https://github.com/resend/react-email/commit/6b0cfd6be32b1efdac316713fbdb5f8a09087601"><code>6b0cfd6</code></a> fix(preview-server): hot reloading with collapsed directories (<a href="https://github.com/resend/react-email/tree/HEAD/packages/react-email/issues/2284">#2284</a>)</li> <li><a href="https://github.com/resend/react-email/commit/e352a67519f7af266b6f2c6965469c936c19337b"><code>e352a67</code></a> fix(preview-server): <code>\&lt;svg&gt;</code> not being flagged by compatibility checker (<a href="https://github.com/resend/react-email/tree/HEAD/packages/react-email/issues/2259">#2259</a>)</li> <li><a href="https://github.com/resend/react-email/commit/8c93330d65616f754c418c33c086421ee846a866"><code>8c93330</code></a> fix(react-email): prettier errors causing NextJS serialization error (<a href="https://github.com/resend/react-email/tree/HEAD/packages/react-email/issues/2214">#2214</a>)</li> <li><a href="https://github.com/resend/react-email/commit/cb83898896ed394f00b9192eff357754e1556011"><code>cb83898</code></a> feat(react-email): TypeScript's path aliases support for hot reloading (<a href="https://github.com/resend/react-email/tree/HEAD/packages/react-email/issues/2215">#2215</a>)</li> <li><a href="https://github.com/resend/react-email/commit/a07eebf2c052ae6852f06c9a3d1e798c653b4571"><code>a07eebf</code></a> chore(react-email): Pre-render email templates on hover (<a href="https://github.com/resend/react-email/tree/HEAD/packages/react-email/issues/2187">#2187</a>)</li> <li><a href="https://github.com/resend/react-email/commit/b30dad1cc010cf91ad1ec51ac986ed87cd1905a4"><code>b30dad1</code></a> feat(button): respect the user's order of padding properties (<a href="https://github.com/resend/react-email/tree/HEAD/packages/react-email/issues/2234">#2234</a>)</li> <li>See full diff in <a href="https://github.com/resend/react-email/commits/react-email@4.0.17/packages/react-email">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-20 08:49:03 -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#4355
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?