Skip to content

ci: hold rand at 0.8 until rsa 0.10 is stable - #46

Merged
nihaopaul merged 1 commit into
mainfrom
chore/dependabot-ignore-rand
Aug 24, 2026
Merged

ci: hold rand at 0.8 until rsa 0.10 is stable#46
nihaopaul merged 1 commit into
mainfrom
chore/dependabot-ignore-rand

Conversation

@nihaopaul

Copy link
Copy Markdown
Owner

Follow-up to closing #43.

rand 0.9 moved to rand_core 0.9, but rsa 0.9 — still the latest stable release, with 0.10 at 0.10.0-rc.18 — takes its RNG as rand_core 0.6's CryptoRngCore. The two trait hierarchies are unrelated, so the throwaway RSA keypair that cloudflare-authenticator's tests mint at run time cannot be generated from a newer rand:

error[E0277]: the trait bound `ThreadRng: CryptoRngCore` is not satisfied
    = note: there are multiple different versions of crate `rand` in the dependency graph
    = note: required for `ThreadRng` to implement `CryptoRngCore`

Without this entry the weekly run keeps reopening a pull request that cannot compile. Ignoring major and minor bumps still lets 0.8.x patches through, so a genuine fix in the 0.8 line would land normally.

rand is a [dev-dependencies] entry, so this pins nothing in the released binary. Lift the ignore and bump rsa and rand together once rsa 0.10 is stable.

🤖 Generated with Claude Code

rand 0.9 moved to rand_core 0.9, but rsa 0.9 — still the latest stable
release — takes its RNG as rand_core 0.6's `CryptoRngCore`. The two trait
hierarchies are unrelated, so the throwaway RSA keypair minted for the
cloudflare-authenticator tests cannot be generated from a newer rand
without either an rsa release candidate or a hand-written adapter shim.

Ignore major and minor rand bumps so the weekly run stops reopening a
pull request that cannot compile, while still letting 0.8.x patches
through. Both should be lifted together when rsa 0.10 ships stable.
@nihaopaul
nihaopaul merged commit 6b73e84 into main Aug 24, 2026
7 checks passed
@nihaopaul
nihaopaul deleted the chore/dependabot-ignore-rand branch August 24, 2026 08:23
@nihaopaul nihaopaul mentioned this pull request Aug 30, 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.

1 participant