publish

Automating GitHub release workflows after feature approval involves pushing the branch, creating a pull request, waiting for CI, merging, tagging a version, and updating the changelog. This skill coordinates that entire sequence to ensure consistent releases.

The best way to update CHANGELOG.md and tag versions after a merge is to run an automated workflow that squashes the pull request, applies a new package.json version tag, and appends the changes to the changelog in one continuous step.

No, the publish workflow does not strictly require a package.json file for versioning. It applies optional package.json versioning, meaning it can tag releases and update changelogs even if your repository uses a different versioning scheme.

Yes, you can use this release automation skill if your repository has no CI checks configured. The workflow waits for CI only if present, allowing you to proceed directly to merging and tagging if no continuous integration checks are detected.

Resetting workflow-state.json to the V2 schema after merging happens automatically at the end of the release process. Once the feature branch is merged, the workflow updates feature-list.json and resets the state file to prepare for the next cycle.

After a pull request is merged in GitHub, the feature branch is deleted. The release workflow uses a squash merge to integrate the changes and then automatically deletes the remote branch to keep the repository clean.