update-plugin-version

Automate PublishPress Future version updates across post-expirator.php and readme.txt.

9|12|Updated May 3, 2021
One-click install
npx skills add https://github.com/publishpress/publishpress-future --skill update-plugin-version
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-plugin-version
Source: https://github.com/publishpress/publishpress-future/tree/main/.cursor/skills/update-plugin-version
Command: npx skills add https://github.com/publishpress/publishpress-future --skill update-plugin-version

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates updating the PublishPress Future plugin version across all required files (main plugin file, readme.txt) during release, eliminating manual, error-prone edits.

Core Features & Use Cases

  • Built-in Composer command: composer set:version X.Y.Z updates all necessary files automatically.
  • Ensures version consistency across post-expirator.php and readme.txt during releases.
  • Useful during release preparation, version bumps, and when preparing patches or pre-releases.

Quick Start

Run composer set:version X.Y.Z to update all required files automatically.

Frequently Asked Questions about update-plugin-version

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

FAQPage Schema
How do I automate WordPress plugin version updates across multiple files?

Automate WordPress plugin version updates by running composer set:version X.Y.Z, which automatically synchronizes the semantic version string across post-expirator.php and readme.txt, eliminating manual edits during release preparation.

Does this version bump workflow support semantic versioning and pre-release identifiers?

Supporting semantic versioning and pre-release identifiers is a core function of the version bump workflow, enforcing strict semver formats across required plugin files whenever you issue a patch or prepare a new release.

What is the best way to update the PublishPress Future plugin version during a release?

The recommended way to update the PublishPress Future plugin version during a release is executing the standard composer set:version X.Y.Z command, which targets and updates the exact required files automatically.

Can I use this automated version bump for both patches and major WordPress plugin releases?

You can use this automated version bump for both patches and major WordPress plugin releases, as it enforces semantic version formats and updates version strings consistently across the main plugin file and readme.txt.

Why does my manual WordPress plugin version update keep causing readme.txt inconsistencies?

Manual WordPress plugin version updates cause readme.txt inconsistencies because human edits often miss required files, whereas running composer set:version X.Y.Z enforces version consistency across all specified targets automatically.