Skip to content

Update to rand version 0.10#27

Open
matheus23 wants to merge 1 commit intotomtomwombat:mainfrom
matheus23:matheus23/rand-0.10
Open

Update to rand version 0.10#27
matheus23 wants to merge 1 commit intotomtomwombat:mainfrom
matheus23:matheus23/rand-0.10

Conversation

@matheus23
Copy link

This updates rand to version 0.10.

We would need this to ship to be able to update noq (and quinn) to rand version 0.10 without causing users to have duplicate rand dependencies in their dependency tree.

@tomtomwombat
Copy link
Owner

Sorry for the delayed response.

I think rand 0.10 has MSRV 1.85 making it incompatible with fastbloom's MSRV 1.70?

Is there way around this? Just curious, why are the duplicate rand dependencies a blocker for noq's release?

@tomtomwombat
Copy link
Owner

fastbloom only has the rand dependency with it's "rand" feature, which is optional. So one option is to disable that feature in your usage of fastbloom, if acceptable.

@matheus23
Copy link
Author

Thank you.
Yeah it looks like disabling the rand feature is sufficient for our use cases, thank you!

Feel free to keep this PR open for a future MSRV increase or close it 👍

github-merge-queue bot pushed a commit to n0-computer/noq that referenced this pull request Mar 23, 2026
## Description

This updates noq and its dependencies to rand 0.10 and getrandom 0.4.

## Breaking Changes

I don't think there are any of rand's APIs exposed in noq or noq-proto.
So no breaking changes.

## Notes & open questions

~~Blocked on tomtomwombat/fastbloom#27 being
released.~~ We can disable the rand feature for fastbloom instead.

`proptest` still depends on rand 0.9:
```
$ cargo tree -i rand@0.9
rand v0.9.2
└── proptest v1.9.0
    [dev-dependencies]
    └── noq-proto v0.16.0 (/home/philipp/program/work/noq/noq-proto)
        ├── noq v0.17.0 (/home/philipp/program/work/noq/noq)
        │   ├── bench v0.2.0 (/home/philipp/program/work/noq/bench)
        │   └── perf v0.2.0 (/home/philipp/program/work/noq/perf)
        └── perf v0.2.0 (/home/philipp/program/work/noq/perf)
```
But it's only a dev-dependency, so won't get pulled in for people
depending on noq.
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.

2 participants