Publisher374 passed build/tests/lint, then clean-and-install deleted the lockfile and resolved incompatible Node typings. The final npm publish lifecycle failed with50 TypeScript parser errors. Use npm ci followed by the existing prepublishOnly build so release packaging uses the same locked dependency graph that passed validation.
Validation: the real corrected clean-and-install and npm publish --dry-run lifecycle both pass on Node24.21/npm11.19; @types/node remains24.3.0 and TypeScript4.9.5. The committed lockfile is byte-for-byte unchanged; diff check and independent review pass. Prior48 application tests passed on this same source/locked graph; normal PR CI runs them again. No dependencies changed, lifecycle was not bypassed, and dry-run is not claimed as authentication or publication proof.
Publisher374 passed build/tests/lint, then clean-and-install deleted the lockfile and resolved incompatible Node typings. The final npm publish lifecycle failed with50 TypeScript parser errors. Use npm ci followed by the existing prepublishOnly build so release packaging uses the same locked dependency graph that passed validation.
Validation: the real corrected clean-and-install and npm publish --dry-run lifecycle both pass on Node24.21/npm11.19; @types/node remains24.3.0 and TypeScript4.9.5. The committed lockfile is byte-for-byte unchanged; diff check and independent review pass. Prior48 application tests passed on this same source/locked graph; normal PR CI runs them again. No dependencies changed, lifecycle was not bypassed, and dry-run is not claimed as authentication or publication proof.
Refs QRun-IO/qqq#914.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Publisher374 passed build/tests/lint, then clean-and-install deleted the lockfile and resolved incompatible Node typings. The final npm publish lifecycle failed with50 TypeScript parser errors. Use npm ci followed by the existing prepublishOnly build so release packaging uses the same locked dependency graph that passed validation.
Validation: the real corrected clean-and-install and npm publish --dry-run lifecycle both pass on Node24.21/npm11.19; @types/node remains24.3.0 and TypeScript4.9.5. The committed lockfile is byte-for-byte unchanged; diff check and independent review pass. Prior48 application tests passed on this same source/locked graph; normal PR CI runs them again. No dependencies changed, lifecycle was not bypassed, and dry-run is not claimed as authentication or publication proof.
Refs QRun-IO/qqq#914.