@kyaukyuai/linear-cli 2.8.1 → 2.9.0

package/CHANGELOG.md

@@ -2,6 +2,33 @@
 
 ## [Unreleased]
 
+## [2.9.0] - 2026-03-28
+
+### Added
+
+- added stdin / pipeline support to high-value issue write commands and documented the stdin policy for automation use
+- added retry-safe relation semantics so repeated `issue relation add/delete` operations can return no-op success instead of failing
+- added `--no-pager` compatibility support to `issue create`
+
+### Changed
+
+- standardized confirmation bypass flags on destructive commands around `--yes`, while keeping legacy aliases for compatibility
+- expanded agent-focused `--help` examples across automation-tier and major write commands
+
+### Fixed
+
+- improved `-d/--description` parse failures to recommend `--description-file` or stdin for markdown content, and documented the same guidance in help and README
+
+## [2.8.2] - 2026-03-24
+
+### Added
+
+- added rate-limit retry guidance and `error.details.rateLimit` metadata for automation consumers when issue creation hits API throttling
+
+### Changed
+
+- distinguished plan-limit failures from generic automation errors with exit code `5` and clearer upgrade/archive guidance
+
 ## [2.8.1] - 2026-03-24
 
 ### Added

package/README.md

@@ -110,8 +110,20 @@ for bot and org-wide automation use cases, `linear-cli` defines a stable JSON co
 
 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.
 
+for automation consumers, auth and authorization failures now use exit code `4`, while free-plan or workspace-plan limit failures use exit code `5`. 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.
+
 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.
 
+destructive commands use `--yes` as the canonical confirmation-bypass flag. legacy `--force` and `--confirm` flags are still accepted where older workflows already depended on them.
+
+for retry behavior, prefer treating write commands in three buckets:
+
+- retry-safe set-style writes: `issue update` without `--comment`, plus relation add/delete
+- non-idempotent writes: `issue create`, `issue comment add`, and `issue update --comment`
+- resumable but non-idempotent batch writes: `issue create-batch`, which reports `error.details.createdIdentifiers` and `failedStep` on partial failure
+
+For stdin and pipeline behavior, see [docs/stdin-policy.md](docs/stdin-policy.md).
+
 ## differences from upstream
 
 this fork is intentionally diverging from upstream in a few ways:
@@ -182,12 +194,14 @@ linear issue start     # create/switch to issue branch and mark as started
 linear issue start ENG-123 --dry-run  # preview the branch and target state
 linear issue create    # create a new issue (interactive prompts)
 linear issue create -t "title" -d "description"  # create with flags
+cat description.md | linear issue create -t "title" --team ENG  # read description from stdin
 linear issue create -t "title" --team ENG --json  # emit machine-readable created issue data
 linear issue create -t "title" --team ENG --dry-run --json  # preview the created issue payload
 linear issue create-batch --file ./issue-batch.json --json  # create a parent issue and child issues from JSON
 linear issue create-batch --file ./issue-batch.json --dry-run --json  # preview a batch without creating issues
 linear issue create --project "My Project" --milestone "Phase 1"  # create with milestone
 linear issue update    # update an issue (interactive prompts)
+cat description.md | linear issue update ENG-123 --state started  # read description from stdin
 linear issue update ENG-123 --due-date 2026-03-31  # set an issue due date
 linear issue update ENG-123 --clear-due-date       # clear an issue due date
 linear issue update ENG-123 --assignee self --json  # emit machine-readable updated issue data
@@ -198,6 +212,7 @@ linear issue delete    # delete an issue
 linear issue comment list          # list comments on current issue
 linear issue comment add           # add a comment to current issue
 linear issue comment add ENG-123 "follow-up"  # add a comment with positional body
+printf "follow-up\n" | linear issue comment add ENG-123  # read comment body from stdin
 linear issue comment add -p <id>   # reply to a specific comment
 linear issue comment add ENG-123 --body "follow-up" --json  # emit created comment data
 linear issue comment add ENG-123 --body "follow-up" --dry-run --json  # preview comment creation
@@ -207,11 +222,14 @@ linear issue relation delete ENG-123 blocked-by ENG-100 --json  # emit machine-r
 linear issue relation delete ENG-123 blocked-by ENG-100 --dry-run --json  # preview relation deletion
 linear issue relation list ENG-123 --json  # emit dependency graph for an issue
 linear issue comment update <id>   # update a comment
+printf "reworded comment\n" | linear issue comment update <id>  # read updated body from stdin
 linear issue commits               # show all commits for an issue (jj only)
 linear issue parent ENG-123 --json    # emit the parent issue, or null when absent
 linear issue children ENG-123 --json  # emit child issues for decomposition workflows
 ```
 
+For short inline text, `-d/--description` is fine. For Markdown content, prefer `--description-file <path>` or pipe content on stdin to avoid shell escaping issues.
+
 `issue create-batch` expects a JSON file shaped like:
 
 ```json
@@ -284,7 +302,7 @@ linear milestone update <milestoneId> --name "New Name" --dry-run           # pr
 linear m update <milestoneId> --target-date "2026-04-15"  # update target date
 linear milestone delete <milestoneId>           # delete a milestone
 linear milestone delete <milestoneId> --dry-run                                # preview a milestone delete
-linear m delete <milestoneId> --force           # delete without confirmation
+linear m delete <milestoneId> --yes             # delete without confirmation
 ```
 
 ### document commands

package/npm-shrinkwrap.json

@@ -23,7 +23,7 @@
       "hasInstallScript": true,
       "license": "MIT",
       "name": "@kyaukyuai/linear-cli",
-      "version": "2.8.1"
+      "version": "2.9.0"
     },
     "node_modules/@isaacs/cliui": {
       "engines": {
@@ -542,5 +542,5 @@
     }
   },
   "requires": true,
-  "version": "2.8.1"
+  "version": "2.9.0"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "artifactDownloadUrls": [
-    "https://github.com/kyaukyuai/linear-cli/releases/download/v2.8.1"
+    "https://github.com/kyaukyuai/linear-cli/releases/download/v2.9.0"
   ],
   "bin": {
     "linear": "run-linear.js"
@@ -85,7 +85,7 @@
       "zipExt": ".tar.xz"
     }
   },
-  "version": "2.8.1",
+  "version": "2.9.0",
   "volta": {
     "node": "18.14.1",
     "npm": "9.5.0"