fix(ci): use npm pkg delete instead of set to empty string

[carlos-alm]

Summary

• npm pkg set scripts.prepublishOnly="" fails on newer npm versions — the empty "" is not recognized as a valid key=value pair
• Replace with npm pkg delete scripts.prepublishOnly which removes the key entirely (same effect, works across all npm versions)

Test plan

• Merge and verify the publish workflow succeeds on next push to main

[greptile-apps]

Greptile Summary

Fixes publish workflow compatibility with newer npm versions by replacing npm pkg set scripts.prepublishOnly="" with npm pkg delete scripts.prepublishOnly. The empty string syntax is not recognized as valid in recent npm versions, causing the workflow to fail. The delete command removes the key entirely, achieving the same goal (preventing tests from running during publish) while working across all npm versions.

Confidence Score: 5/5

• Safe to merge - simple CI fix with no production code changes
• Single-line change in CI workflow that fixes a documented npm compatibility issue. The npm pkg delete command is the canonical way to remove package.json fields and works across all npm versions, whereas setting to empty string fails on newer npm versions. No impact on runtime code.
• No files require special attention

Important Files Changed

Filename	Overview
.github/workflows/publish.yml	Replaced npm pkg set scripts.prepublishOnly="" with npm pkg delete scripts.prepublishOnly to fix compatibility with newer npm versions

_{Last reviewed commit: 09b07c5}

[greptile-apps]

_{1 file reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}