[laurenfrederick]

Description

This is the Unity version of this PR: CesiumGS/cesium-unreal#1910. In addition there is a script for the updates to cesium-unity-samples.

A GitHub Actions workflow that would be run manually to do the draft release steps of the release:

• Check that main has built successfully
• Pull the release artifacts and rename them
• Create a draft release
  • Upload the artifacts to the release
  • Create release notes and add the changelog
  • Verify checksums

There is also a dry run mode where it prints out what it will do at each step. This way you can validate that it finds the correct artifacts, renames them correctly, and gets the correct changelog entry.

Issue number or link

Author checklist

• I have submitted a Contributor License Agreement (only needed once).
• I have done a full self-review of my code.
• I have updated CHANGES.md with a short summary of my change (for user-facing changes).
• I have added or updated unit tests to ensure consistent code coverage as necessary.
• I have updated the documentation as necessary.

Remaining Tasks

Next steps will be a script for the publishing step (separate PR)

Testing plan

Ran through the scripts/action where possible without causing actual prod issues. Used --dry-run where needed.

Reviewer checklist

Thank you for taking the time to review this PR. By approving a PR you are taking as much responsibility for these changes as the author.

As you review, please go through the checklist below:

• Review and run all parts of the test plan on this branch and verify it matches expectations.
  • If the issue is a bug please make sure you can reproduce the bug in the main branch and then checkout this branch to make sure it actually solved the issue.
• Review the code and make sure you do not have any remaining questions or concerns. You should understand the code change and the chosen approach. If you are not confident or have doubts about the code, please do not hesitate to ask questions.
  • Code should follow the C++ Style Guide
• Review the unit tests and make sure there are no missing tests or edge cases.
• Review documentation changes and updates to CHANGES.md to make sure they accurately cover the work in this PR.
• Verify that the Contributor License Agreement has been submitted, if needed.

[github-actions]

Thank you for the pull request, @laurenfrederick!

✅ We can confirm we have a CLA on file for you.

[j9liu]

Thanks @laurenfrederick !