@kyaukyuai/linear-cli 3.0.0 → 3.1.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +23 -0
- package/README.md +17 -4
- package/npm-shrinkwrap.json +2 -2
- package/package.json +2 -2
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,29 @@
|
|
|
2
2
|
|
|
3
3
|
## [Unreleased]
|
|
4
4
|
|
|
5
|
+
## [3.1.0] - 2026-04-05
|
|
6
|
+
|
|
7
|
+
### Added
|
|
8
|
+
|
|
9
|
+
- expanded Automation Contract v7 across remaining high-value write surfaces, including issue assignment, estimate, move, priority, notification read/archive, project create and project-label mutations, and webhook create/update/delete flows
|
|
10
|
+
- enriched `linear capabilities` with more parser-complete metadata such as aliases, repeatability, variadic inputs, defaults, canonical examples, resolution sources, and stronger machine-readable constraints
|
|
11
|
+
- added machine-readable surface classification to `linear capabilities`, distinguishing `stable`, `partial`, and `escape_hatch` runtime surfaces for agent callers
|
|
12
|
+
|
|
13
|
+
### Changed
|
|
14
|
+
|
|
15
|
+
- expanded downstream certification from a single generic suite into named startup-monitor, control-plane, diagnostics, compatibility-bridge, and timeout-recovery consumer paths so release gates match real agent-runtime usage more closely
|
|
16
|
+
|
|
17
|
+
## [3.0.1] - 2026-04-05
|
|
18
|
+
|
|
19
|
+
### Changed
|
|
20
|
+
|
|
21
|
+
- published a copy-pasteable v2-to-v3 migration cookbook and strengthened the v3 release guide around startup, diagnostics, and explicit compatibility-mode guidance
|
|
22
|
+
- expanded the v3 release gate to certify both the native startup/discovery path and the explicit compatibility path for diagnostics and human/debug inspection
|
|
23
|
+
|
|
24
|
+
### Fixed
|
|
25
|
+
|
|
26
|
+
- improved common v3 compatibility failures so runtime suggestions point callers to `--text`, `--compat v1`, or `--profile human-debug --interactive` instead of forcing migration guidance to live only in docs
|
|
27
|
+
|
|
5
28
|
## [3.0.0] - 2026-04-04
|
|
6
29
|
|
|
7
30
|
### Added
|
package/README.md
CHANGED
|
@@ -40,6 +40,7 @@ Treat `linear-cli` as a shell-native control plane for agents:
|
|
|
40
40
|
- refs can be normalized with `linear resolve ...`
|
|
41
41
|
- write previews use `--dry-run --json`
|
|
42
42
|
- write results expose `operation`, `receipt`, and structured `error.details`
|
|
43
|
+
- `linear capabilities` classifies commands as `stable`, `partial`, or `escape_hatch`
|
|
43
44
|
- human/debug behavior is explicit with `--text` and `--profile human-debug --interactive`
|
|
44
45
|
|
|
45
46
|
The practical default loop is:
|
|
@@ -68,6 +69,7 @@ Recommended docs:
|
|
|
68
69
|
- [Agent workflow guide](docs/agent-first.md)
|
|
69
70
|
- [Automation contracts](docs/json-contracts.md)
|
|
70
71
|
- [Agent-only v3 release guide](docs/agent-only-v3.md)
|
|
72
|
+
- [v2 to v3 migration cookbook](docs/v2-to-v3-migration-cookbook.md)
|
|
71
73
|
- [stdin and pipeline policy](docs/stdin-policy.md)
|
|
72
74
|
|
|
73
75
|
## migration from 2.x
|
|
@@ -80,7 +82,7 @@ If a downstream consumer still assumes the older mixed human/agent behavior, mig
|
|
|
80
82
|
4. add `--text` anywhere a maintainer still wants terminal-oriented output
|
|
81
83
|
5. add `--profile human-debug --interactive` anywhere a maintainer still wants prompts or pager-oriented debugging
|
|
82
84
|
|
|
83
|
-
The detailed release and migration guide lives in [docs/agent-only-v3.md](docs/agent-only-v3.md).
|
|
85
|
+
The detailed release and migration guide lives in [docs/agent-only-v3.md](docs/agent-only-v3.md). For copy-pasteable before/after fixes, use [docs/v2-to-v3-migration-cookbook.md](docs/v2-to-v3-migration-cookbook.md).
|
|
84
86
|
|
|
85
87
|
## human-debug demos
|
|
86
88
|
|
|
@@ -203,8 +205,9 @@ Use the docs in this order if you are building an agent integration:
|
|
|
203
205
|
1. [docs/agent-first.md](docs/agent-first.md) for the recommended discover/read/preview/apply/recover loop
|
|
204
206
|
2. [docs/json-contracts.md](docs/json-contracts.md) for stable JSON payloads, exit codes, timeout semantics, and dry-run envelopes
|
|
205
207
|
3. [docs/agent-only-v3.md](docs/agent-only-v3.md) for the `v3.0.0` release contract and downstream migration checklist
|
|
206
|
-
4. [docs/
|
|
207
|
-
5. [
|
|
208
|
+
4. [docs/v2-to-v3-migration-cookbook.md](docs/v2-to-v3-migration-cookbook.md) for consumer-facing before/after upgrade examples
|
|
209
|
+
5. [docs/stdin-policy.md](docs/stdin-policy.md) for pipeline and file-input conventions
|
|
210
|
+
6. [`linear capabilities`](#automation-contract) for machine-readable command metadata at runtime
|
|
208
211
|
|
|
209
212
|
## automation contract
|
|
210
213
|
|
|
@@ -212,6 +215,8 @@ for bot and org-wide automation use cases, `linear-cli` defines a stable machine
|
|
|
212
215
|
|
|
213
216
|
to discover the curated agent-facing command surface programmatically, use `linear capabilities`. the default shape now returns the richer v2 schema metadata for agent-native startup. when an older consumer still expects the trimmed legacy shape, pin it explicitly with `linear capabilities --compat v1`.
|
|
214
217
|
|
|
218
|
+
the default capabilities shape now carries parser-oriented metadata for representative commands, including repeatable/variadic inputs, deprecated aliases, default values, composition constraints, and concrete resolution sources such as env vars, config keys, git branch context, jj trailers, and implicit stdin fallbacks.
|
|
219
|
+
|
|
215
220
|
`agent-safe` is now the default execution profile for agent-controlled runs. it disables pager-by-default behavior, extends the built-in write timeout to `45000ms` unless `--timeout-ms` or `LINEAR_WRITE_TIMEOUT_MS` is set, and keeps destructive confirmation bypass explicit with `--yes`. use `--profile human-debug` when a maintainer explicitly wants prompt-driven or pager-oriented debugging behavior.
|
|
216
221
|
|
|
217
222
|
non-goals:
|
|
@@ -220,13 +225,21 @@ non-goals:
|
|
|
220
225
|
- it does not auto-confirm destructive actions
|
|
221
226
|
- it does not replace explicit human/debug prompt flows; callers should pass flags, stdin, file inputs, or opt into `--profile human-debug --interactive`
|
|
222
227
|
|
|
228
|
+
runtime surface classes:
|
|
229
|
+
|
|
230
|
+
- `stable`: startup-contract or automation-contract surface. safe for primary agent runtime paths.
|
|
231
|
+
- `partial`: agent-usable surface with shared dry-run or machine-readable traits, but not a full stable contract. pin explicit flags and avoid assuming long-term shape stability.
|
|
232
|
+
- `escape_hatch`: intentionally raw or human/debug-only path, such as `linear api`, `--text`, or `--profile human-debug --interactive`.
|
|
233
|
+
|
|
223
234
|
- v1 in scope: `issue list/view/create/update --json`, `issue relation add/delete/list --json`, `issue comment add --json`, `team members --json`, `issue parent/children/create-batch --json`
|
|
224
235
|
- v2 additions: `project list/view --json`, `cycle list/view/current/next --json`, `milestone list/view --json`
|
|
225
236
|
- v3 additions: `document list/view --json`, `webhook list/view --json`, `notification list/count --json`
|
|
226
237
|
- v4 additions: `team list/view --json`, `user list/view --json`, `workflow-state list/view --json`, `label list --json`, `project-label list --json`
|
|
227
238
|
- v5 additions: `initiative list/view --json`, `project-update list --json`, `initiative-update list --json`
|
|
228
239
|
- v6 additions: `resolve issue/team/workflow-state/user/label --json`
|
|
229
|
-
-
|
|
240
|
+
- v7 additions: `issue assign/estimate/move/priority --json`, `notification read/archive --json`, `project create --json`, `project label add/remove --json`, `webhook create/update/delete --json`
|
|
241
|
+
- partial surfaces today include high-value dry-run adopters that do not yet expose a stable apply contract, such as `document create/update/delete`, `milestone create/update/delete`, `project update/delete`, and `issue start`
|
|
242
|
+
- escape-hatch only surfaces include non-JSON terminal flows, `linear api`, and explicit human/debug output paths
|
|
230
243
|
|
|
231
244
|
the contract fixes top-level success payload shapes and requires machine-readable failure payloads for the automation tier. see [docs/json-contracts.md](docs/json-contracts.md) for the full contract, compatibility rules, and example payloads. that guarantee also covers parser and argument validation failures when the command is in machine-readable mode, whether that is the default or was requested explicitly with `--json`.
|
|
232
245
|
|
package/npm-shrinkwrap.json
CHANGED
|
@@ -23,7 +23,7 @@
|
|
|
23
23
|
"hasInstallScript": true,
|
|
24
24
|
"license": "MIT",
|
|
25
25
|
"name": "@kyaukyuai/linear-cli",
|
|
26
|
-
"version": "3.
|
|
26
|
+
"version": "3.1.0"
|
|
27
27
|
},
|
|
28
28
|
"node_modules/@isaacs/cliui": {
|
|
29
29
|
"engines": {
|
|
@@ -542,5 +542,5 @@
|
|
|
542
542
|
}
|
|
543
543
|
},
|
|
544
544
|
"requires": true,
|
|
545
|
-
"version": "3.
|
|
545
|
+
"version": "3.1.0"
|
|
546
546
|
}
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"artifactDownloadUrls": [
|
|
3
|
-
"https://github.com/kyaukyuai/linear-cli/releases/download/v3.
|
|
3
|
+
"https://github.com/kyaukyuai/linear-cli/releases/download/v3.1.0"
|
|
4
4
|
],
|
|
5
5
|
"bin": {
|
|
6
6
|
"linear": "run-linear.js"
|
|
@@ -85,7 +85,7 @@
|
|
|
85
85
|
"zipExt": ".tar.xz"
|
|
86
86
|
}
|
|
87
87
|
},
|
|
88
|
-
"version": "3.
|
|
88
|
+
"version": "3.1.0",
|
|
89
89
|
"volta": {
|
|
90
90
|
"node": "18.14.1",
|
|
91
91
|
"npm": "9.5.0"
|