github-starred/feeddeck
2
0
Fork 0
mirror of https://github.com/feeddeck/feeddeck.git synced 2026-03-22 21:09:51 -05:00
Code Issues 23 Packages Projects Releases 8 Wiki Activity

[PR #30] [MERGED] [core] Update NPM Packages #317

New Issue
Closed
opened 2026-03-22 12:47:41 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-03-22 12:47:41 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/feeddeck/feeddeck/pull/30
Author: @ricoberger
Created: 10/13/2023
Status: ✅ Merged
Merged: 10/13/2023
Merged by: @ricoberger

Base: main ← Head: update-npm-packages-2023-10-13

📝 Commits (1)

  • e5a8aa1 [core] Update NPM Packages

📊 Changes

4 files changed (+1933 additions, -2120 deletions)

View changed files

📝 landing/package-lock.json (+782 -932)
📝 landing/package.json (+12 -12)
📝 supabase/email-templates/package-lock.json (+1137 -1174)
📝 supabase/email-templates/package.json (+2 -2)

📄 Description

Update the npm packages used by the email templates and the landing 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/30 **Author:** [@ricoberger](https://github.com/ricoberger) **Created:** 10/13/2023 **Status:** ✅ Merged **Merged:** 10/13/2023 **Merged by:** [@ricoberger](https://github.com/ricoberger) **Base:** `main` ← **Head:** `update-npm-packages-2023-10-13` --- ### 📝 Commits (1) - [`e5a8aa1`](https://github.com/feeddeck/feeddeck/commit/e5a8aa1dcda61b5f8df46c2c756e02896b8dc66b) [core] Update NPM Packages ### 📊 Changes **4 files changed** (+1933 additions, -2120 deletions) <details> <summary>View changed files</summary> 📝 `landing/package-lock.json` (+782 -932) 📝 `landing/package.json` (+12 -12) 📝 `supabase/email-templates/package-lock.json` (+1137 -1174) 📝 `supabase/email-templates/package.json` (+2 -2) </details> ### 📄 Description Update the npm packages used by the email templates and the landing page. <!-- Keep PR title verbose enough and add prefix telling about what source it touches e.g "[rss] Add feature xyz" or if the the PR is not realated to a source use "[core]", e.g. "[core] Fix xyz". If you add a breaking change within your PR you should add ":warning:" to the title, e.g. ":warning: [core] My breaking change" --> <!-- Description of what have been changed. Please also reference an issue, when available. --> --- <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-03-22 12:47:41 -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#317
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?