BD103

> maybe the deprecated comment could redirect to something like "go comment on this pr if you see this message" to encourage potential users to report back I added a...

> I am sorry, how again is this controversial? I haven't seen any comment indicating such. @cart disagreed with this change last time it was attempted. (https://github.com/bevyengine/bevy/pull/3893#issuecomment-1055247308) No one has...

Bevy's dynamic plugin interface is almost certainly unsound, and I think this may be one such case. You may find #11969 interesting in this regard. Other bits of code that...

> I think the CI failure is spurious. Yup, feel free to rebase / merge from main to get the check started again. :)

> You might be interested in this: https://github.com/Leafwing-Studios/cargo-cache Thank you! I'll definitely take inspiration from that. I chose not to hash the lockfile because I figured that the amount of...

So far things are working well. I'm having some issues with the cache not being found, so I may have to move my testing over to my fork, where I...

Following @TimJentzsch's interesting link, I've decided to switch this PR to use Leafwing-Studios/cargo-cache for everything. I think it's a lot more maintainable than my custom solution (and it's easy to...

> Previously attempted in #7627, but the action has also improved since then Is there a reason the original PR was closed?

I feel like the risk is acceptable. Leafwing Studios is a trusted third-party, and the argument against using it is the same as any other Github Action we depend on....

> What would you think about handling this in a separate issue/PR? > I think it could be tackled independently of the way we generate the cache and has its...