Resolve #3577469 "Add possibility to"

Ahmad Khalilrequested to merge
issue/ai-3586465:3586465-release-script-does-not-set-the-version-for-json-schema-editor into 1.4.x

Issue #3586465: Release script does not set the version for json-schema-editor.

Problem

scripts/tag-release.sh runs npm version "$TAG" against ui/json-schema-editor (via build_dir), which mutates both package.json and package-lock.json. The first git add -f block staged only ui/json-schema-editor/dist, so the version bump was silently dropped from the release commit — unlike mdxeditor and default-tools-editor, which stage all three paths.

Fix

Add the two missing paths to the git add -f list:

   ui/default-tools-editor/dist \
+  ui/json-schema-editor/package.json \
+  ui/json-schema-editor/package-lock.json \
   ui/json-schema-editor/dist

The reset-to-dev block at the bottom of the script already handles these files correctly, so no change there.

Merge request reports