[PR #34] [CLOSED] Add GitHub Actions workflow for creating plugin releases with manifest #76

New issue

Closed

opened 2026-05-07 00:17:56 +02:00 by BreizhHardware · 0 comments

BreizhHardware commented

2026-05-07 00:17:56 +02:00

Owner

📋 Pull Request Information

Original PR: https://github.com/pelican-dev/plugins/pull/34
Author: @PalmarHealer
Created: 12/21/2025
Status: ❌ Closed

Base: main ← Head: palmarhealer/add-github-action

📝 Commits (2)

41a7e46 Add GitHub Actions workflow for creating draft releases with plugin zips and manifest
77b3cd9 Improve release workflow: validate plugin.json, add checksum to manifest, and ensure JSON integrity

📊 Changes

1 file changed (+160 additions, -0 deletions)

View changed files

➕ .github/workflows/release.yml (+160 -0)

📄 Description

This adds a Github Action that can be triggered manually that creates a .zip for each plugin. It also creates a manifest.json which contains the plugin.json, the download link and the checksum.

This would make it possible to add a marketplace to the panel and the manifest could be used to pull them together. The only drawback i could see to this is that there would have to be an release for the whole repo if a plugin gets an update

Summary by CodeRabbit

Chores
- Added an automated release workflow that packages each plugin into zip archives, generates a release manifest with version, download URLs and SHA256 checksums, validates plugin metadata, and creates a draft GitHub release with the zip assets and manifest. The workflow emits a plugins list and manifest as outputs and includes error handling for missing or invalid plugin metadata and archive files.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

_{🔄 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/pelican-dev/plugins/pull/34 **Author:** [@PalmarHealer](https://github.com/PalmarHealer) **Created:** 12/21/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `palmarhealer/add-github-action` --- ### 📝 Commits (2) - [`41a7e46`](https://github.com/pelican-dev/plugins/commit/41a7e464a0e382fbd126983a9298ca972f460ae4) Add GitHub Actions workflow for creating draft releases with plugin zips and manifest - [`77b3cd9`](https://github.com/pelican-dev/plugins/commit/77b3cd922ca1c95208da5e65bac9888214f172c9) Improve release workflow: validate `plugin.json`, add checksum to manifest, and ensure JSON integrity ### 📊 Changes **1 file changed** (+160 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `.github/workflows/release.yml` (+160 -0) </details> ### 📄 Description This adds a Github Action that can be triggered manually that creates a .zip for each plugin. It also creates a [manifest.json](https://github.com/user-attachments/files/24275741/manifest.json) which contains the plugin.json, the download link and the checksum. This would make it possible to add a marketplace to the panel and the manifest could be used to pull them together. The only drawback i could see to this is that there would have to be an release for the whole repo if a plugin gets an update  ## Summary by CodeRabbit * **Chores** * Added an automated release workflow that packages each plugin into zip archives, generates a release manifest with version, download URLs and SHA256 checksums, validates plugin metadata, and creates a draft GitHub release with the zip assets and manifest. The workflow emits a plugins list and manifest as outputs and includes error handling for missing or invalid plugin metadata and archive files. <sub>✏️ Tip: You can customize this high-level summary in your review settings.</sub>  --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>