chore: publish-prep for v0.2.0#229
Conversation
- xtask: move uselesskey-token-spec to leaf section in PUBLISH_CRATES - README: fix version refs 0.3 → 0.2 - release.yml: align with ci.yml (timeout 75m, install-action, toolchain diag)
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughA comprehensive 0.1.0 to 0.2.0 version bump across the workspace. Updates CI workflows (timeout, tool installation), version dependencies in 60+ crate manifests, synchronizes documentation across multiple files, enhances xtask planning logic with new test execution flags, and updates factory extension trait signatures. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request prepares the repository for a new minor release, Highlights
Changelog
Ignored Files
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request prepares the repository for the v0.2.0 release by bumping crate versions, updating the changelog and other documentation, and adapting tests for dependency changes. The changes are largely correct and align with the release goals. I've identified one minor issue in the changelog regarding a likely typo in the release date.
|
|
||
| ## [Unreleased] | ||
|
|
||
| ## [0.2.0] - 2026-03-06 |
Match the main job timeout. This is a safety net for release-prep PRs that touch many files and trigger broad CI steps.
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@CHANGELOG.md`:
- Line 159: The CHANGELOG line "50-crate workspace organised into four layers"
is inconsistent with the actual Cargo.toml workspace membership (which includes
crates/uselesskey-token-spec and excludes fuzz); update the CHANGELOG to match
the real workspace by either (A) adding crates/uselesskey-token-spec to the
listed workspace members and removing fuzz from the count and any tables, or (B)
rewording the section to be a repository architecture overview (remove the
explicit "50-crate workspace" count and any workspace-specific membership
claims). Make the change where the phrase "50-crate workspace organised into
four layers" appears and ensure the tables below reflect the chosen option so
the text and Cargo.toml members (e.g., crates/uselesskey-token-spec, fuzz) are
consistent.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: 427545f2-46a4-46ff-9452-6fa637bdadfb
⛔ Files ignored due to path filters (1)
Cargo.lockis excluded by!**/*.lock
📒 Files selected for processing (69)
.github/workflows/ci.yml.github/workflows/release.ymlAGENTS.mdCHANGELOG.mdCLAUDE.mdCONTRIBUTING.mdCargo.tomlGEMINI.mdREADME.mdcrates/uselesskey-aws-lc-rs/Cargo.tomlcrates/uselesskey-aws-lc-rs/README.mdcrates/uselesskey-bdd-steps/Cargo.tomlcrates/uselesskey-core-base62/Cargo.tomlcrates/uselesskey-core-cache/Cargo.tomlcrates/uselesskey-core-factory/Cargo.tomlcrates/uselesskey-core-hash/Cargo.tomlcrates/uselesskey-core-hmac-spec/Cargo.tomlcrates/uselesskey-core-id/Cargo.tomlcrates/uselesskey-core-jwk-builder/Cargo.tomlcrates/uselesskey-core-jwk-shape/Cargo.tomlcrates/uselesskey-core-jwk/Cargo.tomlcrates/uselesskey-core-jwks-order/Cargo.tomlcrates/uselesskey-core-keypair-material/Cargo.tomlcrates/uselesskey-core-keypair/Cargo.tomlcrates/uselesskey-core-kid/Cargo.tomlcrates/uselesskey-core-negative-der/Cargo.tomlcrates/uselesskey-core-negative-pem/Cargo.tomlcrates/uselesskey-core-negative/Cargo.tomlcrates/uselesskey-core-rustls-pki/Cargo.tomlcrates/uselesskey-core-seed/Cargo.tomlcrates/uselesskey-core-sink/Cargo.tomlcrates/uselesskey-core-token-shape/Cargo.tomlcrates/uselesskey-core-token/Cargo.tomlcrates/uselesskey-core-x509-chain-negative/Cargo.tomlcrates/uselesskey-core-x509-derive/Cargo.tomlcrates/uselesskey-core-x509-negative/Cargo.tomlcrates/uselesskey-core-x509-spec/Cargo.tomlcrates/uselesskey-core-x509/Cargo.tomlcrates/uselesskey-core/Cargo.tomlcrates/uselesskey-ecdsa/Cargo.tomlcrates/uselesskey-ed25519/Cargo.tomlcrates/uselesskey-feature-grid/Cargo.tomlcrates/uselesskey-hmac/Cargo.tomlcrates/uselesskey-jsonwebtoken/Cargo.tomlcrates/uselesskey-jsonwebtoken/README.mdcrates/uselesskey-jwk/Cargo.tomlcrates/uselesskey-pgp/Cargo.tomlcrates/uselesskey-ring/Cargo.tomlcrates/uselesskey-ring/README.mdcrates/uselesskey-rsa/Cargo.tomlcrates/uselesskey-rustcrypto/Cargo.tomlcrates/uselesskey-rustcrypto/README.mdcrates/uselesskey-rustls/Cargo.tomlcrates/uselesskey-rustls/README.mdcrates/uselesskey-test-grid/Cargo.tomlcrates/uselesskey-token-spec/Cargo.tomlcrates/uselesskey-token/Cargo.tomlcrates/uselesskey-tonic/Cargo.tomlcrates/uselesskey-tonic/README.mdcrates/uselesskey-x509/Cargo.tomlcrates/uselesskey/Cargo.tomlcrates/uselesskey/README.mddocs/PUBLISHING.mddocs/release.mdtests/Cargo.tomltests/governance.rstests/msrv_check.rsxtask/src/main.rsxtask/src/plan.rs
| ### Architecture | ||
|
|
||
| 51-crate workspace organised into four layers: | ||
| 50-crate workspace organised into four layers: |
There was a problem hiding this comment.
Align the architecture count with the actual workspace membership.
Line 159 now says "50-crate workspace", but Cargo.toml:3-54 still includes crates/uselesskey-token-spec as a workspace member and excludes fuzz. The tables below do the opposite, so this section is still not describing the real workspace layout. Either add uselesskey-token-spec and stop counting fuzz as a workspace crate, or reword this as a repository architecture overview instead.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@CHANGELOG.md` at line 159, The CHANGELOG line "50-crate workspace organised
into four layers" is inconsistent with the actual Cargo.toml workspace
membership (which includes crates/uselesskey-token-spec and excludes fuzz);
update the CHANGELOG to match the real workspace by either (A) adding
crates/uselesskey-token-spec to the listed workspace members and removing fuzz
from the count and any tables, or (B) rewording the section to be a repository
architecture overview (remove the explicit "50-crate workspace" count and any
workspace-specific membership claims). Make the change where the phrase
"50-crate workspace organised into four layers" appears and ensure the tables
below reflect the chosen option so the text and Cargo.toml members (e.g.,
crates/uselesskey-token-spec, fuzz) are consistent.
Summary
toml1.0 API changesCHANGELOG.md,docs/release.md,docs/PUBLISHING.mduselesskey-token-specto leaf section inPUBLISH_CRATES, fix README version refs (0.3→0.2), alignrelease.ymlwithci.yml(timeout 75m, install-action, toolchain diag)Test plan
cargo xtask gate— 4/4 pass (fmt, check, clippy, test-compile)cargo test -p uselesskey-integration-tests --test governance --test msrv_check— 12/12 pass