github-starred/feeddeck
2
0
Fork 0
mirror of https://github.com/feeddeck/feeddeck.git synced 2026-07-11 13:34:49 -05:00
Code Issues 257 Packages Projects Releases 8 Wiki Activity

[PR #335] chore(deps): bump esbuild and react-email in /supabase/email-templates #6051

New Issue
Open
opened 2026-06-15 05:13:38 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-06-15 05:13:38 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/feeddeck/feeddeck/pull/335
Author: @dependabot[bot]
Created: 6/14/2026
Status: 🔄 Open

Base: main ← Head: dependabot/npm_and_yarn/supabase/email-templates/multi-c39646fe4c

📝 Commits (1)

  • 471556d chore(deps): bump esbuild and react-email in /supabase/email-templates

📊 Changes

2 files changed (+539 additions, -818 deletions)

View changed files

📝 supabase/email-templates/package-lock.json (+538 -817)
📝 supabase/email-templates/package.json (+1 -1)

📄 Description

Bumps esbuild to 0.28.1 and updates ancestor dependency react-email. These dependencies need to be updated together.

Updates esbuild from 0.25.4 to 0.28.1

Release notes

Sourced from esbuild's releases.

v0.28.1

  • Disallow \ in local development server HTTP requests (GHSA-g7r4-m6w7-qqqr)

    This release fixes a security issue where HTTP requests to esbuild's local development server could traverse outside of the serve directory on Windows using a \ backslash character. It happened due to the use of Go's path.Clean() function, which only handles Unix-style / characters. HTTP requests with paths containing \ are no longer allowed.

    Thanks to @​dellalibera for reporting this issue.

  • Add integrity checks to the Deno API (GHSA-gv7w-rqvm-qjhr)

    The previous release of esbuild added integrity checks to esbuild's npm install script. This release also adds integrity checks to esbuild's Deno install script. Now esbuild's Deno API will also fail with an error if the downloaded esbuild binary contains something other than the expected content.

    Note that esbuild's Deno API installs from registry.npmjs.org by default, but allows the NPM_CONFIG_REGISTRY environment variable to override this with a custom package registry. This change means that the esbuild executable served by NPM_CONFIG_REGISTRY must now match the expected content.

    Thanks to @​sondt99 for reporting this issue.

  • Avoid inlining using and await using declarations (#4482)

    Previously esbuild's minifier sometimes incorrectly inlined using and await using declarations into subsequent uses of that declaration, which then fails to dispose of the resource correctly. This bug happened because inlining was done for let and const declarations by avoiding doing it for var declarations, which no longer worked when more declaration types were added. Here's an example:

    // Original code
{
  using x = new Resource()
  x.activate()
}

    // Old output (with --minify)
    
new Resource().activate();
    

    // New output (with --minify)
    
{using e=new Resource;e.activate()}

  • Fix module evaluation when an error is thrown (#4461, #4467)

    If an error is thrown during module evaluation, esbuild previously didn't preserve the state of the module for subsequent module references. This was observable if import() or require() is used to import a module multiple times. The thrown error is supposed to be thrown by every call to import() or require(), not just the first. With this release, esbuild will now throw the same error every time you call import() or require() on a module that throws during its evaluation.

  • Fix some edge cases around the new operator (#4477)

    Previously esbuild incorrectly printed certain edge cases involving complex expressions inside the target of a new expression (specifically an optional chain and/or a tagged template literal). The generated code for the new target was not correctly wrapped with parentheses, and either contained a syntax error or had different semantics. These edge cases have been fixed so that they now correctly wrap the new target in parentheses. Here is an example of some affected code:

    // Original code
new (foo()`bar`)()
new (foo()?.bar)()

    // Old output
    
new foo()bar();
    
new (foo())?.bar();

... (truncated)

Changelog

Sourced from esbuild's changelog.

Changelog: 2025

This changelog documents all esbuild versions published in the year 2025 (versions 0.25.0 through 0.27.2).

0.27.2

  • Allow import path specifiers starting with #/ (#4361)

    Previously the specification for package.json disallowed import path specifiers starting with #/, but this restriction has recently been relaxed and support for it is being added across the JavaScript ecosystem. One use case is using it for a wildcard pattern such as mapping #/* to ./src/* (previously you had to use another character such as #_* instead, which was more confusing). There is some more context in nodejs/node#49182.

    This change was contributed by @​hybrist.

  • Automatically add the -webkit-mask prefix (#4357, #4358)

    This release automatically adds the -webkit- vendor prefix for the mask CSS shorthand property:

    /* Original code */
main {
  mask: url(x.png) center/5rem no-repeat
}

    /* Old output (with --target=chrome110) */
    
main {
    
mask: url(x.png) center/5rem no-repeat;
    
}
    

    /* New output (with --target=chrome110) */
    
main {
    
-webkit-mask: url(x.png) center/5rem no-repeat;
    
mask: url(x.png) center/5rem no-repeat;
    
}

    This change was contributed by @​BPJEnnova.

  • Additional minification of switch statements (#4176, #4359)

    This release contains additional minification patterns for reducing switch statements. Here is an example:

    // Original code
switch (x) {
  case 0:
    foo()
    break
  case 1:
  default:
    bar()
}

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for esbuild since your current version.


Updates react-email from 4.2.6 to 6.6.0

Release notes

Sourced from react-email's releases.

react-email@6.6.0

Minor Changes

  • 16ff94c: add a useTitleTag in Preview component so users can disable it if they want to

react-email@6.5.0

Minor Changes

  • 3875d2a: add a --clients option to email dev and a COMPATIBILITY_EMAIL_CLIENTS environment variable to narrow which email clients trigger compatibility warnings. By default the preview still warns for gmail, apple-mail, outlook, and yahoo. Teams that only target one or two clients can now skip the noise: email dev --clients outlook,apple-mail. The CLI flag wins over the env var; an empty or fully-invalid list falls back to the defaults so warnings can't be silently switched off. Builds on #2797 by @​ReemX.

Patch Changes

  • d47825a: Add accessibility defaults to components: dir/lang on Body, an empty alt fallback on Img, role="presentation" on the Markdown table, and a <title> from Preview.

react-email@6.4.0

Minor Changes

  • ba99365: resolve and strip unresolved --tw-* CSS variables in non-inlinable rules so Tailwind media query utilities no longer break Gmail

react-email@6.3.3

No release notes provided.

react-email@6.3.2

Patch Changes

  • fbda5c8: increase whitespace padding to 200 characters for better Gmail preview text rendering

react-email@6.3.1

Patch Changes

  • c610dc0: fix: padding in Container/Section failing on Klaviyo and Outlook desktop

react-email@6.3.0

No release notes provided.

react-email@6.2.0

Minor Changes

  • 192d82a: Add theme and utility props to <Tailwind> for Tailwind v4 CSS-first configuration. Both accept a CSS string and can be combined with the existing config prop.

    import themeCss from "./theme.css?inline";

    <Tailwind theme={themeCss}>
    
<div className="bg-brand font-display">Custom themed content</div>
    
</Tailwind>;

    Empty strings are no-ops. The base Tailwind theme and utilities are still loaded — theme and utility layer on top.

... (truncated)

Changelog

Sourced from react-email's changelog.

6.6.0

Minor Changes

  • 16ff94c: add a useTitleTag in Preview component so users can disable it if they want to

6.5.0

Minor Changes

  • 3875d2a: add a --clients option to email dev and a COMPATIBILITY_EMAIL_CLIENTS environment variable to narrow which email clients trigger compatibility warnings. By default the preview still warns for gmail, apple-mail, outlook, and yahoo. Teams that only target one or two clients can now skip the noise: email dev --clients outlook,apple-mail. The CLI flag wins over the env var; an empty or fully-invalid list falls back to the defaults so warnings can't be silently switched off. Builds on #2797 by @​ReemX.

Patch Changes

  • d47825a: Add accessibility defaults to components: dir/lang on Body, an empty alt fallback on Img, role="presentation" on the Markdown table, and a <title> from Preview.

6.4.0

Minor Changes

  • ba99365: resolve and strip unresolved --tw-* CSS variables in non-inlinable rules so Tailwind media query utilities no longer break Gmail

6.3.3

6.3.2

Patch Changes

  • fbda5c8: increase whitespace padding to 200 characters for better Gmail preview text rendering

6.3.1

Patch Changes

  • c610dc0: fix: padding in Container/Section failing on Klaviyo and Outlook desktop

6.3.0

6.2.0

Minor Changes

  • 192d82a: Add theme and utility props to <Tailwind> for Tailwind v4 CSS-first configuration. Both accept a CSS string and can be combined with the existing config prop.

    import themeCss from "./theme.css?inline";

    <Tailwind theme={themeCss}>
    
<div className="bg-brand font-display">Custom themed content</div>
    
</Tailwind>;

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for react-email since your current version.


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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

🔄 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/feeddeck/feeddeck/pull/335 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 6/14/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `dependabot/npm_and_yarn/supabase/email-templates/multi-c39646fe4c` --- ### 📝 Commits (1) - [`471556d`](https://github.com/feeddeck/feeddeck/commit/471556d00db15e7cc386e7b89989084695a93cfa) chore(deps): bump esbuild and react-email in /supabase/email-templates ### 📊 Changes **2 files changed** (+539 additions, -818 deletions) <details> <summary>View changed files</summary> 📝 `supabase/email-templates/package-lock.json` (+538 -817) 📝 `supabase/email-templates/package.json` (+1 -1) </details> ### 📄 Description Bumps [esbuild](https://github.com/evanw/esbuild) to 0.28.1 and updates ancestor dependency [react-email](https://github.com/resend/react-email/tree/HEAD/packages/react-email). These dependencies need to be updated together. Updates `esbuild` from 0.25.4 to 0.28.1 <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.28.1</h2> <ul> <li> <p>Disallow <code>\</code> in local development server HTTP requests (<a href="https://github.com/evanw/esbuild/security/advisories/GHSA-g7r4-m6w7-qqqr">GHSA-g7r4-m6w7-qqqr</a>)</p> <p>This release fixes a security issue where HTTP requests to esbuild's local development server could traverse outside of the serve directory on Windows using a <code>\</code> backslash character. It happened due to the use of Go's <code>path.Clean()</code> function, which only handles Unix-style <code>/</code> characters. HTTP requests with paths containing <code>\</code> are no longer allowed.</p> <p>Thanks to <a href="https://github.com/dellalibera"><code>@​dellalibera</code></a> for reporting this issue.</p> </li> <li> <p>Add integrity checks to the Deno API (<a href="https://github.com/evanw/esbuild/security/advisories/GHSA-gv7w-rqvm-qjhr">GHSA-gv7w-rqvm-qjhr</a>)</p> <p>The previous release of esbuild added integrity checks to esbuild's npm install script. This release also adds integrity checks to esbuild's Deno install script. Now esbuild's Deno API will also fail with an error if the downloaded esbuild binary contains something other than the expected content.</p> <p>Note that esbuild's Deno API installs from <code>registry.npmjs.org</code> by default, but allows the <code>NPM_CONFIG_REGISTRY</code> environment variable to override this with a custom package registry. This change means that the esbuild executable served by <code>NPM_CONFIG_REGISTRY</code> must now match the expected content.</p> <p>Thanks to <a href="https://github.com/sondt99"><code>@​sondt99</code></a> for reporting this issue.</p> </li> <li> <p>Avoid inlining <code>using</code> and <code>await using</code> declarations (<a href="https://redirect.github.com/evanw/esbuild/issues/4482">#4482</a>)</p> <p>Previously esbuild's minifier sometimes incorrectly inlined <code>using</code> and <code>await using</code> declarations into subsequent uses of that declaration, which then fails to dispose of the resource correctly. This bug happened because inlining was done for <code>let</code> and <code>const</code> declarations by avoiding doing it for <code>var</code> declarations, which no longer worked when more declaration types were added. Here's an example:</p> <pre lang="js"><code>// Original code { using x = new Resource() x.activate() } <p>// Old output (with --minify)<br /> new Resource().activate();</p> <p>// New output (with --minify)<br /> {using e=new Resource;e.activate()}<br /> </code></pre></p> </li> <li> <p>Fix module evaluation when an error is thrown (<a href="https://redirect.github.com/evanw/esbuild/issues/4461">#4461</a>, <a href="https://redirect.github.com/evanw/esbuild/pull/4467">#4467</a>)</p> <p>If an error is thrown during module evaluation, esbuild previously didn't preserve the state of the module for subsequent module references. This was observable if <code>import()</code> or <code>require()</code> is used to import a module multiple times. The thrown error is supposed to be thrown by every call to <code>import()</code> or <code>require()</code>, not just the first. With this release, esbuild will now throw the same error every time you call <code>import()</code> or <code>require()</code> on a module that throws during its evaluation.</p> </li> <li> <p>Fix some edge cases around the <code>new</code> operator (<a href="https://redirect.github.com/evanw/esbuild/issues/4477">#4477</a>)</p> <p>Previously esbuild incorrectly printed certain edge cases involving complex expressions inside the target of a <code>new</code> expression (specifically an optional chain and/or a tagged template literal). The generated code for the <code>new</code> target was not correctly wrapped with parentheses, and either contained a syntax error or had different semantics. These edge cases have been fixed so that they now correctly wrap the <code>new</code> target in parentheses. Here is an example of some affected code:</p> <pre lang="js"><code>// Original code new (foo()`bar`)() new (foo()?.bar)() <p>// Old output<br /> new foo()<code>bar</code>();<br /> new (foo())?.bar();</p> <p></code></pre></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-2025.md">esbuild's changelog</a>.</em></p> <blockquote> <h1>Changelog: 2025</h1> <p>This changelog documents all esbuild versions published in the year 2025 (versions 0.25.0 through 0.27.2).</p> <h2>0.27.2</h2> <ul> <li> <p>Allow import path specifiers starting with <code>#/</code> (<a href="https://redirect.github.com/evanw/esbuild/pull/4361">#4361</a>)</p> <p>Previously the specification for <code>package.json</code> disallowed import path specifiers starting with <code>#/</code>, but this restriction <a href="https://redirect.github.com/nodejs/node/pull/60864">has recently been relaxed</a> and support for it is being added across the JavaScript ecosystem. One use case is using it for a wildcard pattern such as mapping <code>#/*</code> to <code>./src/*</code> (previously you had to use another character such as <code>#_*</code> instead, which was more confusing). There is some more context in <a href="https://redirect.github.com/nodejs/node/issues/49182">nodejs/node#49182</a>.</p> <p>This change was contributed by <a href="https://github.com/hybrist"><code>@​hybrist</code></a>.</p> </li> <li> <p>Automatically add the <code>-webkit-mask</code> prefix (<a href="https://redirect.github.com/evanw/esbuild/issues/4357">#4357</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/4358">#4358</a>)</p> <p>This release automatically adds the <code>-webkit-</code> vendor prefix for the <a href="https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Properties/mask"><code>mask</code></a> CSS shorthand property:</p> <pre lang="css"><code>/* Original code */ main { mask: url(x.png) center/5rem no-repeat } <p>/* Old output (with --target=chrome110) */<br /> main {<br /> mask: url(x.png) center/5rem no-repeat;<br /> }</p> <p>/* New output (with --target=chrome110) */<br /> main {<br /> -webkit-mask: url(x.png) center/5rem no-repeat;<br /> mask: url(x.png) center/5rem no-repeat;<br /> }<br /> </code></pre></p> <p>This change was contributed by <a href="https://github.com/BPJEnnova"><code>@​BPJEnnova</code></a>.</p> </li> <li> <p>Additional minification of <code>switch</code> statements (<a href="https://redirect.github.com/evanw/esbuild/issues/4176">#4176</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/4359">#4359</a>)</p> <p>This release contains additional minification patterns for reducing <code>switch</code> statements. Here is an example:</p> <pre lang="js"><code>// Original code switch (x) { case 0: foo() break case 1: default: bar() } </code></pre> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/evanw/esbuild/commit/bb9db84c02433fbe37b3509f53f9f3e3cc48725e"><code>bb9db84</code></a> publish 0.28.1 to npm</li> <li><a href="https://github.com/evanw/esbuild/commit/9ff053e53b8eeb990f59355dbea365277ac45ee2"><code>9ff053e</code></a> security: add integrity checks to the Deno API</li> <li><a href="https://github.com/evanw/esbuild/commit/0a9bf2135b67c7e28989a5ba19f0f000805a5ab5"><code>0a9bf21</code></a> enforce non-negative size in gzip parser</li> <li><a href="https://github.com/evanw/esbuild/commit/e2a1a7132058ee067fe736eac15f695861b8654e"><code>e2a1a71</code></a> security: forbid <code>\\</code> in local dev server requests</li> <li><a href="https://github.com/evanw/esbuild/commit/83a2cbfc35809f4fd5152da59572d7bed7739d78"><code>83a2cbf</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/4482">#4482</a>: don't inline <code>using</code> declarations</li> <li><a href="https://github.com/evanw/esbuild/commit/308ad745d824c77bc607603451b257d0f2fd9a38"><code>308ad74</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/4471">#4471</a>: renaming of nested <code>var</code> declarations</li> <li><a href="https://github.com/evanw/esbuild/commit/f013f5f99a015bce92ec48d49181d4ad3177b29b"><code>f013f5f</code></a> fix some typos</li> <li><a href="https://github.com/evanw/esbuild/commit/aafd6e48b1088336a5f5a17e930be7e840d43d8c"><code>aafd6e4</code></a> chore: fix some minor issues in comments (<a href="https://redirect.github.com/evanw/esbuild/issues/4462">#4462</a>)</li> <li><a href="https://github.com/evanw/esbuild/commit/15300c30b5e22f7cfcbed850c246d35095658386"><code>15300c3</code></a> follow up: cjs evaluation fixes</li> <li><a href="https://github.com/evanw/esbuild/commit/1bda0c31d7697c0af44b3ab39b81e599e559a395"><code>1bda0c3</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/4461">#4461</a>, fix <a href="https://redirect.github.com/evanw/esbuild/issues/4467">#4467</a>: esm evaluation fixes</li> <li>Additional commits viewable in <a href="https://github.com/evanw/esbuild/compare/v0.25.4...v0.28.1">compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~GitHub%20Actions">GitHub Actions</a>, a new releaser for esbuild since your current version.</p> </details> <br /> Updates `react-email` from 4.2.6 to 6.6.0 <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@6.6.0</h2> <h3>Minor Changes</h3> <ul> <li>16ff94c: add a useTitleTag in Preview component so users can disable it if they want to</li> </ul> <h2>react-email@6.5.0</h2> <h3>Minor Changes</h3> <ul> <li>3875d2a: add a <code>--clients</code> option to <code>email dev</code> and a <code>COMPATIBILITY_EMAIL_CLIENTS</code> environment variable to narrow which email clients trigger compatibility warnings. By default the preview still warns for <code>gmail</code>, <code>apple-mail</code>, <code>outlook</code>, and <code>yahoo</code>. Teams that only target one or two clients can now skip the noise: <code>email dev --clients outlook,apple-mail</code>. The CLI flag wins over the env var; an empty or fully-invalid list falls back to the defaults so warnings can't be silently switched off. Builds on <a href="https://github.com/resend/react-email/tree/HEAD/packages/react-email/issues/2797">#2797</a> by <a href="https://github.com/ReemX"><code>@​ReemX</code></a>.</li> </ul> <h3>Patch Changes</h3> <ul> <li>d47825a: Add accessibility defaults to components: <code>dir</code>/<code>lang</code> on <code>Body</code>, an empty <code>alt</code> fallback on <code>Img</code>, <code>role=&quot;presentation&quot;</code> on the <code>Markdown</code> table, and a <code>&lt;title&gt;</code> from <code>Preview</code>.</li> </ul> <h2>react-email@6.4.0</h2> <h3>Minor Changes</h3> <ul> <li>ba99365: resolve and strip unresolved <code>--tw-*</code> CSS variables in non-inlinable rules so Tailwind media query utilities no longer break Gmail</li> </ul> <h2>react-email@6.3.3</h2> <p>No release notes provided.</p> <h2>react-email@6.3.2</h2> <h3>Patch Changes</h3> <ul> <li>fbda5c8: increase whitespace padding to 200 characters for better Gmail preview text rendering</li> </ul> <h2>react-email@6.3.1</h2> <h3>Patch Changes</h3> <ul> <li>c610dc0: fix: padding in Container/Section failing on Klaviyo and Outlook desktop</li> </ul> <h2>react-email@6.3.0</h2> <p>No release notes provided.</p> <h2>react-email@6.2.0</h2> <h3>Minor Changes</h3> <ul> <li> <p>192d82a: Add <code>theme</code> and <code>utility</code> props to <code>&lt;Tailwind&gt;</code> for Tailwind v4 CSS-first configuration. Both accept a CSS string and can be combined with the existing <code>config</code> prop.</p> <pre lang="tsx"><code>import themeCss from &quot;./theme.css?inline&quot;; <p>&lt;Tailwind theme={themeCss}&gt;<br /> &lt;div className=&quot;bg-brand font-display&quot;&gt;Custom themed content&lt;/div&gt;<br /> &lt;/Tailwind&gt;;<br /> </code></pre></p> <p>Empty strings are no-ops. The base Tailwind theme and utilities are still loaded — <code>theme</code> and <code>utility</code> layer on top.</p> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </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>6.6.0</h2> <h3>Minor Changes</h3> <ul> <li>16ff94c: add a useTitleTag in Preview component so users can disable it if they want to</li> </ul> <h2>6.5.0</h2> <h3>Minor Changes</h3> <ul> <li>3875d2a: add a <code>--clients</code> option to <code>email dev</code> and a <code>COMPATIBILITY_EMAIL_CLIENTS</code> environment variable to narrow which email clients trigger compatibility warnings. By default the preview still warns for <code>gmail</code>, <code>apple-mail</code>, <code>outlook</code>, and <code>yahoo</code>. Teams that only target one or two clients can now skip the noise: <code>email dev --clients outlook,apple-mail</code>. The CLI flag wins over the env var; an empty or fully-invalid list falls back to the defaults so warnings can't be silently switched off. Builds on <a href="https://github.com/resend/react-email/tree/HEAD/packages/react-email/issues/2797">#2797</a> by <a href="https://github.com/ReemX"><code>@​ReemX</code></a>.</li> </ul> <h3>Patch Changes</h3> <ul> <li>d47825a: Add accessibility defaults to components: <code>dir</code>/<code>lang</code> on <code>Body</code>, an empty <code>alt</code> fallback on <code>Img</code>, <code>role=&quot;presentation&quot;</code> on the <code>Markdown</code> table, and a <code>&lt;title&gt;</code> from <code>Preview</code>.</li> </ul> <h2>6.4.0</h2> <h3>Minor Changes</h3> <ul> <li>ba99365: resolve and strip unresolved <code>--tw-*</code> CSS variables in non-inlinable rules so Tailwind media query utilities no longer break Gmail</li> </ul> <h2>6.3.3</h2> <h2>6.3.2</h2> <h3>Patch Changes</h3> <ul> <li>fbda5c8: increase whitespace padding to 200 characters for better Gmail preview text rendering</li> </ul> <h2>6.3.1</h2> <h3>Patch Changes</h3> <ul> <li>c610dc0: fix: padding in Container/Section failing on Klaviyo and Outlook desktop</li> </ul> <h2>6.3.0</h2> <h2>6.2.0</h2> <h3>Minor Changes</h3> <ul> <li> <p>192d82a: Add <code>theme</code> and <code>utility</code> props to <code>&lt;Tailwind&gt;</code> for Tailwind v4 CSS-first configuration. Both accept a CSS string and can be combined with the existing <code>config</code> prop.</p> <pre lang="tsx"><code>import themeCss from &quot;./theme.css?inline&quot;; <p>&lt;Tailwind theme={themeCss}&gt;<br /> &lt;div className=&quot;bg-brand font-display&quot;&gt;Custom themed content&lt;/div&gt;<br /> &lt;/Tailwind&gt;;<br /> </code></pre></p> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/resend/react-email/commit/6e3cf423001bd09e503c38482762f58ba826a513"><code>6e3cf42</code></a> chore(root): version packages (<a href="https://github.com/resend/react-email/tree/HEAD/packages/react-email/issues/3555">#3555</a>)</li> <li><a href="https://github.com/resend/react-email/commit/16ff94cc9b8d65a6dc9b002e36bf3ec9d4aecbf7"><code>16ff94c</code></a> feat(react-email): useTitleTag flag on Preview component (<a href="https://github.com/resend/react-email/tree/HEAD/packages/react-email/issues/3554">#3554</a>)</li> <li><a href="https://github.com/resend/react-email/commit/62630604e92aaca0c4d2fa0477cba1c0996856c4"><code>6263060</code></a> chore(root): version packages (<a href="https://github.com/resend/react-email/tree/HEAD/packages/react-email/issues/3548">#3548</a>)</li> <li><a href="https://github.com/resend/react-email/commit/3875d2a228450223c8130ed366aacb3bae7d9780"><code>3875d2a</code></a> feat(react-email): filter compatibility warnings by email client (<a href="https://github.com/resend/react-email/tree/HEAD/packages/react-email/issues/3547">#3547</a>)</li> <li><a href="https://github.com/resend/react-email/commit/d47825a4d7ce10514d3143ff69cba43799966aa3"><code>d47825a</code></a> feat: better accessibility defaults (<a href="https://github.com/resend/react-email/tree/HEAD/packages/react-email/issues/3546">#3546</a>)</li> <li><a href="https://github.com/resend/react-email/commit/c295594053ff02eb7387c844a9097b264f501b18"><code>c295594</code></a> chore(root): version packages (<a href="https://github.com/resend/react-email/tree/HEAD/packages/react-email/issues/3543">#3543</a>)</li> <li><a href="https://github.com/resend/react-email/commit/ba993652e42a300b899f7bb07e8fa846d853bef1"><code>ba99365</code></a> fix(tailwind): tw-* variables in non inlined rules (<a href="https://github.com/resend/react-email/tree/HEAD/packages/react-email/issues/3542">#3542</a>)</li> <li><a href="https://github.com/resend/react-email/commit/32cb16c5ff69f5ab060aa896d1aaee060fc9e1cd"><code>32cb16c</code></a> fix(editor): repair columns.spec.tsx type errors + run typecheck on CI (<a href="https://github.com/resend/react-email/tree/HEAD/packages/react-email/issues/3539">#3539</a>)</li> <li><a href="https://github.com/resend/react-email/commit/a79acd1f19f4da032ad7c287d78b9ec3dcbb2da0"><code>a79acd1</code></a> chore(root): version packages (<a href="https://github.com/resend/react-email/tree/HEAD/packages/react-email/issues/3535">#3535</a>)</li> <li><a href="https://github.com/resend/react-email/commit/7745296a31a7d463a170c7f3f8dc3f70a69a24ae"><code>7745296</code></a> chore(root): version packages (<a href="https://github.com/resend/react-email/tree/HEAD/packages/react-email/issues/3533">#3533</a>)</li> <li>Additional commits viewable in <a href="https://github.com/resend/react-email/commits/react-email@6.6.0/packages/react-email">compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~GitHub%20Actions">GitHub Actions</a>, a new releaser for react-email since your current version.</p> </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 show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/feeddeck/feeddeck/network/alerts). </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-06-15 05:13:38 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
pull-request
Mirrored from GitHub Pull Request
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/feeddeck#6051
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?