hex-publish-module

Publishes a SpacetimeDB WASM module and refreshes bindings, schema version, builds, and services.

4|Updated Mar 16, 2026

Search Tags:#automation #deployment #build #publish #bindings #schema-version #spacetimedb

Ready to run

npx skills add https://github.com/gaberger/hex --skill hex-publish-module

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: hex-publish-module
Source: https://github.com/gaberger/hex/tree/main/.claude/skills/hex-publish-module
Command: npx skills add https://github.com/gaberger/hex --skill hex-publish-module

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end lifecycle of publishing a SpacetimeDB WASM module, including regenerating bindings, bumping the schema version, rebuilding, and restarting services, reducing manual steps and drift.

Core Features & Use Cases

End-to-end module publish: publish the module from its directory.
Bindings regeneration: regenerate TypeScript bindings to reflect the new module schema.
Schema management: bump SCHEMA_VERSION to invalidate and refresh client state.
Build and restart: rebuild hex-nexus and hex-cli and restart nexus to apply changes.
Re-registration: re-register the project and agent to restore deployment context after changes.

Quick Start

Publish the updated SpacetimeDB module from its module directory and follow the pipeline to regenerate bindings, bump the schema, rebuild, and restart services.

Frequently Asked Questions about hex-publish-module

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate SpacetimeDB module deployment and regenerate TypeScript bindings?▼

To automate SpacetimeDB module deployment, this Skill publishes the WASM module, regenerates TypeScript bindings, bumps the schema version, rebuilds binaries, and restarts services in a verified sequence to ensure coherent deployment and reduce manual drift.

What is the end-to-end process for publishing a SpacetimeDB WASM module?▼

The end-to-end publishing process for a SpacetimeDB WASM module involves publishing from the module directory, regenerating bindings, bumping SCHEMA_VERSION, rebuilding binaries, and restarting services while coordinating each step for recoverability upon failure.

How do I bump the schema version for SpacetimeDB to refresh client state?▼

To refresh client state, the publish workflow bumps the SCHEMA_VERSION, which invalidates outdated client state and ensures the regenerated TypeScript bindings reflect the newly published SpacetimeDB module schema.

Does the SpacetimeDB publish workflow handle rebuilding binaries and restarting services?▼

Yes, the SpacetimeDB publish workflow handles rebuilding hex-nexus and hex-cli binaries, restarting the nexus service to apply changes, and re-registering the project and agent to restore the full deployment context.

What happens if a SpacetimeDB module deployment step fails midway?▼

If a deployment step fails midway, the workflow verifies and coordinates each action to ensure coherent deployment and provide recoverability, preventing partial updates from breaking the SpacetimeDB module lifecycle.