@kyaukyuai/linear-cli 2.11.0 → 2.12.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 CHANGED
@@ -2,6 +2,17 @@
2
2
 
3
3
  ## [Unreleased]
4
4
 
5
+ ## [2.12.0] - 2026-03-30
6
+
7
+ ### Added
8
+
9
+ - added schema-style metadata to `linear capabilities --json` so agents can inspect command arguments, input modes, output semantics, and exit codes without scraping docs
10
+ - added Automation Contract v5 coverage for `initiative list/view --json`, `project-update list --json`, and `initiative-update list --json`
11
+
12
+ ### Changed
13
+
14
+ - upgraded write timeout handling to reconcile against Linear after client-side confirmation timeouts, distinguishing `probably_succeeded`, `definitely_failed`, and `partial_success` outcomes for high-value write commands
15
+
5
16
  ## [2.11.0] - 2026-03-30
6
17
 
7
18
  ### Added
package/README.md CHANGED
@@ -88,7 +88,7 @@ deno task install
88
88
  compared to upstream, this fork adds and maintains capabilities aimed at automation-heavy workflows:
89
89
 
90
90
  - stable JSON contracts for the automation tier, with machine-readable failures for parser, validation, and runtime errors
91
- - a self-describing `linear capabilities --json` surface so agents can discover contract coverage and command traits without scraping docs
91
+ - a self-describing `linear capabilities --json` surface so agents can discover contract coverage, primary input schema, output semantics, and command traits without scraping docs
92
92
  - `--dry-run` previews for high-value write commands, including `issue start`, issue writes, and non-issue writes
93
93
  - stdin and pipeline support for high-value write paths
94
94
  - retry-safe semantics for relation add/delete, project label add/remove, notification read/archive, and structured partial-failure details
@@ -101,7 +101,8 @@ compared to upstream, this fork adds and maintains capabilities aimed at automat
101
101
  - workflow state commands for `list` and `view`
102
102
  - user commands for `list` and `view`
103
103
  - project label commands for `list` and `project label add/remove`
104
- - JSON output for scripting across issue, cycle, project, milestone, document, webhook, and notification commands
104
+ - initiative commands for `list` and `view`, plus project update and initiative update feeds
105
+ - JSON output for scripting across issue, cycle, project, milestone, initiative, document, webhook, notification, and update-feed commands
105
106
  - workspace-aware auth management with keyring migration and default workspace support
106
107
  - generated AI-agent skill docs, Claude plugin metadata, npm publishing, and Homebrew tap release plumbing
107
108
 
@@ -109,18 +110,20 @@ compared to upstream, this fork adds and maintains capabilities aimed at automat
109
110
 
110
111
  for bot and org-wide automation use cases, `linear-cli` defines a stable JSON contract for a focused automation tier.
111
112
 
112
- to discover the curated agent-facing command surface programmatically, use `linear capabilities --json`. it reports stable contract versions, automation-tier membership, and per-command support for `--json`, `--dry-run`, stdin, confirmation bypass, and idempotency category.
113
+ to discover the curated agent-facing command surface programmatically, use `linear capabilities --json`. it reports stable contract versions, automation-tier membership, and per-command support for `--json`, `--dry-run`, stdin, confirmation bypass, idempotency category, primary arguments and flags, and success/failure output semantics.
113
114
 
114
115
  - 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`
115
116
  - v2 additions: `project list/view --json`, `cycle list/view/current/next --json`, `milestone list/view --json`
116
117
  - v3 additions: `document list/view --json`, `webhook list/view --json`, `notification list/count --json`
118
+ - v4 additions: `team list/view --json`, `user list/view --json`, `workflow-state list/view --json`, `label list --json`, `project-label list --json`
119
+ - v5 additions: `initiative list/view --json`, `project-update list --json`, `initiative-update list --json`
117
120
  - out of scope: non-JSON terminal output, `linear api`, and other `--json` commands that are not listed above
118
121
 
119
122
  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 `--json` is present.
120
123
 
121
124
  for automation consumers, auth and authorization failures now use exit code `4`, free-plan or workspace-plan limit failures use exit code `5`, and client-side write confirmation timeouts use exit code `6`. other contract failures remain non-zero and currently use `1`. rate-limited responses remain on exit code `1`, but now include retry guidance and, when available, `error.details.rateLimit` metadata.
122
125
 
123
- high-value issue write commands also honor `LINEAR_WRITE_TIMEOUT_MS` and accept `--timeout-ms` for per-command overrides. timeout failures return a distinct machine-readable failure mode, `timeout_error`, with `error.details.failureMode = "timeout_waiting_for_confirmation"`.
126
+ high-value write commands honor `LINEAR_WRITE_TIMEOUT_MS` and accept `--timeout-ms` for per-command overrides. timeout failures return a distinct machine-readable failure mode, `timeout_error`, with `error.details.failureMode = "timeout_waiting_for_confirmation"`. when reconciliation runs after the timeout, `error.details.outcome` now distinguishes `definitely_failed`, `probably_succeeded`, and `partial_success` from the fallback `unknown` state. notification `read` and `archive` now use the same timeout contract as issue write commands.
124
127
 
125
128
  the same document also defines the shared preview contract for future `--dry-run` write commands. those commands are not all implemented yet, but the contract now fixes the expected `stdout`, `exit code`, and `--json --dry-run` envelope shape ahead of rollout.
126
129
 
@@ -23,7 +23,7 @@
23
23
  "hasInstallScript": true,
24
24
  "license": "MIT",
25
25
  "name": "@kyaukyuai/linear-cli",
26
- "version": "2.11.0"
26
+ "version": "2.12.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": "2.11.0"
545
+ "version": "2.12.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/v2.11.0"
3
+ "https://github.com/kyaukyuai/linear-cli/releases/download/v2.12.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": "2.11.0",
88
+ "version": "2.12.0",
89
89
  "volta": {
90
90
  "node": "18.14.1",
91
91
  "npm": "9.5.0"