From 18a1393bcba8b38b92284a8394354b900d10cd63 Mon Sep 17 00:00:00 2001 From: ScriptedAlchemy Date: Mon, 31 Aug 2026 22:43:28 +0000 Subject: [PATCH] chore(rsc-runtime): drop the react-server-components keyword The published manifest contradicted itself: #89 rewrote the description to say the package is a React-element result DSL and explicitly not an RSC renderer, while the keywords array kept claiming react-server-components. Keeps the honest keywords (agent-bundle, mcp); the package name is out of scope here. --- .changeset/rsc-runtime-drop-rsc-keyword.md | 12 ++++++++++++ packages/rsc-runtime/package.json | 3 +-- 2 files changed, 13 insertions(+), 2 deletions(-) create mode 100644 .changeset/rsc-runtime-drop-rsc-keyword.md diff --git a/.changeset/rsc-runtime-drop-rsc-keyword.md b/.changeset/rsc-runtime-drop-rsc-keyword.md new file mode 100644 index 000000000..2ef170856 --- /dev/null +++ b/.changeset/rsc-runtime-drop-rsc-keyword.md @@ -0,0 +1,12 @@ +--- +"@agent-bundle/rsc-runtime": patch +--- + +Published-metadata fix: the `react-server-components` keyword is removed from +`packages/rsc-runtime/package.json`. #89 rewrote the `description` in that same +file to state that the package is a React-element result DSL rather than a +React Server Components renderer, but left the keyword asserting the opposite, +so the npm manifest contradicted itself and the registry surfaced the package +against RSC-renderer searches it cannot serve. The remaining keywords — +`agent-bundle` and `mcp` — describe what the package actually is. No runtime +code, export surface, or package name changes; the name is tracked separately. diff --git a/packages/rsc-runtime/package.json b/packages/rsc-runtime/package.json index 76c654d46..5405e3371 100644 --- a/packages/rsc-runtime/package.json +++ b/packages/rsc-runtime/package.json @@ -5,8 +5,7 @@ "license": "MIT", "keywords": [ "agent-bundle", - "mcp", - "react-server-components" + "mcp" ], "homepage": "https://github.com/ScriptedAlchemy/agent-bundle#readme", "bugs": {