Skip to content

[Merged by Bors] - Remove a non-breaking change from the 0.10 migration guide #593

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

Closed
wants to merge 1 commit into from

Conversation

joseph-gio
Copy link
Member

The type UnsafeWorldCellEntityRef was introduced after 0.9 and renamed before 0.10, so this was not a breaking change.

This type was introduced after 0.9 and renamed before 0.10, so this is not a breaking change.
Copy link
Member

@james7132 james7132 left a comment

Choose a reason for hiding this comment

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

bors r+

bors bot pushed a commit that referenced this pull request Mar 7, 2023
The type `UnsafeWorldCellEntityRef` was introduced after 0.9 and renamed before 0.10, so this was not a breaking change.
@bors
Copy link

bors bot commented Mar 7, 2023

Pull request successfully merged into master.

Build succeeded:

@bors bors bot changed the title Remove a non-breaking change from the 0.10 migration guide [Merged by Bors] - Remove a non-breaking change from the 0.10 migration guide Mar 7, 2023
@bors bors bot closed this Mar 7, 2023
@joseph-gio joseph-gio deleted the patch-3 branch March 7, 2023 12:25
@joseph-gio
Copy link
Member Author

Hmm... I think the even bigger problem is that bevyengine/bevy#6404 seems to have no migration guide, despite removing public methods from World.

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.

3 participants