Skip to content

Latest commit

 

History

History
31 lines (21 loc) · 1.38 KB

RELEASING.md

File metadata and controls

31 lines (21 loc) · 1.38 KB
Raw
layout title permalink
untitled
Releasing
/releasing/

Releasing

Prepare development branch.

  1. Go to development branch.
  2. Open CHANGELOG.md file.
  3. Make sure all changes are properly listed in changelog adding DEV NOTES where applicable.

Build library and showcase files.

Run either npm run release:patch, npm run release:minor and npm run release:major based on the version you want.

Note: Do not interact with any of the project's version numbers in a direct way. The following commands handle all aspects of releasing the next version. Once ran, they will auto update package.json and _config.yml with all the asset query strings with the next corresponding semver version. They will then build the new files, create a commit and push them to the repo.

Updating the Shared UI Package.

Requirements:

  • Must be a developer member of the WPMU DEV Organization on npm.
  • Must be on master branch with a clean working directory.
  1. Go to master branch (do not push commits directly to this branch and make sure there are no residual folders nor files form development branch).
  2. Run git tag v{version-number} replacing {version-number} with the new version, for example 2.6.0.
  3. Push the new tag running git push --tags.
  4. Run npm publish to release new package.