Skip to content

chore: release - #367

Closed
moq-bot[bot] wants to merge 1 commit into
mainfrom
release-plz-2026-11-05T16-55-42Z
Closed

moq-bot[bot] wants to merge 1 commit into
mainfrom
release-plz-2026-11-05T16-55-42Z

Conversation

@moq-bot

@moq-bot moq-bot Bot commented Nov 5, 2026 •

Copy link
Copy Markdown
Contributor

🤖 New release

  • rind: 0.1.13 -> 0.2.0 (⚠ API breaking changes)
  • rind-jsonwebtoken: 0.1.13 -> 0.2.0 (✓ API compatible changes)
  • rind-rustls: 0.1.13 -> 0.2.0 (✓ API compatible changes)
  • rind-dimpl: 0.1.13 -> 0.2.0 (✓ API compatible changes)
  • rind-object-store: 0.1.13 -> 0.2.0 (✓ API compatible changes)
  • rind-ring: 0.1.12 -> 0.2.0 (✓ API compatible changes)
  • rind-rcgen: 0.1.13 -> 0.1.14

⚠ rind breaking changes

--- failure enum_missing: pub enum removed or renamed ---

Description:
A publicly-visible enum cannot be imported by its prior path. A `pub use` may have been removed, or the enum itself may have been renamed or removed entirely.
        ref: https://doc.rust-lang.org/cargo/reference/semver.html#item-remove
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.51.0/src/lints/enum_missing.ron

Failed in:
  enum rind::signature::RsaKeySize, previously in file /tmp/nix-shell.dSVsy2/.tmp38sPT0/rind/src/mid/rsa_key_size.rs:7

--- failure inherent_method_missing: pub method removed or renamed ---

Description:
A publicly-visible method or associated fn is no longer available under its prior name. It may have been renamed or removed entirely.
        ref: https://doc.rust-lang.org/cargo/reference/semver.html#item-remove
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.51.0/src/lints/inherent_method_missing.ron

Failed in:
  EcdsaKeyPair::from_private_key_and_public_key, previously in file /tmp/nix-shell.dSVsy2/.tmp38sPT0/rind/src/high/signature.rs:683

--- failure method_parameter_count_changed: pub method parameter count changed ---

Description:
A publicly-visible method now takes a different number of parameters, not counting the receiver (self) parameter.
        ref: https://doc.rust-lang.org/cargo/reference/semver.html#fn-change-arity
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.51.0/src/lints/method_parameter_count_changed.ron

Failed in:
  rind::cipher::AesCtr::new takes 2 parameters in /tmp/nix-shell.dSVsy2/.tmp38sPT0/rind/src/mid/aes.rs:44, but now takes 3 parameters in /tmp/nix-shell.dSVsy2/.tmpc431QZ/rind/rind/src/mid/aes.rs:72
  rind::cipher::AesCtr::apply_keystream takes 3 parameters in /tmp/nix-shell.dSVsy2/.tmp38sPT0/rind/src/mid/aes.rs:60, but now takes 2 parameters in /tmp/nix-shell.dSVsy2/.tmpc431QZ/rind/rind/src/mid/aes.rs:91

--- failure struct_missing: pub struct removed or renamed ---

Description:
A publicly-visible struct cannot be imported by its prior path. A `pub use` may have been removed, or the struct itself may have been renamed or removed entirely.
        ref: https://doc.rust-lang.org/cargo/reference/semver.html#item-remove
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.51.0/src/lints/struct_missing.ron

Failed in:
  struct rind::signature::Pkcs8, previously in file /tmp/nix-shell.dSVsy2/.tmp38sPT0/rind/src/high/signature.rs:307
  struct rind::signature::RsaPublicKeyComponents, previously in file /tmp/nix-shell.dSVsy2/.tmp38sPT0/rind/src/high/signature.rs:915
  struct rind::signature::Spki, previously in file /tmp/nix-shell.dSVsy2/.tmp38sPT0/rind/src/high/signature.rs:329
Changelog

rind

0.2.0 - 2026-11-06

