Keeping every version field in sync #

This page is for whoever releases a theme. Installations, the About page, Packagist and your users all read the version from different files. When the files disagree, nobody can tell which release is installed.

Where the version lives #

The order #

1. Choose the number from what is already published, never from memory (Checking what is already published).
2. Write it into every file of the table.
3. Commit ("Updated: Version 1.0.4", or as part of the release's last commit).
4. Tag that commit and push both.

Never tag first and bump afterwards: the tag would carry the old number, and a pushed tag is permanent (A pushed tag is permanent).

The one-minute check #

Run in the theme's folder:

grep -n "'Version'" ezinfo.php
grep -n '<version>' extension.xml
grep -n '"version"' composer.json
php -l ezinfo.php
xmllint --noout extension.xml

Expected: the same number on the first two (and the third if present), No syntax errors detected in ezinfo.php, and no output from xmllint.

When they already disagree #

• If nothing has been released with the wrong numbers yet: fix the files, then release.
• If a release went out with mismatched files: do not move its tag. Publish the next version with the files corrected and say so in its notes (When a release goes wrong).

Related pages #

• ezinfo.php, extension.xml
• Bumping the version before the tag
• Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.