July 2025 Summaries

Pnpm version 10, released earlier this year, has made significant strides in improving hermeticity, performance, and reliability, aligning better with Bazel-based workflows utilizing rules_js, as evidenced by the passing of regression tests with its 10.11.1 release. Key changes include requiring explicit declaration of packages needing build steps in package.json, enhancing determinism and hermeticity, and switching to more secure SHA256 hashing in the pnpm-lock.yaml file to align with Bazel's integrity checks. The introduction of pnpm.neverBuiltDependencies in version 10.1 helps manage install warnings, while configuration changes such as updated default hoisting and ignoring NODE_ENV on install may affect user experience during upgrades. Additionally, the catalogs feature from pnpm v9.5, which consolidates version numbers in large monorepos, remains a valuable tool, supporting seamless integration with rules_js without altering the lockfile format. Overall, pnpm v10 continues to support more deterministic builds, solidifying its position as a suitable choice for Bazel and rules_js ecosystems.

The text discusses the concept of Continuous Delivery (CD) and its role in software deployment pipelines, distinguishing it from Continuous Integration (CI) and deployment processes. It suggests treating CD as the stage where built artifacts are uploaded to a known repository, emphasizing the importance of separating responsibilities among CI, CD, and deployment systems. The text further explores the notion of "deliverable" artifacts, which should include both the binary or files and the logic for uploading them. Various methods for identifying and delivering only "changed" targets are outlined, with a preference for empirical determination due to the limitations of predictive tools like bazel-diff and target-determinator. The process of determining deliverable targets involves using a hashing mechanism to avoid redundant deliveries by comparing current and previously delivered hashes. Additionally, the document touches on the debugging process for determining changes in deliverables and the execution of delivery using Bazel with stamping enabled.