Skip to content

[Feature] Bump rand to 0.9 #2310

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mattsse opened this issue Apr 11, 2025 · 1 comment · May be fixed by #2318
Open

[Feature] Bump rand to 0.9 #2310

mattsse opened this issue Apr 11, 2025 · 1 comment · May be fixed by #2318
Assignees
Labels
blocked This cannot move forward until something else changes enhancement New feature or request
Milestone

Comments

@mattsse
Copy link
Member

mattsse commented Apr 11, 2025

Component

signers

Describe the feature you would like

alloy-primitives is using rand 0.9

we should also update here

Additional context

No response

@mattsse mattsse added the enhancement New feature or request label Apr 11, 2025
@github-project-automation github-project-automation bot moved this to Todo in Alloy Apr 11, 2025
@mattsse mattsse added this to the v1.0 milestone Apr 11, 2025
@yash-atreya yash-atreya linked a pull request Apr 15, 2025 that will close this issue
3 tasks
@yash-atreya
Copy link
Member

#2318 (comment)

We need k256 with rand_core v0.9 first

Currently, it's included in a pre-release https://github.com/RustCrypto/elliptic-curves/blob/32343a78f1522aa5bd856556f114053d4bb938e0/k256/CHANGELOG.md#changed

After this, we can update to rand 0.9 in the eip-7702 crate and here as well.

@yash-atreya yash-atreya added the blocked This cannot move forward until something else changes label Apr 18, 2025
@yash-atreya yash-atreya moved this from Todo to In Progress in Alloy Apr 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked This cannot move forward until something else changes enhancement New feature or request
Projects
Status: In Progress
Development

Successfully merging a pull request may close this issue.

2 participants