Cut a new release from the main branch with versioning, changelog generation, and git tagging.
npx skills add https://github.com/ziggy42/epsilon --skill release-ziggy42
Please help me install this Agent Skill. Skill: release Source: https://github.com/ziggy42/epsilon/tree/main/.skills/release Command: npx skills add https://github.com/ziggy42/epsilon --skill release-ziggy42
This skill guides teams through cutting a release from the main branch, ensuring version accuracy, changelog generation, and proper git tagging, while enforcing a clean working tree prior to release.
Cut a new release from the main branch by updating the version, generating the changelog, and tagging the release.
High-intent search queries and answers about installing and using this skill.
You can automate git tagging and changelog generation by cutting a new release from the main branch. This process updates your project version, drafts a user-facing changelog from recent commits, and pushes the new tag to the remote.
The best way to cut a clean release is using an automated workflow that enforces a strict clean working tree prior to release. This ensures version integrity by consistently updating project files before committing changes and creating a git tag.
Yes, the release automation process strictly requires a clean working tree before cutting a release. Enforcing this guardrail prevents uncommitted changes from being included in the new version tag.
Changelog generation works by automatically drafting a user-facing changelog from commits made since the last release. This ensures the CHANGELOG.md accurately reflects all updates when the new version is tagged.
Yes, you can use this release workflow to update specific version files like epsilon/version.go automatically. It commits these version changes, creates a git tag, and pushes everything to the main remote origin.
The main precaution enforced is verifying a clean working tree before starting the release process. This guardrail stops uncommitted or untracked files from accidentally being included in the tagged release commit.
ahandselSynchronizes local Git feature branches with the remote main branch.
mgamadeusBump composer.json versions, commit, and create git tags for Packagist releases.
joaquimscostaAnalyze git commit history to generate formatted changelogs with version bumps.
Lionad-MorotarGuide software releases from planning to semantic versioning and Git tagging.
