helmor-bump-vendors
Helmor Bump Vendors automates the process of upgrading pinned versions of agent CLIs, SDKs, and supporting binaries—including Claude Code, Codex, Cursor SDK, and platform tools. It handles version sourcing, SHA256 computation for both arm64 and x64 architectures, enforces the Claude SDK↔CLI lockstep rule, and runs mandatory verification gates to ensure correctness before release.
Helmor Bump Vendors upgrades bundled agent CLIs and SDKs with cross-architecture SHA256 verification.
AI-generated summary based on this skill's SKILL.md
Install
dohooo/helmor/helmor-bump-vendors · repository language: TypeScript
git clone https://github.com/dohooo/helmor
cp -r helmor/.agents/skills/helmor-bump-vendors ~/.claude/skills/helmor-bump-vendorsFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How to upgrade helmor bundled agent versions?
Helmor Bump Vendors automates upgrading pinned versions of agent CLIs, SDKs, and binaries including Claude Code, Codex, and Cursor SDK. The tool sources the latest versions, computes SHA256 checksums for both arm64 and x64 architectures, enforces the Claude SDK↔CLI lockstep versioning constraint, and runs verification gates before release to ensure correctness.
What does helmor vendor version bump procedure include?
Helmor Bump Vendors' procedure encompasses version sourcing from npm dist-tags (latest, next, stable), SHA256 verification across architectures, updates to package.json and vendor-platform.ts, lockstep validation between Claude SDK and Code, breaking change detection in SDK exports and stdout event shapes, and dependency sweep validation gates for vendor bump releases.
How does helmor compute sha256 vendor binaries?
Helmor Bump Vendors computes SHA256 checksums for vendor binaries across both arm64 and x64 architectures as part of its verification workflow. These checksums are validated against bundled agents like kimi, gh, glab, cloudflared, node, and llama.cpp to ensure binary integrity before the vendor bump release is finalized.
What vendor tools does helmor upgrade?
Helmor Bump Vendors upgrades pinned versions of agent CLIs and SDKs including Claude Code, Codex, Cursor SDK, kimi, gh, glab, cloudflared, node, and llama.cpp. It maintains cross-architecture support for arm64 and x64, enforces the Claude SDK↔CLI lockstep rule, and detects breaking changes in SDK exports before release.
What is the helmor cli sdk lockstep rule?
Helmor Bump Vendors enforces a lockstep versioning constraint between Claude SDK and Code CLI, ensuring they remain synchronized during vendor bumps. This constraint is validated as part of the mandatory verification gates to prevent version mismatches that could cause breaking changes in SDK exports or stdout event shapes.
What verification gates does helmor run before release?
Helmor Bump Vendors runs mandatory verification gates including SHA256 checksum validation across arm64 and x64 architectures, breaking change detection in SDK exports and stdout event shapes, Claude SDK↔CLI lockstep rule enforcement, typecheck pipeline tests, and a full dependency sweep to ensure vendor bump correctness before release.
SKILL.md
rendered from the published skill — quoted content, verbatim
Helmor Bump Vendors
Standardized procedure for upgrading the third-party agent CLIs, SDKs, and helper binaries that Helmor pins and bundles. Goal: a correct, verified bump with no guesswork about where versions live, how to source each SHA256, or what to run before declaring it done.
The pin sites
Every bundled version is pinned in one (or both) of these files:
sidecar/package.json
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 3 files
.agents/skills/helmor-bump-vendors/SKILL.md
.agents/skills/helmor-bump-vendors/references/vendors.md
.agents/skills/helmor-bump-vendors/scripts/npm_vendor_sha.sh