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
The published crate is ~4 weeks behind master, so cargo install linear-cli still delivers a build in which #33, #34, #35 and #36 are all present — even though each is closed as completed on master.
crates.io latest
0.3.27, published 2026-06-26
v0.3.27 tag
commit c7c74464, tagged 2026-06-26
master HEAD
51af446a, 2026-07-24 — 18 commits ahead of the tag
Confirmation from a freshly installed binary
Installed from crates.io (linear-cli 0.3.27 (registry+https://github.com/rust-lang/crates.io-index)), today:
$ linear-cli relations add BF-551 BF-474 -r blocked-byError: HTTP 400 Bad Request: Variable "$type" got invalid value "blockedBy"; Value "blockedBy" does not exist in "IssueRelationType" enum. Did you mean the enum value "blocks"?
That is #36's exact symptom, reproduced on the current published version. blocks, related and duplicate all work — only blocked-by 400s, matching #36's description precisely.
The fix for it (d804df09, "fix: setup team persistence, pager on interactive cmds, blocked-by relations", merged as PR #37 on 2026-07-18) landed three weeks after0.3.27 was published, so it has never appeared in a release.
Unreleased on master
18 commits since the v0.3.27 tag, including the fixes that closed #33/#34/#35/#36:
332c4a4e — silence stderr noise for the hidden _complete command
Ask
Cut and publish 0.3.28 so these reach cargo install.
Two things that look like they'd block or confuse that:
Cargo.toml on master still reads version = "0.3.26" — below the published 0.3.27, so a publish from master as-is would be rejected as a duplicate/older version. Relatedly, v0.3.27 is tagged on c7c74464, which is not an ancestor of master (compare reports diverged, master ahead 18 / behind 1), so the last release doesn't appear to have been cut from master.
repository and homepage in Cargo.toml still point at https://github.com/Finesssee/linear-cli — the pre-rename owner. It redirects, so nothing is broken, but crates.io shows the stale URL on the crate page, which makes the canonical repo harder to find. Worth updating to nesszer/linear-cli in the same release.
Summary
The published crate is ~4 weeks behind
master, socargo install linear-clistill delivers a build in which #33, #34, #35 and #36 are all present — even though each is closed as completed onmaster.0.3.27, published 2026-06-26v0.3.27tagc7c74464, tagged 2026-06-26masterHEAD51af446a, 2026-07-24 — 18 commits ahead of the tagConfirmation from a freshly installed binary
Installed from crates.io (
linear-cli 0.3.27 (registry+https://github.com/rust-lang/crates.io-index)), today:That is #36's exact symptom, reproduced on the current published version.
blocks,relatedandduplicateall work — onlyblocked-by400s, matching #36's description precisely.The fix for it (
d804df09, "fix: setup team persistence, pager on interactive cmds, blocked-by relations", merged as PR #37 on 2026-07-18) landed three weeks after0.3.27was published, so it has never appeared in a release.Unreleased on master
18 commits since the
v0.3.27tag, including the fixes that closed #33/#34/#35/#36:d804df09/ PR fix: setup team persistence, interactive pager, blocked-by relations #37 — setup team persistence, pager on interactive commands,blocked-byrelations (closes Terminal output is disabled from some commands, and not all teams are returned #34, Configuring does not persist team settings #35, relations add --relation blocked-by returns HTTP 400 (advertised but unsupported; should map to inverse 'blocks') #36)df6f7b4a,8a3f0a52,721533b7,5723ece8/ PR fix(auth): enable real OS keyring backends for secure-storage #40 — real OS keyring backends for secure-storage (closes secure-storage uses mock keyring on macOS because apple-native is not enabled #33)03d2b5ca,306b3b7a/ PR fix(initiatives): paginate projects ininitiatives get#39 —initiatives getprojects pagination474f71b1— clippy fixes for rust-1.97332c4a4e— silence stderr noise for the hidden_completecommandAsk
Cut and publish
0.3.28so these reachcargo install.Two things that look like they'd block or confuse that:
Cargo.tomlonmasterstill readsversion = "0.3.26"— below the published0.3.27, so a publish frommasteras-is would be rejected as a duplicate/older version. Relatedly,v0.3.27is tagged onc7c74464, which is not an ancestor ofmaster(comparereportsdiverged, master ahead 18 / behind 1), so the last release doesn't appear to have been cut frommaster.repositoryandhomepageinCargo.tomlstill point athttps://github.com/Finesssee/linear-cli— the pre-rename owner. It redirects, so nothing is broken, but crates.io shows the stale URL on the crate page, which makes the canonical repo harder to find. Worth updating tonesszer/linear-cliin the same release.Happy to open a PR for either if that's useful.