Skip to content

clear 0.19 release content from main#24276

Open
mockersf wants to merge 2 commits into
bevyengine:mainfrom
mockersf:clear-0.19-release-content-from-main
Open

clear 0.19 release content from main#24276
mockersf wants to merge 2 commits into
bevyengine:mainfrom
mockersf:clear-0.19-release-content-from-main

Conversation

@mockersf
Copy link
Copy Markdown
Member

Objective

  • 0.19 branch has started, clear release content on main

Solution

  • clear release content on main

@Zeophlite Zeophlite added D-Trivial Nice and easy! A great choice to get started with Bevy S-Ready-For-Final-Review This PR has been approved by the community. It's ready for a maintainer to consider merging it labels May 13, 2026
alice-i-cecile pushed a commit that referenced this pull request May 13, 2026
# Objective

- Missing some renames during migration to `0.19.0-rc.1`

## Solution

- Add to migration guide
- PR against release branch as expecting
#24276 to remove them

## Testing

- N/A
@alice-i-cecile alice-i-cecile added this pull request to the merge queue May 13, 2026
@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to failed status checks May 13, 2026
@alice-i-cecile alice-i-cecile added this pull request to the merge queue May 14, 2026
@alice-i-cecile alice-i-cecile removed this pull request from the merge queue due to a manual request May 14, 2026
@alice-i-cecile
Copy link
Copy Markdown
Member

I feel mixed about this. It's good to do to unblock 0.20 work, but it makes hybrid fixes + note changes like #24286 quite a bit harder.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

D-Trivial Nice and easy! A great choice to get started with Bevy S-Ready-For-Final-Review This PR has been approved by the community. It's ready for a maintainer to consider merging it

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants