agent-hub-release

What problem does it solve? Releasing a GAIA sidecar agent requires coordinating PyInstaller binary freezes across four platforms, immutable uploads to the Agent Hub Worker, SHA-256 lock generation, and npm OIDC publishing — a multi-stage process with irreversible steps that is easy to get wrong without a documented procedure. ## Core Features & Use Cases - Release execution: Walks through version synchronization across the git tag, npm package.json, and gaia-agent.yaml, then the tag-triggered build, human approval gate, and atomic publish stages. - New agent onboarding: Explains how to scaffold a new sidecar agent by mirroring the email agent's packaging scripts, npm client, and release_agent_<id>.yml workflow, including npm trusted publisher registration. - Infrastructure verification: Lists the one-time maintainer setup (agent-publish environment, GAIA_HUB_TOKEN secret, hub URL vars) that must exist before the first release. - Use Case: A maintainer bumps the email agent to a new version, tags agent-pkg-email-v1.2.0 from main, and uses this Skill to navigate the freeze, publish-gate approval, fetch-verify, and npm publish stages without corrupting the immutable Hub catalog. ## Quick Start Ask the assistant to cut a new sidecar release for the email agent at a specific version, or to onboard a new agent under hub/agents/ with its own release workflow.