# WordPress plugin Stable Tag, tag folder, and PHP version stay in sync

> Align the trunk Stable Tag, the matching `/tags/` release, and the plugin header version before you touch the public plugin page.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/wordpress-plugin-stable-tag-tag-folder-and-php-version-stay-in-sync/
- Source: [developer.wordpress.org](https://developer.wordpress.org/plugins/wordpress-org/how-your-readme-txt-works/)
- GrowthDex source hub: [WordPress Plugin Handbook: Plugin Readmes](/sources/wordpress-plugin-handbook-plugin-readmes-developer-wordpress-org/)
- Last checked: 2026-06-05T07:25:00Z
- Rarity: rare
- Budget: free
- Channels: Marketplaces, Engineering, Operations
- Stages: stable tag, release hygiene, plugin updates, directory accuracy


## Why this can grow

WordPress parses the Stable Tag in trunk first, then reads the referenced tag folder for the public page, while the download button version comes from the plugin's main PHP file. That split means one casual mismatch can create a stale listing, broken updates, or a page that claims one version while shipping another. Teams often treat this as release housekeeping. In practice it is storefront hygiene because the directory page and the updater depend on the triad staying aligned.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where wordpress plugin stable tag, tag folder, and php version stay in sync can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Marketplaces and Engineering channel.
3. Use the evidence from developer.wordpress.org to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

WordPress says a Stable Tag of `1.2.3` makes the directory parse `/tags/1.2.3/`, warns that the tag folder readme must also carry the correct Stable Tag to avoid update issues, and notes that the visible download version comes from the main plugin PHP file.

## Adjacent tactics in the same lane

- [WordPress plugin readme short description under 150 characters](/growth-ideas/wordpress-plugin-readme-short-description-under-150-characters/) - same source, 1 shared channel
- [WordPress plugin Installation section carries the post-install work](/growth-ideas/wordpress-plugin-install-section-carries-the-post-install-work/) - same source, 1 shared channel
- [Firefox Add-ons source package with build steps before review](/growth-ideas/firefox-add-ons-source-package-with-build-steps-before-review/) - 3 shared channels
- [HubSpot agent tool scope only for the context you use](/growth-ideas/hubspot-agent-tool-scope-only-for-the-context-you-use/) - 2 shared channels

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The plugin directory page should survive the first update](/blog/the-plugin-directory-page-should-survive-the-first-update/) - marketplaces, brand trust, SEO

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.