Just found a merge hiccup and I fixed that, but I couldn't fix the broken gamepad tests... It's either something I messed up during the merge process, or it could be that some of the latest changes in main have to be changed to be 0.15 compatible. I'll appreciate any help here!

Can you ignore the tests for now? I think we should move forward as is and then fix the tests in follow-up.

Sure @alice-i-cecile, although I'm a bit worried since they seem to be checking the press status and the values of gamepad buttons and are failing to do so:

failures:

---- buttonlike_actions_can_be_pressed_and_released_when_button_value_set stdout ----
thread 'buttonlike_actions_can_be_pressed_and_released_when_button_value_set' panicked at tests\buttonlike.rs:195:5:
assertion failed: action_state.just_pressed(&TestAction::Throttle)

---- gamepad_button_value stdout ----
thread 'gamepad_button_value' panicked at tests\buttonlike.rs:103:5:
assertion `left == right` failed
  left: 0.0
 right: 1.0
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace


failures:
    buttonlike_actions_can_be_pressed_and_released_when_button_value_set
    gamepad_button_value

test result: FAILED. 4 passed; 2 failed; 2 ignored; 0 measured; 0 filtered out; finished in 0.00s

I tried fixing pcwalton's branch prior to merging main and the system ordering suggestion fixed all test issues, which suggests there's some other new issue that popped up for gamepads.

I'll push a change to ignore them anyway if that's the way to go.

Definitely share your concern: it's a blocking issue. I want to split it out though to be sure we can properly review and discuss the fix.

I forgot to test this with all features enabled 😓 I'll do another pass and fix the remaining failures as soon as I can.

@alice-i-cecile should be ready now, I ran all CI commands locally and they all pass. I took the liberty to adjust some doc comments to better fit the fact that Gamepads are now entities.