tritonkit-release-package-governance

Aligns and validates TritonKit release versions across CLI, Homebrew, Web, CocoaPods, and skill packages.

1|Updated May 15, 2026
One-click install
npx skills add https://github.com/NeptuneKit/TritonKit --skill tritonkit-release-package-governance-neptunekit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tritonkit-release-package-governance
Source: https://github.com/NeptuneKit/TritonKit/tree/main/.agents/skills/tritonkit-release-package-governance
Command: npx skills add https://github.com/NeptuneKit/TritonKit --skill tritonkit-release-package-governance-neptunekit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Publishing a TritonKit release requires keeping many package surfaces (CLI binaries, Homebrew formula, Web manifests, CocoaPods spec, public skill bundle) aligned to the same tag version, and a missed surface or moved tag breaks consumers. ## Core Features & Use Cases - Version Alignment: Defines the release boundary covering CLI assets, Web package.json/package-lock.json, TritonKit.podspec, and the public skill tarball, while noting SwiftPM has no version field. - Validation Workflow: Prescribes ordered gates including verify-release-package-versions.sh, verify-release-automation.sh, pod lib lint, npm build, and skill package verification before publishing via release.sh. - Recovery Rules: Documents how to handle wrong tags, observation races in GitHub Releases, truncated asset downloads, and Homebrew validation without moving published tags. - Use Case: A maintainer preparing v1.2.0 runs the pre-check script, updates the podspec and Web manifests, runs all validation gates, publishes through release.sh, then verifies GitHub assets, Homebrew upgrade, and a real triton web smoke test. ## Quick Start Ask the agent to prepare and publish TritonKit release v1.2.0 with all package surfaces aligned and validated.

Frequently Asked Questions about tritonkit-release-package-governance

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

FAQPage Schema
How do I publish a TritonKit release with aligned package versions?▼

Pick the next tag, run verify-release-package-versions.sh to confirm current manifests fail, update TritonKit.podspec and Web package manifests, run all validation gates, then publish with release.sh v<version> --yes and verify GitHub assets and Homebrew.

Which package surfaces must match a TritonKit release tag?▼

CLI binary assets and triton version output, the bundled Web asset, the public skill bundle tarball, the TritonKit.podspec CocoaPods spec, and Web/package.json plus package-lock.json. SwiftPM has no version field; consumers resolve the Git tag.

Should I edit CLIBuildInfo.swift to set the release version?▼

No. CI writes TritonKitBuildInfo.cliVersion during release builds, stamping it from the v* tag. Manually editing Sources/TritonKitCLI/CLIBuildInfo.swift for a release version is explicitly prohibited.

What should I do if the wrong release tag was pushed?▼

If no GitHub Release exists yet, cancel only that superseded workflow, delete the local and remote tag, fix manifests on main, and publish the intended tag. Never move a published tag; if a Release exists, cut a new higher version instead.

Why does release asset checksum validation fail right after download?▼

A still-running gh release download can leave truncated .tar.gz files that produce false checksum mismatches. Wait for the download to exit successfully, then inspect asset sizes and run gzip -t before rewriting any published asset or checksum manifest.

Is this skill part of the public TritonKit skill bundle?▼

No. It is an internal maintainer workflow under .agents/skills/ and must not be packaged into TritonKit.skills/. Only the three public skills are distributed to external users.