Skip to content

Release request: crates.io 0.3.27 predates the #33-#36 fixes (18 commits unreleased on master) #42

Description

@rosskevin

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:

Ask

Cut and publish 0.3.28 so these reach cargo install.

Two things that look like they'd block or confuse that:

  1. 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.

  2. 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.

Happy to open a PR for either if that's useful.

Activity

  1. Finesssee commented on Jul 30, 2026

    @Finesssee
    Collaborator

    hey, thanks for the report. I been quite busy, I would love for u to open a PR for me. Many thanks!

  2. Finesssee commented on Sep 13, 2026

    @Finesssee
    Collaborator

    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.

  3. deleted a comment from tlq5l on Sep 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions