This release adds new options to the release publish command for more flexible release automation. You can now prevent GitHub from marking a release as latest with --no-latest (useful for backport releases), and automatically commit staged changes before tagging with --commit.
🚀 Features
Section titled “🚀 Features”New --no-latest and --commit options for release publishing
Section titled “New --no-latest and --commit options for release publishing”Dec 18, 2025 · @mavam, @claude
The release publish command now supports two new options for smoother release
automation:
--no-latestprevents GitHub from marking the release as latest, useful for backport releases to older branches--commitcommits staged changes before creating the tag, eliminating a manual step in release workflows. The commit message defaults toRelease {version}but can be customized via--commit-messageor therelease.commit_messageconfig option.