-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
[Merged by Bors] - Bump notify to 5.0.0-pre.11 #2564
Conversation
I believe there was discussion on discord about chosing I assume |
Replaces #2545 Yup, the idea was to fix for a patch with the smallest change possible, and that was using the last known working version. Thank you for the followup pr! |
bors try |
tryTimed out. |
bogus |
bors r+ |
# Objective notify 5.0.0-pre.11 breaks the interface again, but apparently in a way that's similar to how it used to be ## Solution Bump `bevy_asset` dependency on notify to `5.0.0-pre.11` and fix the errors that crop up. It looks like `pre.11` was mentioned in #2528 by @mockersf but there's no mention of why `pre.10` was chosen ultimately.
# Objective notify 5.0.0-pre.11 breaks the interface again, but apparently in a way that's similar to how it used to be ## Solution Bump `bevy_asset` dependency on notify to `5.0.0-pre.11` and fix the errors that crop up. It looks like `pre.11` was mentioned in bevyengine#2528 by @mockersf but there's no mention of why `pre.10` was chosen ultimately.
Objective
notify 5.0.0-pre.11 breaks the interface again, but apparently in a way that's similar to how it used to be
Solution
Bump
bevy_asset
dependency on notify to5.0.0-pre.11
and fix the errors that crop up.It looks like
pre.11
was mentioned in #2528 by @mockersf but there's no mention of whypre.10
was chosen ultimately.