github-starred/feeddeck
2
0
Fork 0
mirror of https://github.com/feeddeck/feeddeck.git synced 2026-03-09 07:02:01 -05:00
Code Issues 5 Packages Projects Releases 8 Wiki Activity

[PR #89] [MERGED] Bump the npm-email-templates group in /supabase/email-templates with 1 update #90

New Issue
Closed
opened 2025-10-31 16:57:08 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-10-31 16:57:08 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/feeddeck/feeddeck/pull/89
Author: @dependabot[bot]
Created: 12/1/2023
Status: ✅ Merged
Merged: 12/1/2023
Merged by: @ricoberger

Base: main ← Head: dependabot/npm_and_yarn/supabase/email-templates/npm-email-templates-20d3ffbca4

📝 Commits (2)

📊 Changes

2 files changed (+394 additions, -398 deletions)

View changed files

📝 supabase/email-templates/package-lock.json (+393 -397)
📝 supabase/email-templates/package.json (+1 -1)

📄 Description

Bumps the npm-email-templates group in /supabase/email-templates with 1 update: @react-email/components.

Updates @react-email/components from 0.0.10 to 0.0.11

Changelog

Sourced from @​react-email/components's changelog.

title: "Changelog" sidebarTitle: "Changelog" description: "New features, bug fixes, and improvements made to each package." "og:image": "https://react.email/static/covers/react-email.png" icon: "list-check"

Nov 01, 2023

Components 0.0.11

  • Upgrade @react-email/render to v0.0.9

Render 0.0.9

  • Fix renderAsync function to support Next.js 14

April 05. 2023

Button 0.0.8

  • Fix invalid CSS

Components 0.0.6

  • Upgrade components to latest version

Client 0.0.12

  • Remove nav block classname
  • Stop subprocess if an error occurs

Create Email 0.0.16

  • Fix required Node 18
  • Upgrade template to use latest versions

React Email 1.9.1

  • Upgrade client version to 0.0.12

Render 0.0.7

  • Add renderAsync function to enable edge runtime support

Preview 0.0.6

  • Fix 150 characters limit

... (truncated)

Commits

Dependabot compatibility score

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/feeddeck/feeddeck/pull/89 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 12/1/2023 **Status:** ✅ Merged **Merged:** 12/1/2023 **Merged by:** [@ricoberger](https://github.com/ricoberger) **Base:** `main` ← **Head:** `dependabot/npm_and_yarn/supabase/email-templates/npm-email-templates-20d3ffbca4` --- ### 📝 Commits (2) - [`d2bc057`](https://github.com/feeddeck/feeddeck/commit/d2bc05762dceddb7f3e8e81c5266f4998693711d) Bump the npm-email-templates group - [`497c890`](https://github.com/feeddeck/feeddeck/commit/497c89092025aa2efd5bb8d20e2ad9e51fdac1d8) Run `npm install` ### 📊 Changes **2 files changed** (+394 additions, -398 deletions) <details> <summary>View changed files</summary> 📝 `supabase/email-templates/package-lock.json` (+393 -397) 📝 `supabase/email-templates/package.json` (+1 -1) </details> ### 📄 Description Bumps the npm-email-templates group in /supabase/email-templates with 1 update: [@react-email/components](https://github.com/resendlabs/react-email/tree/HEAD/packages/components). Updates `@react-email/components` from 0.0.10 to 0.0.11 <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/resendlabs/react-email/blob/canary/docs/changelog.mdx"><code>@​react-email/components</code>'s changelog</a>.</em></p> <blockquote> <hr /> <h2>title: &quot;Changelog&quot; sidebarTitle: &quot;Changelog&quot; description: &quot;New features, bug fixes, and improvements made to each package.&quot; &quot;og:image&quot;: &quot;<a href="https://react.email/static/covers/react-email.png">https://react.email/static/covers/react-email.png</a>&quot; icon: &quot;list-check&quot;</h2> <h2>Nov 01, 2023</h2> <p><strong>Components <code>0.0.11</code></strong></p> <ul> <li>Upgrade <code>@react-email/render</code> to <code>v0.0.9</code></li> </ul> <p><strong>Render <code>0.0.9</code></strong></p> <ul> <li>Fix <code>renderAsync</code> function to support Next.js 14</li> </ul> <h2>April 05. 2023</h2> <p><strong>Button <code>0.0.8</code></strong></p> <ul> <li>Fix invalid CSS</li> </ul> <p><strong>Components <code>0.0.6</code></strong></p> <ul> <li>Upgrade components to latest version</li> </ul> <p><strong>Client <code>0.0.12</code></strong></p> <ul> <li>Remove nav block classname</li> <li>Stop subprocess if an error occurs</li> </ul> <p><strong>Create Email <code>0.0.16</code></strong></p> <ul> <li>Fix required Node 18</li> <li>Upgrade template to use latest versions</li> </ul> <p><strong>React Email <code>1.9.1</code></strong></p> <ul> <li>Upgrade client version to <code>0.0.12</code></li> </ul> <p><strong>Render <code>0.0.7</code></strong></p> <ul> <li>Add <code>renderAsync</code> function to enable edge runtime support</li> </ul> <p><strong>Preview <code>0.0.6</code></strong></p> <ul> <li>Fix 150 characters limit</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/resendlabs/react-email/commits/v0.0.11/packages/components">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=@react-email/components&package-manager=npm_and_yarn&previous-version=0.0.10&new-version=0.0.11)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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 2025-10-31 16:57:08 -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#90
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?