pnpm-workspace.yaml

# workerd (the Cloudflare Workers runtime @cloudflare/vitest-pool-workers drives the workers test suite through) and esbuild (its bundler) both ship native binaries installed via a postinstall script -- pnpm 11 ignores those by default, so allow them explicitly. Preserved alongside this file's existing minimumReleaseAge/minimumReleaseAgeExclude content, which govern an unrelated concern (supply-chain release-age gating, not native-binary build scripts).
allowBuilds:
  esbuild: true
  workerd: true
# minimumReleaseAgeExclude is NOT honoured by `pnpm install --frozen-lockfile` (what CI runs) -- only minimumReleaseAge itself gates that path. Set low enough here that a same-day sibling-package release (documents.js/odf.js/pdf-codec) never blocks CI, matching documents.js's own pnpm-workspace.yaml precedent.
minimumReleaseAge: 60
# Bare package names (no @version), per pnpm's own documented syntax (https://pnpm.io/settings#minimumreleaseageexclude -- "webpack" exempts every version, not just one) -- these are this org's own sibling packages, published only via their own semantic-release CI with npm OIDC trusted publishing, so a version-agnostic exemption is a deliberate, low-risk carry-forward rather than the version-pinned entries this file used to need updating on every single release, matching documents.js's/pdf-codec's/odf.js's/ooxml.js's own identical convention.
minimumReleaseAgeExclude:
  - documents.js
  - ooxml.js
  - odf.js
  - document-schema.js
  - pdf-codec
  - markdown-codec
  - byte-codec