Skip to content

release.md

Latest commit

 

History

History
179 lines (126 loc) · 6.52 KB

release.md

File metadata and controls

179 lines (126 loc) · 6.52 KB
Raw

Release Flow

This repository publishes in three different ways:

  • Claude / Codex / Copilot ship from the GitHub repository marketplace files.
  • OpenCode and the standalone terminal CLI ship as npm packages (@bbingz/polycli-opencode and @bbingz/polycli).
  • Library packages @bbingz/polycli-utils and @bbingz/polycli-timing ship on their own v1.x cadence.

Current Release State

As of 2026-07-15, the current public release is v0.6.31:

  • GitHub repo: https://github.com/bbingz/polycli
  • GitHub release: v0.6.31 — https://github.com/bbingz/polycli/releases/tag/v0.6.31 (publishedAt 2026-07-15T14:39:17Z; tag commit a70eb093bc7892e2f6b653ed29ca8bba5d66489b)
  • Release notes: English · 简体中文 · 日本語
  • Published npm packages:
    • @bbingz/polycli@0.6.31 (latest, registry time 2026-07-15T14:37:53.706Z, shasum 57d0f77811767c4310623af03f27af82375abae8)
    • @bbingz/polycli-utils@1.0.5 (latest, registry time 2026-07-15T14:37:22.557Z, shasum 99df508a6bffe601e79569927bedf4016d3d471f)
    • @bbingz/polycli-timing@1.0.2 (latest, registry time 2026-07-15T02:10:59.440Z, shasum bd305c872ecd50e0abef6b6bd4abefcc1240e15a)
    • @bbingz/polycli-opencode@0.6.31 (latest, registry time 2026-07-15T14:38:07.324Z, shasum 65c990f89df099bb0a1a95104a0a8400abb0f6ca)
  • @bbingz/polycli-runtime remains an internal/private package.

Verified release paths:

  • Claude: marketplace add/install from bbingz/polycli
  • Codex: marketplace add from bbingz/polycli, then install Polycli from TUI /plugins
  • Copilot: marketplace add/install from bbingz/polycli
  • OpenCode: @bbingz/polycli-opencode
  • Terminal CLI: npm install -g @bbingz/polycli
  • public utility packages: @bbingz/polycli-utils, @bbingz/polycli-timing

Note:

  • npm registry read-after-write may briefly lag immediately after publishing a new package version.
  • GitHub social preview uses docs/assets/social-preview.png; upload it from the repository settings UI when the preview needs refreshing.

Current Scope

Current runtime scope in-repo:

  • claude
  • copilot
  • opencode
  • pi
  • cmd
  • gemini
  • kimi
  • qwen
  • minimax
  • agy
  • grok

Current host scope:

  • Claude marketplace plugin
  • Codex marketplace plugin
  • Copilot marketplace plugin
  • OpenCode npm package
  • Terminal CLI npm package

Model selection behavior remains intentionally simple:

  • every provider uses the underlying CLI default model unless --model is explicitly passed through runtime options

v0.6.0 absorbed the four legacy provider plugins into the unified polycli host surface:

  • Kimi session continuation flags: --resume-last, --resume <uuid>, --fresh
  • Gemini approval and reasoning flags: --write, --effort low|medium|high
  • Claude Code lifecycle hooks and opt-in stop-time review gate
  • 12 provider guidance skills under the polycli: namespace
  • one generic polycli:polycli-provider-agent subagent
  • unified namespace UX: /polycli:<command> --provider <provider>

The four legacy provider repos are no longer migration targets. They remain reference-only history and should not be edited from this repository.

Pre-release

Run the full release checks from the repository root:

npm run release:check

release:check includes:

  • npm run validate:bundles, a read-only source-derived freshness gate that runs before any in-place build
  • npm test, which then rebuilds plugin bundles before running package, runtime, plugin, and release-script tests
  • npm run validate:fixtures
  • npm run check:fixture-freshness -- --strict
  • npm run validate:manifests
  • npm run validate:host-map
  • npm run validate:codex-adapter
  • npm run check:review-drift (self-skips unavailable CLIs and blocks only detected installed-CLI review-flag drift)
  • claude plugin validate for the marketplace and Claude host plugin manifests
  • dry-run or pack checks for OpenCode, terminal CLI, utils, and timing npm packages

Run the review hard-constraint drift watcher directly when diagnosing a release-gate failure or inspecting local provider compatibility:

npm run check:review-drift

Build a distributable OpenCode tarball:

npm run pack:opencode

The tarball is written to dist/.

GitHub marketplace release

Create or update the public repository:

gh repo create bbingz/polycli --public --source=. --remote=origin --push

For the next release once external publishing is approved, replace <version> with the host plugin release version:

git push origin main
git tag v<version>
git push origin v<version>
gh release create v<version> --title "v<version>" --notes-file docs/release-notes-v<version>.md

Consumers install from the repository:

claude plugin marketplace add bbingz/polycli
claude plugin install polycli@polycli-hosts

codex plugin marketplace add bbingz/polycli
# then open Codex TUI /plugins and install Polycli from polycli-hosts

copilot plugin marketplace add bbingz/polycli
copilot plugin install polycli-copilot@polycli-hosts

OpenCode npm release

Publish the package directory directly:

npm publish ./plugins/polycli-opencode --access public

Consumers install with:

opencode plugin @bbingz/polycli-opencode

If npm account policy requires interactive browser verification, complete the CLI auth challenge and then re-run the same npm publish command.

Terminal CLI npm release (@bbingz/polycli)

@bbingz/polycli is the PATH-callable wrapper around the bundled companion. It ships in lockstep with the host plugin version (validate:manifests enforces alignment).

Pre-publish sanity checks (already wired into release:check):

  • npm publish ./packages/polycli-terminal --dry-run --access public returns + @bbingz/polycli@<version> with no npm pkg fix warning.
  • npm pack ./packages/polycli-terminal --dry-run --json lists LICENSE, README.md, package.json, bin/polycli.mjs, and bin/polycli-companion.bundle.mjs.

Publish with:

npm publish ./packages/polycli-terminal --access public

Consumers install with:

npm install -g @bbingz/polycli
polycli health --json

The terminal package re-uses the same polycli-companion.bundle.mjs that every host adapter ships. Before publishing, validate:bundles independently renders the expected outputs from source without writing them and compares all five bundle copies plus generated terminal metadata byte-for-byte; npm run build:plugins is the only in-place writer.