Conversation
|
Thank you for the pull request, @ggetz! ✅ We can confirm we have a CLA on file for you. |
Contributor
Author
|
@mzschwartz5 or @jjhembd, could you please review? |
mzschwartz5
reviewed
Feb 2, 2026
| - If an update is incompatible, open a new issue tagged with the `dependencies` label. | ||
| - If an update can be resolved, commit the changes and open a PR for review. | ||
| - Check against the [`dependencies` label](https://github.com/CesiumGS/cesium/issues?q=is%3Aissue+is%3Aopen+label%3Adependencies) for any known compatibility issues or specifics on pinned versions. Skip the dependency update if it is still incompatible. | ||
| - To increment a dependency, check out a new branch. Run `npm install <packagename>@latest` and verify the update. |
Contributor
There was a problem hiding this comment.
This kind of makes it sound like each dependency update should get its own branch.
Contributor
Author
There was a problem hiding this comment.
Fair, updated to make this a bit clearer.
mzschwartz5
reviewed
Feb 2, 2026
| - Search the codebase for any versioned deprecations and, if present, ensure a corresponding tagged issue exists for each | ||
| - Open a PR to address each item scheduled for removal in the next release, if any | ||
|
|
||
| 4. Ensure you've generated valid [end-to-end testing snapshots](../TestingGuide/README.md) against a previous release tag with `npm run test-e2e-update` |
Contributor
There was a problem hiding this comment.
Should this happen before or after updating npm packages?
Contributor
|
Looks good to me, just had one or two questions/comments. |
Contributor
Author
|
Thanks @mzschwartz5! Updated! |
mzschwartz5
approved these changes
Feb 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Refreshes the release guide with:
There are no fundamental changes to our existing processes here—This should be a documentation-only review.
Feedback welcome if anything feels less clear or people don't like my formatting 😄
Issue number and link
N/A
Testing plan
Read the updated Release Guide
Author checklist
CONTRIBUTORS.mdI have updatedCHANGES.mdwith a short summary of my changeI have added or updated unit tests to ensure consistent code coverageI have updated the inline documentation, and included code examples where relevant