Back to GrowthDex
Growth idea action plan

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.

rare tacticfree budget

Why this can grow a startup

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.

Company 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.

Source and metric

Source: WordPress Plugin Handbook: Plugin Readmes · Browse WordPress Plugin Handbook: Plugin Readmes tactics

The public page is chosen from the Stable Tag target, while the visible download version is taken from the main plugin PHP header.

MarketplacesEngineeringOperationsstable tagrelease hygieneplugin updatesdirectory accuracy
GrowthDex operator note

When to use it

Use this when Marketplaces, Engineering, Operations is relevant to stable tag, release hygiene, plugin updates and you can run a bounded test with a free budget.

When not to use it

Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.

Founder checklist

  1. Read WordPress Plugin Handbook: Plugin Readmes and identify what is directly supported.
  2. Choose one channel context: Marketplaces, Engineering, Operations.
  3. Define the test around The public page is chosen from the Stable Tag target, while the visible download version is taken from the main plugin PHP header..
  4. Set an owner, evidence window, and stop condition before launch.

Explore the context

Product-Led GrowthMarketplacesEngineeringOperations

Related tactics

Firefox Add-ons source package with build steps before review

Prepare the reviewable source package and build instructions before submission, because Mozilla can reject or block the add-on when reviewers cannot reproduce what shipped.

rareMarketplaces, Operations, Engineering

Chrome Web Store channel inheritance on update

Treat release channels as sticky state, because Chrome publishes updates to the same channel as the last version unless you deliberately change distribution.

rareMarketplaces, Operations, QA

Chrome Web Store deferred publish window after review

Submit for review with deferred publishing when launch timing matters, then use the staged window to line up docs, support, and announcement timing before the listing goes live.

rareMarketplaces, Launches, Operations

Edge Add-ons hidden listing before review push

Keep the extension hidden while certification and setup finish, then unhide after the page, markets, and support surfaces are ready for real discovery.

rareMarketplaces, Launches, Operations

GitHub Marketplace individual owner emails in contact info

Use named individual email addresses in GitHub Marketplace contact info so pricing, payout, and review updates land with someone accountable instead of disappearing into a shared inbox.

rareMarketplaces, Operations, Brand

Google Chat app audience choice before marketplace push

Choose whether the Chat app is private or public before launch prep hardens, because Google says you cannot change that visibility setting after publish.

rareMarketplaces, Onboarding, Operations
Advisory bridge

Apply this with an operator

Choose product surfaces that compound distribution without hiding weak activation or retention.

Work with Ian