project-release

Automate monorepo releases by orchestrating pre-flight checks, semantic version bumps, changelog generation from conventional commits, and atomic git tagging. This coordinates synchronized changes across multiple apps and packages to ensure a strict, auditable release pipeline.

Yes, the release workflow is platform-agnostic and supports push-to-main deployments on Railway, Vercel, Render, and Fly.io. It triggers CI/CD deployments through atomic commit and tag creation, coordinating changes across web frontends, APIs, and worker services.

Force a semantic version bump by providing a specific bump type argument like patch, minor, or major when triggering the release command. The automation applies the forced version update alongside standard pre-flight checks and changelog generation.

The best way to coordinate synchronized monorepo releases is using an automated pipeline that captures pre-flight state, detects changes across apps, applies version bumps, and creates atomic git tags. This ensures all web, API, and worker services deploy in unison.

Changelog generation works by parsing conventional commit messages automatically during the release process. It creates an auditable log of changes before applying version bumps and pushing atomic tags to trigger downstream CI/CD platform deployments.

Pre-flight checks are needed to capture repository state and detect changes across apps before versioning. They act as strict quality gates to prevent error-prone manual releases and ensure atomic tags only push verified, synchronized updates to deployment platforms.