Skip to content
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

Update code after changes of systems api in bevy #208

Merged
merged 1 commit into from
Mar 23, 2023

Conversation

iwek7
Copy link
Contributor

@iwek7 iwek7 commented Mar 22, 2023

Breaking changes were introduced in
bevyengine/bevy#8079

Not sure what strategy of keeping up to date with bevy this project has (master depends on bevy main branch but there are also some other branches), but this will be probably useful for anyone using bevy custom build.

@Nilirad
Copy link
Owner

Nilirad commented Mar 23, 2023

Hi, thanks for the fix! According to #205 I'm going to track the latest bevy release on the master branch. Can you please change the target branch of this PR to bevy-main?

@iwek7 iwek7 changed the base branch from master to bevy-main March 23, 2023 08:19
@iwek7
Copy link
Contributor Author

iwek7 commented Mar 23, 2023

done

@Nilirad Nilirad merged commit 057f3e8 into Nilirad:bevy-main Mar 23, 2023
@iwek7 iwek7 deleted the bevy_master_work branch March 23, 2023 14:49
Nilirad added a commit that referenced this pull request Jul 10, 2023
* Update code after changes of systems api in bevy (#208)

Breaking changes were introduced in
bevyengine/bevy#8079

* Use GitHub Actions config from master branch (#217)

* Use GitHub Actions config from master branch

* Fix formatting

* Fix deprecation warnings on add_plugin

* Fix CI (#218)

* Fix shader (#219)

* Depend on Bevy 0.11

* Bump version to v0.9.0

* Use cargo add instruction in README

* Update README

* Update CHANGELOG

---------

Co-authored-by: Michał Iwańczuk <miwanczuk7@gmail.com>
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