From 58a2a04c4a49013bf2906f4d238c82d29b0cfa24 Mon Sep 17 00:00:00 2001 From: jjspace <8007967+jjspace@users.noreply.github.com> Date: Thu, 29 Aug 2024 16:20:09 -0400 Subject: [PATCH 1/2] update packages --- package.json | 2 +- packages/engine/package.json | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/package.json b/package.json index e3a813f1e08..e61b91c6cef 100644 --- a/package.json +++ b/package.json @@ -57,7 +57,7 @@ "devDependencies": { "@playwright/test": "^1.41.1", "chokidar": "^3.5.3", - "cloc": "^2.0.0-cloc", + "cloc": "^2.2.0-cloc", "compression": "^1.7.4", "esbuild": "^0.23.0", "eslint": "^9.1.1", diff --git a/packages/engine/package.json b/packages/engine/package.json index bc74fc1d261..1ef8d540dc3 100644 --- a/packages/engine/package.json +++ b/packages/engine/package.json @@ -32,7 +32,7 @@ "./Specs/**/*" ], "dependencies": { - "@tweenjs/tween.js": "^23.1.1", + "@tweenjs/tween.js": "^25.0.0", "@zip.js/zip.js": "^2.7.34", "autolinker": "^4.0.0", "bitmap-sdf": "^1.0.3", From 49e9af94ed50ef2a1b6de0f8b5209aaf167200a3 Mon Sep 17 00:00:00 2001 From: jjspace <8007967+jjspace@users.noreply.github.com> Date: Thu, 29 Aug 2024 16:39:37 -0400 Subject: [PATCH 2/2] add note about new dependency label --- Documentation/Contributors/ReleaseGuide/README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Documentation/Contributors/ReleaseGuide/README.md b/Documentation/Contributors/ReleaseGuide/README.md index 43cb9175713..9730b888ff8 100644 --- a/Documentation/Contributors/ReleaseGuide/README.md +++ b/Documentation/Contributors/ReleaseGuide/README.md @@ -8,7 +8,7 @@ There is no release manager; instead, our community shares the responsibility. A 1. Check for any outdated dependencies with `npm outdated`. 2. If one or more dependencies are outdated, checkout a new branch and run `npm install @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. +3. Verify each update. If an update can be resolved, open a PR with your changes. If an update is incompatible, open an issue. Check the [`dependencies` label](https://github.com/CesiumGS/cesium/issues?q=is%3Aissue+is%3Aopen+label%3Adependencies) for any open issues pinning versions. 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. Ensure you've generated valid [end to end testing snapshots](../TestingGuide/README.md) against a previous release tag with `npm run test-e2e-update`. @@ -24,8 +24,8 @@ There is no release manager; instead, our community shares the responsibility. A 6. Update the Cesium ion demo token in `Ion.js` with a new token from the CesiumJS ion team account with read and geocode permissions. These tokens are named like this: `1.85 Release - Delete on November 1st, 2021`. Delete the token from 2 releases ago. 7. Update the ArcGIS Developer API key in `ArcGisMapService.js` with a new API key from the CesiumJS ArcGIS Developer account. These API keys are named like this: `1.85 Release - Delete on November 1st, 2021`. Delete the API key from the last release. 8. Proofread [`CHANGES.md`](../../../CHANGES.md) with the date of the release. Adjust the order of changes so that prominent/popular changes come first. Ensure each change is in the section for the relevant workspace. -9. Based on `CHANGES.md`, update each workspace version following the rules of [semantic versioning](https://semver.org/), e.g., - `npm version minor -w @cesium/engine --no-git-tag-version`. +9. Based on `CHANGES.md`, update each workspace version following the rules of [semantic versioning](https://semver.org/), e.g., + `npm version minor -w @cesium/engine --no-git-tag-version`. Changes in one workspace may require version updates in other workspaces that depend on it. For example, if `CHANGES.md` reports changes in `@cesium/engine` only, the version for `@cesium/widgets` should also be incremented to reflect the updated dependency. 10. Update the version in `package.json` to match, e.g. `1.115.0` -> `1.116.0`. 11. Commit these changes.