Ensure ui/package.json version updates are committed during the automated release process
>>> [!note] Migrated issue
<!-- Drupal.org comment -->
<!-- Migrated from issue #3579049. -->
Reported by: [nagwani](https://www.drupal.org/user/278167)
Related to !731
>>>
<h3 id="overview">Overview</h3>
<p>The automated release process introduced in <a href="https://www.drupal.org/project/canvas/issues/3552788">Run the release process on CI</a> currently doesn't include the updated UI package.json version in the release branch. That version is normally used for cache busting query strings in the Canvas import map and for versioning of the canvas-ui, astro.client and astro.hydration libraries.</p>
<p>It causes the 1.2.0 release of Canvas to use the asset query string service instead of the Canvas version for versioning these.</p>
<p>If someone were to update Canvas from 1.2.0 to a new version without running db updates or clearing Drupal cache, stale locally cached Canvas assets could be served.</p>
<h3 id="proposed-resolution">Proposed resolution</h3>
<p>It looks like the version in package.json is updated but not committed to the release branch. We need to add git add ui/package.json to the release script so that the package.json with the updated version is included in the release branches. <a href="https://git.drupalcode.org/project/canvas/-/blob/9cc93d60e9c9e249ddca52afc4d50c049af56128/.gitlab-ci.yml#L807-814">https://git.drupalcode.org/project/canvas/-/blob/9cc93d60e9c9e249ddca52afc4d50c049af56128/.gitlab-ci.yml#L807-814</a></p>
> Related issue: [Issue #3552788](https://www.drupal.org/node/3552788)
issue