ship

Automating software release verification and changelog generation requires orchestrating pre-land lane checks, commit parsing, and version tagging. This skill manages the entire release process to ensure quality control and maintain version consistency.

Cutting a structured release with risk assessment involves conducting pre-release verification, evaluating potential issues, generating a changelog, and tagging the version. This approach ensures quality control by requiring maintainer approval at critical steps.

Yes, automated release automation works without additional dependencies. This skill operates independently using scripts to orchestrate the release workflow, from pre-land lane verification to trunk advancement.

Generating a changelog from commits since the last release is handled automatically during the release cut. The skill parses commit history to create the changelog, ensuring documentation aligns with version control updates.

Maintainer approval is needed at each critical step of the release automation process. This requirement ensures human oversight during verification, risk assessment, changelog creation, and version tagging to prevent unauthorized releases.

Yes, you can use scripts to advance the trunk after version tagging. The release workflow tags the release and automatically advances the trunk to maintain version consistency across the software development project.