0.5.0 release

CHANGES.md

@@ -1,5 +1,15 @@
 # Change Log
 
+### v0.5.0 - 2023-05-01
+
+- Added material pool for better performance and to reduce texture/material loading artifacts.
+- Added support for multiple viewports.
+- Fixed red flashes when materials are loading.
+- Fixed cyan flashes when textures are loading.
+- Fixed adding imagery as base layer for existing tileset.
+- Fixed Fabric types for `tilesetId` and `tileId`.
+- Upgraded to cesium-native v0.23.0.
+
 ### v0.4.0 - 2023-04-03
 
 - Fixed a crash when removing the last available access token for a tileset.

CMakeLists.txt

@@ -9,7 +9,7 @@ endif()
 # Both CXX and C need to be given otherwise Conan may ignore the CMAKE_C_COMPILER flag
 project(
     CesiumOmniverse
-    VERSION 0.4.0
+    VERSION 0.5.0
     DESCRIPTION "Cesium for Omniverse"
     LANGUAGES CXX C)
 

docs/release-guide/README.md

@@ -10,15 +10,16 @@ This is the process we follow when releasing a new version of Cesium for Omniver
 6. Update the extension `version` in [extension.toml](../../exts/cesium.omniverse/config/extension.toml). This should be the same version as above.
 7. Update [`CHANGES.md`](CHANGES.md).
 8. Commit the changes, e.g. `git commit -am "0.0.0 release"`.
-9. Tag the release, e.g. `git tag -a v0.0.0 -m "0.0.0 release"`.
-10. Push to main, e.g. `git push --atomic origin main v0.0.0`.
-11. Wait for CI to pass.
-12. Download the release build from S3. In the AWS management console (old AWS account), go to the bucket [`cesium-travis-builds/cesium-omniverse/main`](https://s3.console.aws.amazon.com/s3/buckets/cesium-travis-builds?region=us-east-1&prefix=cesium-omniverse/main/&showversions=false), find the appropriate date and commit hash to download the CentOS and Windows builds zip files (e.g. `CesiumForOmniverse-Linux-vX.X.X.zip` and `CesiumForOmniverse-Windows-vX.X.X.zip`). Note that the git tag is appended to end of the file name instead of the git commit hash.
-13. Create a new release on GitHub: https://github.com/CesiumGS/cesium-omniverse/releases/new.
+9. Push the commit, e.g. `git push origin main`.
+10. Tag the release, e.g. `git tag -a v0.0.0 -m "0.0.0 release"`.
+11. Push the tag, e.g. `git push origin v0.0.0`.
+12. Wait for CI to pass.
+13. Download the release build from S3. In the AWS management console (old AWS account), go to the bucket [`cesium-travis-builds/cesium-omniverse/main`](https://s3.console.aws.amazon.com/s3/buckets/cesium-travis-builds?region=us-east-1&prefix=cesium-omniverse/main/&showversions=false), find the appropriate date and commit hash to download the CentOS and Windows builds zip files (e.g. `CesiumForOmniverse-Linux-vX.X.X.zip` and `CesiumForOmniverse-Windows-vX.X.X.zip`). Note that the git tag is appended to end of the file name instead of the git commit hash.
+14. Create a new release on GitHub: https://github.com/CesiumGS/cesium-omniverse/releases/new.
   * Chose the new tag.
   * Copy the changelog into the description. Follow the format used in previous releases.
   * Upload the Linux and Windows release zip files.
-14. Proceed to [Releasing a new version of Cesium for Omniverse Samples](#releasing-a-new-version-of-cesium-for-omniverse-samples).
+15. Proceed to [Releasing a new version of Cesium for Omniverse Samples](#releasing-a-new-version-of-cesium-for-omniverse-samples).
 
 # Releasing a new version of Cesium for Omniverse Samples
 

exts/cesium.omniverse/config/extension.toml

@@ -1,5 +1,5 @@
 [package]
-version = "0.4.0"
+version = "0.5.0"
 category = "simulation"
 feature = false
 app = false