Bump version

idanarye · Feb 26, 2024 · 2282e5d · 2282e5d
1 parent 6bcbc9a
commit 2282e5d
Show file tree

Hide file tree

Showing 3 changed files with 13 additions and 10 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -6,18 +6,13 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
 
 ## [Unreleased]
 
-## 0.18.0 - 2024-02-18
+## 0.19.0 - 2024-02-27
 ### Changed
 - Upgrade bevy_egui to 0.24.
-- [**BREAKING**] Changed some API types to use Bevy's new math types (instead
-  of vectors):
-  - `VpeolDragPlane` now uses `Plane3d`.
-  - `Vpeol3dPluginForEditor` also uses `Plane3d`.
-  - `Vpeol3dCameraControl` uses `Plane3d` for the camera drag plane, and
-    `Direction3d` for configuring the UP direction to maintain while rotating
-    the camera.
-
+- [**BREAKING**] Changed some API types to use Bevy's new math types. See the
+  [migration guide](MIGRATION-GUIDES.md#migrating-to-yoleck-019).
 
+## 0.18.0 - 2024-02-18
 ### Fixed
 - [**BREAKING**] Typo - `Rotatation` -> `Rotation` in Vpeol.
 

diff --git a/Cargo.toml b/Cargo.toml
@@ -4,7 +4,7 @@ members = ["macros"]
 [package]
 name = "bevy-yoleck"
 description = "Your Own Level Editor Creation Kit"
-version = "0.18.0"
+version = "0.19.0"
 edition = "2021"
 authors = ["IdanArye <idanarye@gmail.com>"]
 license = "MIT OR Apache-2.0"

diff --git a/MIGRATION-GUIDES.md b/MIGRATION-GUIDES.md
@@ -4,6 +4,14 @@
 
 Bevy 0.13 introduces types for defining directions and planes, which can be used instead of vectors. Yoleck (mainly Vpeol) uses them now in its API. The conversion should be straightforward.
 
+Specifically:
+
+- `VpeolDragPlane` now uses `Plane3d`.
+- `Vpeol3dPluginForEditor` also uses `Plane3d`.
+- `Vpeol3dCameraControl` uses `Plane3d` for the camera drag plane, and
+`Direction3d` for configuring the UP direction to maintain while rotating
+the camera.
+
 ## `vpeol_read_click_on_entity`
 
 Bevy 0.13 [split `WorldQuery` to `QueryData` and `FilterData`](https://bevyengine.org/learn/migration-guides/0-12-to-0-13/#split-worldquery-into-querydata-and-queryfilter) (though there is still a `WorldQuery` trait with some of that functionality). When you use `vpeol_read_click_on_entity`, the data passed to it is `QueryFilter`, not `QueryData` - which measn that if it's a component (which should usually be the case) you need `vpeol_read_click_on_entity::<Has<MyComponent>>` and not `vpeol_read_click_on_entity::<&MyComponent>` (which would have worked before)