Repository navigation
Release request: crates.io 0.3.27 predates the #33-#36 fixes (18 commits unreleased on master) #42
Description
Summary
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-by
Error: 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 after 0.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:
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_completecommand
Ask
Cut and publish 0.3.28 so these reach cargo 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.
Activity
Document linear-cli relations gotchas
Finesssee commentedon Jul 30, 2026
hey, thanks for the report. I been quite busy, I would love for u to open a PR for me. Many thanks!
Finesssee commentedon Sep 13, 2026
Status after #50 and #51: v0.3.28 is published on GitHub with the complete five-target asset matrix, and the CircleCI release-context wiring is fixed for future tags. crates.io remains at 0.3.27 because the CircleCI organization currently has no cargo-release-publisher context or CARGO_REGISTRY_TOKEN. Keep this issue open until the token is configured and a crate publication is verified.