|
cesium-native 0.65.0
|
This is the process we follow when releasing a new version of Cesium Native.
Run the /prepare-release skill in the GitHub-hosted skill file and provide the release version number. You can do this in the GitHub Copilot chat by typing /prepare-release <version-number>. It performs these four steps for you:
CHANGES.md is complete and accurate.version property in package.json.VERSION property passed to the project() function in CMakeLists.txt.After the prompt has completed, review and commit these changes. You can push them directly to main.
Use the release helper script to tag the release, push the tag to GitHub, and fast-forward the cesium.com branch to the new tag. Replace the version number with the one used in the preparation steps above.
Use --dry-run to preview the commands without changing anything, --yes to skip the confirmation prompt, or --remote <name> to target a non-default remote.
This script performs the release and docs publication steps in one operation:
v0.56.0 tag.cesium.com and fast-forwards it to the tag.cesium.com branch.main.| Date | User |
|---|---|
| 6/1/2026 | @timoore |
| 7/1/2026 | @azrogers |
| 8/3/2026 | @j9liu |
| 9/1/2026 | @timoore |
| 10/1/2026 | @azrogers |
| 11/2/2026 | @j9liu |
| 12/1/2026 | @timoore |
| Days Until Release | Release Tasks |
|---|---|
| T-2 | * All pending PRs merged in all repos * Begin cesium-native release * Update cesium-native in all runtimes and perform regression testing |
| T-1 | * Create release commits for cesium-unity and cesium-unreal * Debug any CI issues * Prepare GitHub release drafts |
| T-0 | * Publish releases |