Skip to content

Add stricter nonmax crate version requirement#24776

Merged
mockersf merged 1 commit into
bevyengine:mainfrom
RCoder01:patch-1
Jun 27, 2026
Merged

Add stricter nonmax crate version requirement#24776
mockersf merged 1 commit into
bevyengine:mainfrom
RCoder01:patch-1

Conversation

@RCoder01

@RCoder01 RCoder01 commented Jun 27, 2026

Copy link
Copy Markdown
Contributor

Objective

bevy_ecs fails to compile when using nonmax crate version <= 0.5.3, but version 0.5.3 satisifes the Cargo.toml nonmax = "0.5". Specifically, bevy_ecs uses the nonmax::NonMaxU32::MAX associated item, which was added in version 0.5.4.

Solution

Update the bevy_ecs Cargo.toml to require a version of nonmax newer than 0.5.4

Testing

I compiled an empty application with the following Cargo.toml, which causes a compile error in bevy_ecs.

[package]
name = "app"
version = "0.1.0"
edition = "2024"

[dependencies]
bevy = "0.19"
nonmax = "=0.5.3"

Updating to nonmax = "=0.5.4" or nonmax = "=0.5.5" fixes the issue.

@RCoder01

RCoder01 commented Jun 27, 2026

Copy link
Copy Markdown
Contributor Author

I ran into this when upgrading an old bevy 0.13 app straight to 0.19 without running cargo update

@kfc35 kfc35 added D-Trivial Nice and easy! A great choice to get started with Bevy C-Dependencies A change to the crates that Bevy depends on S-Ready-For-Final-Review This PR has been approved by the community. It's ready for a maintainer to consider merging it labels Jun 27, 2026
@mockersf mockersf added this pull request to the merge queue Jun 27, 2026
Merged via the queue into bevyengine:main with commit a5c5071 Jun 27, 2026
49 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

C-Dependencies A change to the crates that Bevy depends on D-Trivial Nice and easy! A great choice to get started with Bevy S-Ready-For-Final-Review This PR has been approved by the community. It's ready for a maintainer to consider merging it

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants