[shivanee-p]

Fixes release failures for by aligning their prepare, compile, and postpack scripts with the rest of the monorepo packages.

Key Changes:

• Updated "prepare" from "npm run compile-protos && npm run compile" to "npm run compile".
• Updated "compile" from "tsc -p . && cp -r protos build/ && minifyProtoJson" to "tsc -p . && cp -r protos build/".
• Added "postpack": "minifyProtoJson".

[gemini-code-assist]

Code Review

This pull request updates the build and packaging scripts across multiple package.json files by removing the compile-protos step from the prepare script and moving the minifyProtoJson task from the compile script to a postpack lifecycle script. Feedback from the reviewer correctly highlights a critical issue: because postpack runs after the tarball has already been generated, any files minified during this step will not be included in the published npm packages. To ensure the minified proto JSON files are packaged correctly, the prepack lifecycle script should be used instead of postpack.

[gemini-code-assist]

In npm, the postpack lifecycle script runs after the tarball has already been generated and packed. Any file modifications performed in postpack (such as running minifyProtoJson to minify the proto JSON files in the build directory) will not be included in the packed tarball that gets published to npm.

To ensure that the published packages actually contain the minified proto JSON files (thereby keeping the package size small), you should use the prepack lifecycle script instead of postpack.

Suggested change

	"postpack": "minifyProtoJson",
	"prepack": "minifyProtoJson",

[gemini-code-assist]

While reviewing the scripts here, note that the adjacent postpack script (on line 62) also runs minifyProtoJson after the tarball has already been packed. This means the minified files are not included in the published package.

Please consider changing postpack to prepack here as well to ensure the minified files are correctly included in the published ESM packages.