Skip to content

Prompt for release prep steps - #1443

Merged
j9liu merged 10 commits into
mainfrom
prepare-release-prompt
Sep 24, 2026
Merged

j9liu merged 10 commits into
mainfrom
prepare-release-prompt

Conversation

@laurenfrederick

Copy link
Copy Markdown
Contributor

Description

GitHub Copilot Prompt for the release preparation steps.

< !-- Provide context for the reviewer to understand the pull request. Include what changes were made and why. -->

Issue number or link

#1441

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

Testing plan

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.
  • 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.

@j9liu
j9liu self-requested a review September 21, 2026 17:51
@j9liu j9liu added this to the October 2026 Release milestone Sep 21, 2026

@j9liu j9liu left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @laurenfrederick ! Just two small comments from me.

Comment thread .github/skills/prepare-release/SKILL.md Outdated
Comment thread doc/topics/release-process.md Outdated

## Prepare for Release

Run the `/prepare-release` skill in [.github/skills/prepare-release/SKILL.md](../../.github/skills/prepare-release/SKILL.md) and provide the release version number. It performs the first four steps for you:

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The documentation build is failing because ../.github/skills/prepare-release/SKILL.md is not included in the known paths. You can add it to the docs/CMakeLists.txt under doxygen_add_docs.

However, doing so makes the page look like so:

Image

I'm not sure how useful it is to view it that way -- I kinda prefer seeing it on the GitHub site itself, since it's GH specific, so maybe this could link to https://github.com/CesiumGS/cesium-native/tree/main/.github/skills/prepare-release/SKILL.md. But up to you what you think is most useful!

laurenfrederick and others added 7 commits September 23, 2026 15:47
Co-authored-by: Janine Liu <32226860+j9liu@users.noreply.github.com>
The local mesh variable was constructed but never read, so it
served no purpose. It could not simply be optimized away, though:
draco::Mesh has an out-of-line constructor and a non-trivial
destructor defined inside the Draco library, so the compiler must
still emit the construction/destruction across the shared-library
boundary. Removing the unused variable eliminates that unnecessary
overhead.
@j9liu

j9liu commented Sep 24, 2026

Copy link
Copy Markdown
Collaborator

Thanks @laurenfrederick !

@j9liu
j9liu merged commit 3e4ea9b into main Sep 24, 2026
28 checks passed
@j9liu
j9liu deleted the prepare-release-prompt branch September 24, 2026 18:06
@j9liu j9liu linked an issue Sep 28, 2026 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Create a Copilot prompt for release preparation steps

5 participants