Skip to content

Latest commit

 

History

History
34 lines (29 loc) · 1.73 KB

DEVELOPERS.md

File metadata and controls

34 lines (29 loc) · 1.73 KB

Developers

Publishing a new version

This WordPress plugin is hosted on Gibhub pages:

  1. Create a new branch based on the version number, e.g. v2.0.7
  2. Implement and commit any improvements to the plugin (e.g. bug fixes or new features)
  3. Update the version numbers in these files:
    1. envato-market.php in the comment at the top, and in the ENVATO_MARKET_VERSION const
    2. docs/dist/update-check.json
    3. package.json
    4. readme.txt stable tag
    5. (Do not edit readme.md or envato-market.pot these files are auto generated)
  4. Update the changelog in these files:
    1. readme.txt add a new changelog entry for version number
    2. docs/dist/update-check.json add a changelog entry like: <h4>v2.0.7</h4><ul><li>Fix global notice hidden bug</li></ul>
  5. Update the "tested up to" tag in envato-market.php e.g. Tested up to: 5.9
  6. Commit the changes ^^
  7. Run the build script:
    1. npm install
    2. npm run deploy
    3. This updates a few files including readme.md and the new zip file in docs/dist/envato-market.zip
  8. Commit the changes ^^
  9. Open a PR based on this branch
  10. Get approval and merge the PR
  11. Publish a new github release https://github.com/envato/wp-envato-market/releases/new to match the new version number.
  12. The update will now be live for everyone

For local testing and development, see the market wiki page for the Envato WordPress Plugin, under the systems menu