You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Release 1.5.0 of the bailian-cli family. Bundles the new command groups landed since 1.4.2 (fine-tuning, deployment, datasets, Token Plan, auto-update) together with the composable-package refactor and a new sibling CLI (kscli).
New commands (user-facing)
bl finetune — model fine-tuning: create / list / get / watch / cancel jobs, training logs, checkpoints, export a checkpoint as a deployable model, query training capability. Types: sft, sft-lora, dpo, dpo-lora, cpt.
bl deploy — model deployment: create / list / get / update (rate limits) / scale / delete, list deployable models and plans.
bl dataset — datasets: upload / list / get / delete, plus validate to check a local .jsonl before uploading (ChatML / DPO / CPT).
bl token-plan — Token Plan management: list seats, add members, batch-assign seats, create per-seat API key.
Auto-update check — after a command runs, the CLI checks npm (throttled) and shows an Update available hint; a major stable-version gap self-updates. Skipped with --quiet / on bl update.
Architecture (internal)
bailian-cli split into composable packages:
bailian-cli-core # pure SDK
bailian-cli-runtime # NEW — CLI framework: createCli, registry, args, output, pipeline
bailian-cli-commands # NEW — shared command library
bailian-cli # bl — composes runtime + commands (behavior unchanged)
knowledge-studio-cli # NEW — kscli, lightweight RAG CLI on the same runtime
Commands declare usageArgs / exampleArgs (no bin prefix) so the runtime renders help per product. Release tooling builds/publishes runtime + commands alongside core + cli.
Version
bailian-cli, bailian-cli-core, bailian-cli-runtime, bailian-cli-commands release in lockstep → all bumped to 1.5.0 (from 1.4.2 / 1.4.0).
knowledge-studio-cli stays at 0.0.1 — it publishes from a separate workflow run and is not in the bailian-cli publish set.
Fixed
Console gateway commands surface a readable message on a non-string errorCode instead of [object Object].
Notes / follow-ups
Lockstep validation (tools/release/lib/validate.mjs) requires every package in the publish set to match core's version. The --knowledge publish path includes kscli, so its 0.0.1 would fail that check — decide before the first kscli publish whether kscli joins the 1.5.0 lockstep or the validation exempts it.
…CLIs
Decompose the monolithic `cli` package into three layers so multiple
products can be assembled from a shared base:
- bailian-cli-runtime: framework infra (createCli, registry, args,
output, pipeline, utils) — product-agnostic
- bailian-cli-commands: command library, grouped (base/knowledge/text/
media/memory/misc) so each product picks the sets it needs
- packages/cli (bl): full command set; packages/rag (rag): base +
knowledge only
Product identity (binName / clientName / npmPackage) is injected at the
createCli boundary and required there, with no per-consumer defaults.
…h presets
Commands no longer hardcode "bl" or their path — the runtime renders the
`<bin> <path>` prefix from each product's registry key, so shared commands
show `bl knowledge retrieve` / `rag retrieve` from one codebase. commands
package now exports only individual commands (no groups/catalog); bl and rag
each spell out their own path map. Also removes the unused export-schema command.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Release 1.5.0 of the
bailian-clifamily. Bundles the new command groups landed since 1.4.2 (fine-tuning, deployment, datasets, Token Plan, auto-update) together with the composable-package refactor and a new sibling CLI (kscli).New commands (user-facing)
bl finetune— model fine-tuning: create / list / get / watch / cancel jobs, training logs, checkpoints, export a checkpoint as a deployable model, query training capability. Types:sft,sft-lora,dpo,dpo-lora,cpt.bl deploy— model deployment: create / list / get / update (rate limits) / scale / delete, list deployable models and plans.bl dataset— datasets: upload / list / get / delete, plusvalidateto check a local.jsonlbefore uploading (ChatML / DPO / CPT).bl token-plan— Token Plan management: list seats, add members, batch-assign seats, create per-seat API key.Update availablehint; a major stable-version gap self-updates. Skipped with--quiet/ onbl update.Architecture (internal)
bailian-clisplit into composable packages:Commands declare
usageArgs/exampleArgs(no bin prefix) so the runtime renders help per product. Release tooling builds/publishesruntime+commandsalongsidecore+cli.Version
bailian-cli,bailian-cli-core,bailian-cli-runtime,bailian-cli-commandsrelease in lockstep → all bumped to 1.5.0 (from 1.4.2 / 1.4.0).knowledge-studio-clistays at0.0.1— it publishes from a separate workflow run and is not in thebailian-clipublish set.Fixed
errorCodeinstead of[object Object].Notes / follow-ups
tools/release/lib/validate.mjs) requires every package in the publish set to matchcore's version. The--knowledgepublish path includeskscli, so its0.0.1would fail that check — decide before the first kscli publish whether kscli joins the1.5.0lockstep or the validation exempts it.Test
pnpm install --frozen-lockfile✓ (lockfile unchanged)vp check+ tests🤖 Generated with Claude Code