Skip to content

chore: prep 0.5.1 release#317

Merged
EffortlessSteven merged 1 commit into
mainfrom
chore/release-0.5.1
Mar 28, 2026
Merged

chore: prep 0.5.1 release#317
EffortlessSteven merged 1 commit into
mainfrom
chore/release-0.5.1

Conversation

@EffortlessSteven

@EffortlessSteven EffortlessSteven commented Mar 28, 2026

Copy link
Copy Markdown
Member

Summary

  • bump workspace crate versions and release-facing dependency snippets to 0.5.1
  • add the 0.5.1 changelog entry and mark the X.509 negative-wave follow-up complete
  • validate the release prep path with publish-preflight, publish-check, and gate

Validation

  • cargo xtask publish-preflight
  • cargo xtask publish-check
  • cargo xtask gate --check

@gemini-code-assist

gemini-code-assist Bot commented Mar 28, 2026

Copy link
Copy Markdown

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

@coderabbitai

coderabbitai Bot commented Mar 28, 2026 •
edited
Loading

Copy link
Copy Markdown

Caution

Review failed

Pull request was closed or merged during review

Summary by CodeRabbit

  • Bug Fixes

    • Fixed RustCrypto/HMAC compatibility issues in adapters and fuzz targets.

  • Chores

    • Released v0.5.1 with X.509 chain negative fixtures (not-yet-valid certificates and intermediate CA path validation failures).
    • Updated dependencies: toml 1.1.0, insta 1.47.0, sha2 0.11.0.
    • Bumped all workspace crate versions to align with release.

Walkthrough

This PR implements a coordinated version release from 0.5.0 to 0.5.1 across the entire workspace, updating package versions in 50+ Cargo.toml manifests, CHANGELOG with release notes dated 2026-03-27, documentation examples, workflow dispatch inputs, and roadmap files to mark v0.5.1 as shipped while planning v0.5.2.

Changes

Cohort / File(s) Summary
Workflow & Configuration
.github/workflows/publish-retry.yml		 Updated workflow dispatch input example tag from v0.5.0 to v0.5.1.
Release Documentation
CHANGELOG.md, docs/explanation/roadmap.md, docs/explanation/roadmap-followups-0251.md		 Added v0.5.1 release entry (dated 2026-03-27) documenting X.509 chain negatives, dependency refreshes, and RustCrypto/HMAC fixes; marked v0.5.1 complete and planned v0.5.2 follow-ups.
Workspace Root & Facade
Cargo.toml, README.md, crates/uselesskey/Cargo.toml, crates/uselesskey/README.md, crates/uselesskey/src/lib.rs		 Updated workspace and main crate versions to 0.5.1; synchronized all internal dependency versions; refreshed README dependency snippets across feature combinations.
Core Infrastructure Crates
crates/uselesskey-core-{base62,cache,factory,hash,hmac-spec,id,keypair-material,keypair,kid,seed,sink,token-shape,token,x509-chain-negative,x509-derive,x509-negative,x509-spec,x509}/Cargo.toml		 Bumped package versions to 0.5.1 and aligned intra-workspace dependency versions; preserved local path references and feature flags.
Key-Type & Builder Crates
crates/uselesskey-core-{jwk-builder,jwk-shape,jwk,jwks-order,negative-der,negative-pem,negative,rustls-pki}/Cargo.toml, crates/uselesskey-{rsa,ecdsa,ed25519,hmac,jwk,pgp,x509}/Cargo.toml		 Updated package and dependency versions to 0.5.1; kept optional/path configuration intact across key-type implementations.
Adapter & Specialized Crates
crates/uselesskey-{ring,rustcrypto,rustls,jsonwebtoken,jose-openid,pgp-native,tonic,aws-lc-rs,bdd-steps,feature-grid,test-grid,token-spec}/Cargo.toml		 Bumped versions to 0.5.1 for adapters and test utilities; synchronized optional key-type and core dependencies.
Adapter & Crate Documentation
crates/uselesskey-{ring,rustcrypto,rustls,jsonwebtoken,aws-lc-rs,tonic}/README.md, docs/how-to/choose-features.md, docs/metadata/workspace-docs.json		 Updated version references in Cargo.toml examples and dependency snippets from 0.5.0 to 0.5.1.
Test Suite
tests/Cargo.toml		 Updated all test dependency versions to 0.5.1 for core, key-type, adapter, and facade crates.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~8 minutes

Possibly related PRs

  • EffortlessMetrics/uselesskey#229: Related coordinated workspace release preparation performing synchronized Cargo.toml package/dependency version bumps and release metadata updates across multiple crates.

Poem

🐰 A Rabbit's Release Day Cheer ✨

Five-point-oh has had its day,
Five-point-one now leads the way!
From manifests to changelogs bright,
Version bumps throughout the night—
Negatives tested, dependencies aligned,
A bouncing release of the finest kind! 🥕

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title 'chore: prep 0.5.1 release' clearly describes the main change—preparing version 0.5.1 for release through version bumps and changelog updates.
Description check ✅ Passed The description directly relates to the changeset, explaining the version bump to 0.5.1, changelog entry addition, and validation steps performed.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/release-0.5.1

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

Comment @coderabbitai help to get the list of available commands and usage tips.

@EffortlessSteven EffortlessSteven merged commit 58d1427 into main Mar 28, 2026
2 of 4 checks passed
@EffortlessSteven EffortlessSteven deleted the chore/release-0.5.1 branch March 28, 2026 04:21
@coderabbitai coderabbitai Bot mentioned this pull request May 14, 2026
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@EffortlessSteven