Update README.md

Remove outdated step.
CesiumGS · May 1, 2024 · fb4a832 · fb4a832
1 parent 55ede3c
commit fb4a832
Showing 1 changed file with 1 addition and 2 deletions.
diff --git a/Documentation/Contributors/ReleaseGuide/README.md b/Documentation/Contributors/ReleaseGuide/README.md
@@ -10,8 +10,7 @@ There is no release manager; instead, our community shares the responsibility. A
 2. If one or more dependencies are outdated, checkout a new branch and run `npm install <packagename>@latest` for each package to increment the version.
 3. Verify each update. If an update can be resolved, open a PR with your changes. If an update is incompatible, open an issue.
 4. Check the [`priority - next release` issues and PRs](https://github.com/CesiumGS/cesium/labels/priority%20-%20next%20release). If there are any outstanding items, post a message to the `#cesiumjs` channel in Slack to figure out what needs to be addressed before we can release.
-5. Merge [`cesium` to `cesium-analytics`](https://github.com/CesiumGS/cesium-analytics/wiki/Merging-between-Cesium-Analytics-and-CesiumJS) and address any conflicts. Doing this before the release helps detect problems sooner.
-6. Ensure you've generated valid [end to end testing snapshots](../TestingGuide/README.md) against a previous release tag with `npm run test-e2e-update`.
+5. Ensure you've generated valid [end to end testing snapshots](../TestingGuide/README.md) against a previous release tag with `npm run test-e2e-update`.
 
 ## Release testing and packaging