Skip to content

Prepare spiceai plugin and automate marketplace distribution - #27

Merged
lukekim merged 2 commits into
trunkfrom
codex/spiceai-marketplace-publishing
Sep 30, 2026
Merged

lukekim merged 2 commits into
trunkfrom
codex/spiceai-marketplace-publishing

Conversation

@lukekim

@lukekim lukekim commented Sep 30, 2026

Copy link
Copy Markdown
Contributor

The plugin currently uses inconsistent client names, exposes a maintainer skill, and only uploads a ZIP on GitHub release publication. This change prepares spiceai for distribution through Claude, OpenAI, GitHub Copilot, and Grok.

  • Standardize the plugin namespace as spiceai and use short skill names aligned with the CLI/API surfaces, such as $spiceai:sql and /spiceai:cloud. Add an SDK skill for the six official language clients.
  • Remove improve-skills from public sources and exclude private maintenance files, eval tooling, credentials, and local caches from packages. The local maintainer copy remains outside version control.
  • Make runtime installation a user-managed prerequisite in setup and cookbook guidance, and require an installed runtime before launch.
  • Add Copilot marketplace metadata, bundled OpenAI listing assets, the declared MIT license, and catalogs that install from their own checkout.
  • Add PR validation and reproducible ZIP/tar release builds with checksums, catalog entries pinned to the release commit, and submission instructions. Tag pushes create draft GitHub releases; publication and manual reruns update assets while preserving authored notes.

Validation:

  • make check test-distribution release-preview — passed, including 13 distribution tests.
  • actionlint, shellcheck for packaging/version scripts, ruff, and git diff --check — passed.
  • Claude manifest/catalog validation and five setup response scenarios passed during preparation.

The namespace and skill renames require callers to update existing invocations. The plugin remains aligned with runtime v2.3.2. The existing published tag is unchanged; release automation applies to a future version/tag containing these changes and requires a clean checkout at that matching tag. Marketplace scans, portal publication, and external catalog PRs remain separate steps documented in docs/publishing.md. This does not rewrite historical commits or old release packages.

@lukekim lukekim self-assigned this Sep 30, 2026
@lukekim
lukekim merged commit 526f542 into trunk Sep 30, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant