-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Strange issue with latest bevy main #31
Comments
To be sure: you are using the |
Could you try pinning Bevy to the same commit bevy_kira_audio uses? |
That works, but, that restricts me to use that specific commit |
If there are no further breaking changes since that commit, you should be able to patch the bevy dependency from the official repository to your own fork in your Cargo file. Then bevy_kira_audio will use the latest commit, too. |
Also, I recommend reading https://bevy-cheatbook.github.io/setup/bevy-git.html |
Yes, if you update to latest bevy main the issue is fixed. |
I choose on purpose to pin the Bevy dependency because I want the branch to always work. See #13 for the last time this came up. An alternative I have been considering is to depend on the main branch without pinning a working revision and have some workflow regularly check if all tests are still green. But for now I would like to keep pinning working revisions. |
I will close this for now, because the used Bevy commit can be patched in the user's I also updated the Bevy commit on the |
The text was updated successfully, but these errors were encountered: