This PR removes the support for the bevy-main branch, which depends on the main version of Bevy. I'm going to remove that for multiple reasons. First of all, breaking changes in Bevy have become more rare, especially on the rendering side (for what this project is concerned about). Second, Bevy now implements a release candidate schedule, which gives plugin maintainers time for updating their packages.
Given these benefits, maintaining a tracking branch is more of a burden than else, therefore, it will be removed. There are no commits ahead of master in bevy-main, so the only required next action is to remove the branch.
This PR removes the support for the
bevy-mainbranch, which depends on the main version of Bevy. I'm going to remove that for multiple reasons. First of all, breaking changes in Bevy have become more rare, especially on the rendering side (for what this project is concerned about). Second, Bevy now implements a release candidate schedule, which gives plugin maintainers time for updating their packages.Given these benefits, maintaining a tracking branch is more of a burden than else, therefore, it will be removed. There are no commits ahead of
masterinbevy-main, so the only required next action is to remove the branch.