Skip to content

Conversation

@n1ght-hunter
Copy link

built on top of #255 .
update a few different things.
move dependencies to workspace to make it easier to update and track versions.
updated most dependencies as well as move to bevy 0.16 (avian3d is currently a git dependency until they release)
fix up examples and tests to compile

@alphastrata
Copy link

@kaosat-dev there's a bevy gamejam coming up soon, is there any reason not to merge this one in before then? (Context: I suspect a lot of folk will reach for this tool over the next fortnight...)

@NicoZweifel
Copy link

@alphastrata I think the reason is that the Branch that this PR is based on (blenvy) is stale.

The reason for this is that the blenvy branch got squashed into main. This means that there will be conflicts with any branch based on the old blenvy branch. To fix the affected PR's you'll have to point them at main and resolve around 30 conflicts or re-do the PR/Branch based on main, some of them are changes that were pushed to main in the mean time. It will revert changes like #250 if not careful.

Idk if the maintainers of this project plan to continue maintaining it or not but to make merging this branch easier it should be based/point to main, only contain relevant changes and conflicts resolved. I did this to continue with a local project and 0.16.0 https://github.com/NicoZweifel/Blenvy/tree/0.16-fixed. I can create a separate PR as well but I am not sure if there is any point or if this PR should be fixed/cleaned up/updated instead.

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.

4 participants