Added

  • (rsa) load RSA keys named id-RSAES-OAEP or id-ea-rsa, as aws-lc-rs does (#413)
  • (rsa) RSA public keys export as SPKI (#411)
  • [breaking] audit rind's public API, and apply its decisions, before 0.2.0 (#383)
  • (keys) SPKI, SEC1, and seed key formats, and compressed ECDH peers, for Bun (#382)
  • (cipher) AES-CBC with PKCS#7 padding on every backend (#381)
  • (agreement) [breaking] store, load, and export agreement keys, agreeing by reference (#372)
  • (signature) ECDSA over a precomputed digest (#379)
  • (signature) RSA-PSS with any salt length (#363)
  • (key_wrap) AES key wrap (RFC 3394) on AES decryption for every backend (#359)
  • (rsa) RSA-OAEP encryption and decryption, and RSA SPKI public keys (#361)
  • (cipher) [breaking] AES-CTR over a 16-byte counter block with a per-key counter width (#360)
  • (aead) AES-GCM with any IV length and truncated tags (#362)
  • (digest) SHA3-256, SHA3-384, and SHA3-512 (#358)
  • (proofs) prove aarch64 P-256 ECDSA end to end with Aeneas and Lean (#346)

Fixed

  • (ctgrind) green the nightly again: PBKDF2's HMAC out of line, and DIT denied under valgrind (#406)
  • (bench-report) hold each host with quest gate --host, and measure macOS noise (#399)
  • (cpu) run aarch64 Linux with DIT where Hyper-V hides it (#370)
  • (cpu) run aarch64 Windows with DIT where the core has it (#366)
  • (x86_64) build on the declared 1.90 rust-version, and gate on it (#365)

Other

  • (readme) show how to use rind and link the details (#410)
  • (aarch64) seal and open short AES-GCM messages in one pass (#393)
  • (aes) header protection reads the sample straight into AES-NI (#392)
  • (readme) credit Vale's proven kernel for short AES-GCM on VAES CPUs (#402)
  • (aes-gcm) run Vale's kernel for short messages on VAES CPUs (#391)
  • stop wiping anything but keys, keyed state, and private-key heap scratch (#394)
  • (sha) pad SHA-1 and SHA-256's last block in registers on the SHA extensions (#376)
  • (ecdsa) build a verifying key's multiples on its first verification (P-256 keygen 1.4x) (#374)
  • a prompt has an agent migrate a repo to rind and report the results (#357)
  • (sha256) [breaking] finish SHA-NI hashes in registers, and digest contexts by reference (#352)
  • (build) test aarch64 Windows, x86_64 macOS, and musl (#356)

rind-jsonwebtoken

0.2.0 - 2026-11-06

Added

  • [breaking] audit rind's public API, and apply its decisions, before 0.2.0 (#383)

rind-rustls

0.2.0 - 2026-11-06

Added

  • [breaking] audit rind's public API, and apply its decisions, before 0.2.0 (#383)

Fixed

  • (adapters) [breaking] return each adapter's own MissingFeature, not rind's (#420)

Other

  • (sha256) [breaking] finish SHA-NI hashes in registers, and digest contexts by reference (#352)

rind-dimpl

0.2.0 - 2026-11-06

Fixed

  • (adapters) [breaking] return each adapter's own MissingFeature, not rind's (#420)

rind-object-store

0.2.0 - 2026-11-06

Fixed

  • (adapters) [breaking] return each adapter's own MissingFeature, not rind's (#420)

rind-ring

0.2.0 - 2026-11-06

Added

  • (rsa) load RSA keys named id-RSAES-OAEP or id-ea-rsa, as aws-lc-rs does (#413)
  • [breaking] audit rind's public API, and apply its decisions, before 0.2.0 (#383)
  • (rind-ring) re-export rind's CPU check as cpu (#377)

Fixed

  • (adapters) [breaking] return each adapter's own MissingFeature, not rind's (#420)

Other

  • (readme) show how to use rind and link the details (#410)
  • stop wiping anything but keys, keyed state, and private-key heap scratch (#394)
  • (sha256) [breaking] finish SHA-NI hashes in registers, and digest contexts by reference (#352)

rind-rcgen

0.1.14 - 2026-11-06

Other

  • updated the following local packages: rind


This PR was generated with release-plz.

@pullfrog pullfrog Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ No new issues found.

Reviewed changes

Reviewed the full diff of the release-plz output (16 files): version bumps, Cargo.lock, and changelog entries for all seven published crates, against git history since the previous release.

  • rind 0.1.13 → 0.1.14 — changelog correctly records exactly the two commits landed since 7a1f4d6: feat(proofs) #346 and ci(build) #356; the quest/-only planning commit (#364) is correctly excluded.
  • Adapter bumps — rind-{jsonwebtoken,rustls,dimpl,rcgen,object-store} 0.1.13 → 0.1.14 and rind-ring 0.1.12 → 0.1.13, each with its rind path dependency bumped to 0.1.14 and its changelog entry inserted below ## [Unreleased]. Unpublished rind-instant-acme gets only the dependency bump, as expected.
  • Cargo.lock — package versions updated to match; nothing else touched.

Pullfrog  | View workflow run | Using glm-5.3-flash | 𝕏

@moq-bot
moq-bot Bot force-pushed the release-plz-2026-11-05T16-55-42Z branch 3 times, most recently from d24656b to 80e060a Compare November 5, 2026 17:22

@pullfrog pullfrog Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ No new issues found.

Reviewed changes

Reviewed the incremental delta since the prior pullfrog review (d24656b): release-plz regenerating the PR after the breaking AES-CTR change #360 landed on main.

  • rind bumped 0.1.14 → 0.2.0 — correct and required: #360 changes the public arity of AesCtr::new and AesCtr::apply_keystream (flagged by cargo-semver-checks in the PR body as a semver violation), and 0.x semver permits breaking changes in a minor bump. The new changelog bullet *(cipher)* [**breaking**] correctly carries the breaking marker.
  • Adapter dependency bumps — all six adapters now require rind 0.2.0; their own versions stay at the already-recorded 0.1.14 bumps (none of them use or re-export AesCtr, so their APIs are unaffected). Unpublished rind-instant-acme gets only the dep bump, as expected.
  • Cargo.lock — consistent with the 0.2.0 bump; the complete 0.2.0 changelog section still matches exactly the commits landed since 7a1f4d6 (verified against git history).

Pullfrog  | View workflow run | Using glm-5.3-flash | 𝕏

@moq-bot
moq-bot Bot force-pushed the release-plz-2026-11-05T16-55-42Z branch 6 times, most recently from 3890127 to ffd8de7 Compare November 5, 2026 18:04

@pullfrog pullfrog Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ No new issues found.

Reviewed changes

Reviewed the incremental delta since the prior pullfrog review (3890127): release-plz regenerating the PR after the breaking SHA-256 change #352 landed on main.

  • rind-ring and rind-rustls bumped to 0.2.0 — justified: both consume the affected digest API (rind-ring exposes a public digest module wrapping rind::digest; rind-rustls wires rind::digest into its rustls hash provider), so #352 reaches them, and release-plz replaced their previous "updated local packages" entries with the inherited *(sha256)* [**breaking**] bullet. The cargo-semver-checks-gated CI also confirms no adapter that stays at 0.1.14 needed a major bump.
  • rind/CHANGELOG.md — adds the *(sha256)* [**breaking**] bullet under ### Other; the 0.2.0 section now records exactly the eleven commits landed since 7a1f4d6 (#346, #356, #358, #359, #360, #361, #362, #365, #366, #363, #352), with the quest/-only planning commit (#369) correctly excluded. Verified against git history.
  • Cargo.lock — consistent with all new versions (rind 0.2.0, rind-ring/rind-rustls 0.2.0, adapters 0.1.14); nothing else touched.

Pullfrog  | View workflow run | Using glm-5.3-flash | 𝕏

@moq-bot
moq-bot Bot force-pushed the release-plz-2026-11-05T16-55-42Z branch from ffd8de7 to d6d254e Compare November 5, 2026 19:05
@pullfrog

pullfrog Bot commented Nov 5, 2026

Copy link
Copy Markdown

Your OpenCode Go account is out of credit. Top it up, then re-trigger Pullfrog.

OpenCode Go's response
provider error: Upstream request failed: Insufficient account funds

Top up OpenCode Go →

Pullfrog  | Rerun failed job ➔ | View workflow run | via Pullfrog | Using glm-5.3-flash

@moq-bot
moq-bot Bot force-pushed the release-plz-2026-11-05T16-55-42Z branch 3 times, most recently from a6466cc to 320978b Compare November 5, 2026 21:24
@moq-bot
moq-bot Bot force-pushed the release-plz-2026-11-05T16-55-42Z branch 5 times, most recently from 46e50b1 to e127ea7 Compare November 6, 2026 06:46
@moq-bot
moq-bot Bot force-pushed the release-plz-2026-11-05T16-55-42Z branch 5 times, most recently from f5131ae to ab0b030 Compare November 6, 2026 21:29
@moq-bot
moq-bot Bot force-pushed the release-plz-2026-11-05T16-55-42Z branch 5 times, most recently from 47c9971 to a93323f Compare November 6, 2026 22:47
@moq-bot
moq-bot Bot force-pushed the release-plz-2026-11-05T16-55-42Z branch from a93323f to 4188fd8 Compare November 6, 2026 22:51
@kixelated
kixelated added this pull request to the merge queue Nov 6, 2026
@moq-bot moq-bot Bot closed this Nov 6, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to a manual request Nov 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants