[Finesssee]

Use the existing gh-release-publisher context and map its gh_token to GH_TOKEN. Keep crates.io publication explicit and opt-in via a separate crate-release workflow requiring a dedicated cargo-release-publisher context. The v0.3.28 tag run built all five targets and passed verify-release, but publish-release never started because the config referenced nonexistent linear-cli-release. The existing tag/release is intentionally not rewritten. Validation: circleci config validate, circleci config process, git diff --check.

Summary by CodeRabbit

• New Features

  • Added an optional crates.io publishing workflow, enabled with publish_crate=true.
  • Added automated checks to verify crate versions and package contents before publishing.
  • GitHub releases and crates.io publishing now use separate authentication contexts.

• Documentation

  • Updated release and CI guidance to explain the optional crates.io publishing process, required credentials, and workflow order.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 78b17627-773d-483c-b107-dc3250176b96

📥 Commits

Reviewing files that changed from the base of the PR and between ddcf35f and 4d6020b.

📒 Files selected for processing (4)

• .circleci/README.md
• .circleci/config.yml
• .github/CI.md
• CONTEXT.md

Included review availability: Your plan provides up to 2 included reviews per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

CircleCI release publishing now uses separate GitHub and crates.io credential contexts. GitHub releases remain enabled for tagged releases. Crate publication runs in a separate workflow only when publish_crate=true, after crate verification.

Changes

Release publishing

Layer / File(s)	Summary
Release pipeline and credential separation .circleci/config.yml	Adds the publish_crate parameter and a gated crate-release workflow. The workflow verifies the crate version and package before publishing. GitHub and crates.io use separate contexts.
Release documentation updates .circleci/README.md, .github/CI.md, CONTEXT.md	Documents the separate credential contexts and the optional publish_crate=true release path.

Priority: ➖ Normal

Estimated code review effort: 3 (Moderate) | ~20 minutes

Change: Bug fix

Sequence Diagram(s)

sequenceDiagram
  participant CircleCI
  participant GitHub
  participant crates_io
  CircleCI->>GitHub: Upload tagged release assets
  CircleCI->>CircleCI: Run verify-crate
  CircleCI->>crates_io: Publish when publish_crate=true

Loading

Merge Risk: ⚪ Minimal · up to 4d602

The release configuration and documentation consistently describe separate credential contexts and opt-in crate publishing. No concrete merge-blocking risk remains.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: updating CI release contexts to match the CircleCI configuration.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/circleci-publication-context

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}