myco:monorepo-release-engineering

You coordinate multi-package npm workspace releases by automating versioning, publishing, and tag workflows across the workspace. This ensures consistent tag-driven deployments and prevents silent failures across all published packages in the monorepo.

Tag-driven release publishing uses repository tags to trigger per-package CI publishing within an npm workspace. This mechanism automates version updates and deployments for individual packages whenever a new tag is pushed to the repository.

First-time trusted publishing is bootstrapped during per-package CI publishing setup. This process configures trusted publishers for the package, allowing automated pipelines to publish to npm without requiring manually stored authentication tokens.

Yes, Node 22 is required to run monorepo release engineering workflows. The workspace also requires a root manifest, per-package manifests, and specific wiring steps to properly add and publish new packages.

Adding a publishable package requires four wiring steps and a per-package manifest. This setup integrates the new package into the root workspace manifest, enabling it for CI publishing, tag-driven releases, and workspace bootstrap consistency.

Worktree delivery gates prevent silent failures in monorepo release pipelines by enforcing diagnostics and safeguards. These gates validate workspace bootstrap consistency and verify publishing states before tag-driven releases finalize.