Skip to content

Update to rand:0.8.0 #1113

@CAD97

Description

@CAD97

This is, roughly, intended to be a tracking issue of what's required to cleanly upgrade bevy's tree from rand:0.7 to rand:0.8. Thankfully: not much!

What problem does this solve or what need does it fill?

Update to the latest version of upstream. Randomness is not uncommon in games, and this saves people using the latest version of rand for their game code from having duplicate copies of rand in their dependency tree. This is also currently one of very few out-of-date dependency reported by cargo upgrade[1].

Describe the solution would you like?

The simple cargo upgrade rand --workspace isn't quite enough to purge rand:0.7 from the tree, as uuid:0.8.1 still uses rand:0.7. uuid:git:master currently uses getrandom:0.1.15 directly, and I've opened uuid-rs/uuid#501 to update to getrandom:0.2 (as used by rand:0.8.0 and already in tree via ahash).

Describe the alternative(s) you've considered?

  • Just don't upgrade, and stay on rand:0.7. Drifting behind upstream is definitely not ideal.

Additional context

All out-of-date dependencies:

bevy_ecs:
    Upgrading rand v0.7.3 -> v0.8.0
bevy_asset:
    Upgrading crossbeam-channel v0.4.4 -> v0.5.0
    Upgrading notify v5.0.0-pre.2 -> v5.0.0-pre.4
    Upgrading rand v0.7.3 -> v0.8.0
bevy_gltf:
    Upgrading base64 v0.12.3 -> v0.13.0
bevy_wgpu:
    Upgrading crossbeam-channel v0.4.4 -> v0.5.0
    Upgrading crossbeam-utils v0.7.2 -> v0.8.1
bevy:
    Upgrading rand v0.7.3 -> v0.8.0

Metadata

Metadata

Assignees

No one assigned

    Labels

    C-DependenciesA change to the crates that Bevy depends on

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions