prepare-changelog-release

Name: prepare-changelog-release
Availability: InStock
Author: PublishPress

Move the current version and date into the Unreleased section of CHANGELOG.md.

9|12|Updated May 3, 2021

Search Tags:#automation #workflow #changelog #versioning #plugin #release-management #wordpress

Ready to run

npx skills add https://github.com/publishpress/publishpress-future --skill prepare-changelog-release

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prepare-changelog-release
Source: https://github.com/publishpress/publishpress-future/tree/main/.cursor/skills/prepare-changelog-release
Command: npx skills add https://github.com/publishpress/publishpress-future --skill prepare-changelog-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates updating the CHANGELOG.md Unreleased section by inserting the current plugin version and date, eliminating manual edits during releases.

Core Features & Use Cases

Reads the current plugin version from the plugin header
Updates the Unreleased section with the [VERSION] and date in the required format
Creates a fresh empty [Unreleased] section at the top for future entries

Quick Start

Run the prepare-changelog-release skill to update the Unreleased section with the latest version and date.

Frequently Asked Questions about prepare-changelog-release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate changelog updates for WordPress plugin releases?▼

To automate changelog updates for a WordPress plugin release, you run a process that reads the plugin version from the main file header and rewrites the Unreleased block in CHANGELOG.md with that version and date.

What is an Unreleased section in a changelog used for?▼

An Unreleased section in a changelog is used to collect new changes before a versioned release. During release workflows, the current version and date are inserted into this block, and a fresh empty Unreleased section is created at the top for future entries.

How does a release workflow read the current version from a WordPress plugin?▼

A release workflow reads the current version from a WordPress plugin by parsing the main plugin file header. It uses this extracted version number to update the CHANGELOG.md file during the automated release process.

Can I use this changelog automation for non-WordPress projects?▼

This changelog automation is specifically built for WordPress plugin release workflows and relies on reading the version from the main plugin file header. Using it for non-WordPress projects is not supported unless they follow the exact same plugin header format.

What's the best way to maintain a consistent changelog format across plugin versions?▼

The best way to maintain a consistent changelog format across plugin versions is to automate the process of moving the current version and date into the Unreleased section during releases, ensuring the CHANGELOG.md follows the project's required format.

Why does my changelog Unreleased section need to be rewritten during a release?▼

Your changelog Unreleased section needs to be rewritten during a release to insert the current plugin version and date, creating a finalized entry for that release and establishing a fresh empty Unreleased block at the top for future development changes.