chore(release): pin install to v0.17.0

[muqsitnawaz]

What

Release pin for v0.17.0 / PR #33.

• install.sh default VERSION=v0.17.0
• EXPECTED_SHA256=4a323c0d18d14e3910f44a605887ee309d04014bc44f4ed07f7ae9c57c6a4183
• README install URLs

No CLI behavior change (binary already on main).

Run

$ grep -E "VERSION=|EXPECTED_SHA" install.sh
VERSION="${LINEAR_CLI_VERSION:-v0.17.0}"
EXPECTED_SHA256="${LINEAR_CLI_SHA256:-4a323c0d18d14e3910f44a605887ee309d04014bc44f4ed07f7ae9c57c6a4183}"

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[prix-cloud]

Code Reviewer

Verdict: Ready to merge

Build: N/A (no source-level build required — the linear binary is the released artifact, verified below)
Tests: 84/84 passed (0.021s)

Verification performed

Check	Result
SHA-256 of linear binary matches pinned EXPECTED_SHA256	✅ 4a323c0d... matches
Old v0.16.1 SHA-256 no longer matches current binary	✅ Confirmed mismatch (expected)
install.sh shell syntax	✅ Clean (bash -n)
linear binary is valid Python	✅ Clean (ast.parse)
Tests (all 84)	✅ Passed
README URLs use v0.17.0 tag	✅ Both URLs updated

What changed

• install.sh: VERSION default bumped from v0.16.1 → v0.17.0, EXPECTED_SHA256 updated to match the v0.17.0 release's binary
• README.md: Both install code blocks (install.sh pipe and raw binary curl) point to the v0.17.0 tag

No issues found

Clean release pin — no behavioral changes to the CLI, no env var additions (the existing LINEAR_CLI_VERSION/LINEAR_CLI_SHA256 override mechanism is unchanged), no stubs, no gaps. The SHA-256 was verified against the linear binary in-tree and the old value is confirmed stale.

---

Reviewed by Code Reviewer — actually ran the build and tests on this branch.