release

Trigger a GitHub Actions release workflow by dispatching the release.yml file with a selected semantic version bump (patch, minor, or major). This automates version bumping, branch creation, tagging, and package publishing.

During an automated package publishing pipeline, the system bumps versions across multiple packages, creates necessary branches and PRs, tags the new version, and publishes artifacts. This removes manual coordination and reduces mistakes during software releases.

Yes, you can use a GitHub Actions workflow dispatch to cut a release across multiple packages. By triggering the release.yml workflow with a specified semantic version bump, the pipeline handles multi-package versioning, tagging, and artifact publishing automatically.

To prevent accidental semantic version bumps during a CI CD release, the workflow requires input validation and a confirmation step before proceeding. You must explicitly validate the bump type (patch, minor, major) to ensure safe execution.

The GitHub Actions release workflow returns actionable verification guidance and a reminder of the pipeline duration after dispatch. While exact times vary by project size, the workflow runs continuously to complete versioning, tagging, and artifact publishing.