Automate forepaw releases by updating changelogs, versions, docs, and CI steps.
npx skills add https://github.com/aviraccoon/forepaw --skill forepaw-release
Please help me install this Agent Skill. Skill: forepaw-release Source: https://github.com/aviraccoon/forepaw/tree/main/.agents/skills/forepaw-release Command: npx skills add https://github.com/aviraccoon/forepaw --skill forepaw-release
Releasing a new forepaw version involves coordinating changelog updates, version bumps, release metadata, and docs across the project to prepare a clean, reproducible release.
Follow the eight-step release workflow: update CHANGELOG.md, bump the base version in Sources/Forepaw/Version.swift, update docs, build and test, commit the changes, tag the release, push to git, and rely on CI to publish the artifact and update packaging.
High-intent search queries and answers about installing and using this skill.
Automating a macOS package release involves coordinating changelog entries, version bumps in source files, and documentation updates to prepare a reproducible, tagged Git release. This workflow updates CHANGELOG.md and Version.swift, then builds, tests, commits, and tags the project.
Preparing a reproducible release artifact and a tagged Git version requires an eight-step workflow: update CHANGELOG.md, bump the base version, update docs, build, test, commit, tag, and push. CI then publishes the artifact and updates packaging.
Coordinating release metadata and CI steps improves open-source release workflows by automating build, test, commit, tag, and push operations. This ensures clean, reproducible releases across macOS projects by propagating version changes to docs and release notes.
Yes, you can use this automated release workflow for software maintenance and package publishing across macOS projects. It coordinates version bumps, documentation updates, and CI-driven binaries to produce clean, reproducible release artifacts.
The best way to manage release notes and version propagation is to automate the update of CHANGELOG.md with versioned entries, bump the base version in Version.swift, and propagate those changes to docs and release notes before tagging and pushing.
alanbenUpdate README.md, CHANGELOG.md, LICENSE, and CONTRIBUTING.md before commits or releases.
drvossAutomates version tagging, changelog generation, GitHub Releases, and artifact publishing to registries.
barefootfordAutomate ButterCut releases with version bumps, changelog, git tags, gem build, and GitHub release.
baekenoughBump npm package versions and update changelogs with optional git tags.
