[PR #485] [MERGED] Add plugin metadata generation #3334

Closed
opened 2026-07-15 02:02:27 -05:00 by GiteaMirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/mountain-loop/yaak/pull/485
Author: @gschier
Created: 6/29/2026
Status: Merged
Merged: 6/29/2026
Merged by: @gschier

Base: mainHead: codex/plugin-metadata


📝 Commits (1)

  • d754d22 Add plugin metadata generation

📊 Changes

8 files changed (+401 additions, -3 deletions)

View changed files

📝 crates-cli/yaak-cli/src/cli.rs (+4 -0)
📝 crates-cli/yaak-cli/src/commands/plugin.rs (+184 -2)
📝 crates-cli/yaak-cli/src/main.rs (+1 -0)
📝 package-lock.json (+18 -0)
packages/plugin-runtime/.node-version (+1 -0)
📝 packages/plugin-runtime/package.json (+1 -0)
packages/plugin-runtime/src/metadata.ts (+190 -0)
📝 scripts/vendor-node.cjs (+2 -1)

📄 Description

Adds plugin metadata generation to the Rust CLI so registry-facing API metadata is emitted alongside plugin bundles.

  • Adds a hidden yaak plugin metadata command to generate build/metadata.json from the bundled plugin export
  • Runs metadata generation after plugin build, after successful plugin dev rebuilds, and before plugin publish archives the build output
  • Moves the metadata bootstrapper into packages/plugin-runtime/src/metadata.ts, typed against PluginDefinition from @yaakapp/api
  • Captures plugin API surfaces including themes, template functions, auth/filter/importer, request actions, workspace/folder actions, websocket actions, and lifecycle hooks
  • Adds packages/plugin-runtime/.node-version as the shared Node version source for scripts/vendor-node.cjs and the CLI metadata check
  • Keeps generated plugin npm scripts limited to build and dev

🔄 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/mountain-loop/yaak/pull/485 **Author:** [@gschier](https://github.com/gschier) **Created:** 6/29/2026 **Status:** ✅ Merged **Merged:** 6/29/2026 **Merged by:** [@gschier](https://github.com/gschier) **Base:** `main` ← **Head:** `codex/plugin-metadata` --- ### 📝 Commits (1) - [`d754d22`](https://github.com/mountain-loop/yaak/commit/d754d226294781551f9ce6a26e04ae5f7a75315e) Add plugin metadata generation ### 📊 Changes **8 files changed** (+401 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `crates-cli/yaak-cli/src/cli.rs` (+4 -0) 📝 `crates-cli/yaak-cli/src/commands/plugin.rs` (+184 -2) 📝 `crates-cli/yaak-cli/src/main.rs` (+1 -0) 📝 `package-lock.json` (+18 -0) ➕ `packages/plugin-runtime/.node-version` (+1 -0) 📝 `packages/plugin-runtime/package.json` (+1 -0) ➕ `packages/plugin-runtime/src/metadata.ts` (+190 -0) 📝 `scripts/vendor-node.cjs` (+2 -1) </details> ### 📄 Description Adds plugin metadata generation to the Rust CLI so registry-facing API metadata is emitted alongside plugin bundles. - Adds a hidden `yaak plugin metadata` command to generate `build/metadata.json` from the bundled plugin export - Runs metadata generation after `plugin build`, after successful `plugin dev` rebuilds, and before `plugin publish` archives the build output - Moves the metadata bootstrapper into `packages/plugin-runtime/src/metadata.ts`, typed against `PluginDefinition` from `@yaakapp/api` - Captures plugin API surfaces including themes, template functions, auth/filter/importer, request actions, workspace/folder actions, websocket actions, and lifecycle hooks - Adds `packages/plugin-runtime/.node-version` as the shared Node version source for `scripts/vendor-node.cjs` and the CLI metadata check - Keeps generated plugin npm scripts limited to `build` and `dev` --- <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-07-15 02:02:27 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/yaak#3334