The Composer branch-alias in composer.json needs to map dev-main/dev-master to the next minor development version after the latest release. This is easily forgotten during releases.

Changes

Workflows

• reusable-check-branch-alias.yml - Core logic to detect outdated branch aliases and create PRs
• check-branch-alias.yml - Caller workflow, triggers on release or on-demand
• Updated sync-workflows.yml to distribute to all WP-CLI repos

Logic

• Triggers automatically when a release is marked as released
• Filters git tags to stable releases only: v[0-9]*.[0-9]*.[0-9]*
• Strips pre-release (-alpha) and build metadata (+build.123)
• Calculates expected alias: v2.12.0 → 2.13.x-dev
• Uses Composer commands to read and update branch-alias values
• Handles missing extra.branch-alias structure in composer.json
• Creates PR when current alias doesn't match expected

Composer Integration

• Uses composer config extra.branch-alias.<key> to read current value
• Uses composer config extra.branch-alias.<key> <value> to update value
• Automatically creates the structure if it doesn't exist

Example

After releasing v2.12.0, if composer.json contains:

{
  "extra": {
    "branch-alias": {
      "dev-main": "2.12.x-dev"
    }
  }
}

Workflow updates to "2.13.x-dev" and creates PR with explanation.

• Fixes Add GHA workflow for checking branch alias #6

• Fixes Add GHA workflow for checking branch alias #6

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.