26. https://github.com/bevyengine/bevy/pull/18047
The trivial dependency bump that turned into a disaster due to questionable decisions from getrand on how to handle web support. Sorry! We should make an explicit call on what to do though (even if that's wait for now), so this can stay.
Objective New rand version, which means updating glam and encase to support the newer ecosystem update. Does mean that this changes how WASM builds need to be done in order to configure getrandom c...
27. https://github.com/bevyengine/bevy/pull/19232
Enable wayland by default. Trivial but controversial. Fine, this can stay, and we'll make a call quick. The release candidate process is good for testing risky user-facing changes like this.
28. https://github.com/bevyengine/bevy/pull/17889
Remote asset sources via https. I really want this so we can use better assets for our examples. This has been a huge pain. I would like to ship this, but Francois has had ongoing reasonable complaints. Let me ask him what we should do.
Objective This is a duplicate of #16366 because I made a mess of the commit history. See that pr for more context and discussion. Fixes Feature: Upstream bevy_web_asset, allowing assets loaded via...
29. https://github.com/bevyengine/bevy/pull/19340
Image node rotation. Neat! Definitely not milestone content: it's in draft due to a need for design with no movement for months. Cutting.
30. https://github.com/bevyengine/bevy/issues/18981
Disabled entities are not working properly with rendering, among other things. This is largely due to our decision to avoid firing change detection and lifecycle events when disabling and re-enabling entities.
Needs serious design; cutting :(
Bevy version 0.16.0 What you did Spawn an Entity with a mesh and the Disabled component. Remove the component later. What went wrong The mesh will not render. Additional information Minimal reprodu...
31. https://github.com/bevyengine/bevy/pull/19377
A random cleanup PR for some BRP method names. Just needs a second review. This can stay: I can review this even if needed. Better to get the breaking changes done sooner.
32. https://github.com/bevyengine/bevy/pull/19415
A hacky text measure functionality. Useful, but a reviewer suggested some serious improvements. Those haven't been implemented, so I'm bumping to the next milestone.
33. https://github.com/bevyengine/bevy/issues/19452
A simple request to experiment with type magic to avoid ergonomics regressions for state-scoped entities. Easy to test, leaving it in and I'll get to it this week.
I have reverted back to clear_events_on_exit_state, but unlike with 4 it requires specifying the event type each time. Quick question: if you use an impl Trait argument, rather than a generic, can ...
34. https://github.com/bevyengine/bevy/pull/19489
A proposed change (again...) to the behavior of `Single`. I'm on the fence about this: it's more consistent but less convenient. We should make the call now and stick with it; this stays in the milestone.
@alice_i_cecile oh no, not again.
Single will become useless again with this change.
I would argue a change in the opposite direction would make a lot more sense.
Have Res systems params behave the same way as Single does now.
Unifying the behavior, and allow users to define to panic through configuration.
If this will be merged, using Query with single and an early out is a lot more ergonomic than `When<Single<&Player>>`.