Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@HexSleeves
Copy link
Collaborator

No description provided.

Copy link
Member

@zicklag zicklag left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome, and a big thank you!! It doesn't look like it ended up too bad.

Comment on lines 12 to 15
async-io = "1.9"
bevy_tasks = "0.10"
futures-lite = "1"
pin-project = "1"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a reason to make these version specifications less specific?

I'm not necessarily against it, but I was wondering if it was intentional.

As far as I understand, doing 1 is the same as 1.0.0, and that would assert that we are compatible with 1.0.0 exactly, and everything after 1.0.

That's probably true, but in order to be sure, we would have to try and build the game with version 1.0.0 exactly and make sure it still works. I've actually only ever tested the game with whatever was the latest-released version of the crate at the time I added it, so I only knew that the more specific specifier was actually tested.

@zicklag
Copy link
Member

zicklag commented May 30, 2023

I just pushed a commit to fix the documentation issue in CI. I think this is ready as soon as I get your feedback on the version numbers. 🚀

@zicklag zicklag force-pushed the feat/bevy-0.10 branch 2 times, most recently from 5edc14c to 9e66672 Compare June 1, 2023 18:53
@zicklag zicklag changed the title feat: Upgrade bones to bevy 0.10 feat: upgrade to Bevy 0.10. Jun 1, 2023
@zicklag zicklag added this pull request to the merge queue Jun 1, 2023
Merged via the queue into fishfolk:main with commit 3f2e348 Jun 1, 2023
@HexSleeves HexSleeves deleted the feat/bevy-0.10 branch June 19, 2023 00:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants