Skip to content

Releases & Versioning

Complete Release Process

Terminal
# Get latest changes
git checkout develop && git pull

# Deploy documentation
mkdocs build
# FTP upload site/ to https://genesis.mivareadythemes.com/docs/

# Deploy latest Webpack build
pnpm run bootstrap
cd generator-quickstart/app/templates/themes/genesis && pnpm run build live/production
# FTP Upload `generator-quickstart/app/templates/themes/genesis/public/` to `mm5/themes/genesis/branches/production/public/`

# Deploy latest Miva Templates
# cd repo root
pnpm run framework_export
# Update paths in generator-quickstart\app\templates\miva-templates\templates\framework_export.mvt to point to correct branch path
mmt checkout genesis/live/production -z
mmt push --notes="{{commit message and hash from last git commit}}"
# Log into Miva Admin an create a framework, download the pkg file, and commit it

# Misc. Optional Steps
# Optionally, delete all C&L Components/Layouts and import them from the repo
# Optionally, create the `export-provisioning` page and save a copy of it's xml to the repo
# Optionally, `$ cd optional-extensions/wordpress-theme && pnpm run build`

# Finish the Release
# Follow the "Publishing to NPM" steps below
# Commit your changes and open a release PR

Publishing to NPM

  1. Bump the package(s) you updated.
    • cd package/YOUR_PACKAGE && pnpm version [major|minor|patch|[premajor --preid alpha|preminor --preid alpha|prepatch --preid alpha|prerelease --preid alpha]
  2. Review which packages were updated through git after the version bump.
    • If your package is a dependency for other packages it will automatically their reference to the latest version. This maintains the workspace linking.
    • If this happens you will want to also bump the affected packages as well. Follow through this pattern until all packages are updated to the next version.
  3. Commit all changes.
  4. Run the correct publish command for the type of release you are doing (pre-release or release).

Updating the framework_export.mvt

  1. cd mvps-genesis
  2. pnpm run build --prefix generator-quickstart/app/templates/themes/genesis
  3. pnpm run framework_export
    1. You may need to update the paths in generator-quickstart\app\templates\miva-templates\templates\framework_export.mvtto point to correct branch path
  4. git commit -m "Updated framework_export with latest build files"
  5. Update the Miva Store's framework_export page with updated contents of generator-quickstart/app/templates/miva-templates/framework_export.mvt
    1. For example, mmt checkout REMOTE_NAME --reinitialize && mmt push --notes="ran framework_export
  6. Create a new framework-pkg file from the Miva Store
  7. Commit the new framework pkg file in the mvps-genesis repo.

WordPress Versioning and Build Process

Anytime the WordPress codebase is updated before submitting a new PR with the changes the version should be bumped accordingly along with a new build.

Build steps

  1. Update style.css with new Version: X.X.X on line 7.
  2. Update package.json with new "version": "X.X.X" on line 3.
  3. Update wordpress-theme.md links. Example: [genesis-wordpress-theme-vX.X.X.zip](genesis-wordpress-theme-vX.X.X.zip) - Do not change URL path.
  4. In the mvps-genesis/optional-extensions/wordpress-theme directory run pnpm run build to output new build in the builds directory.

Path to files

# style.css
wordpress-theme/blog-server/httpdocs/blog/wp-content/themes/genesis-wordpress-theme/style.css

# package.json
optional-extensions/wordpress-theme/package.json

# wordpress-theme.md
docs/features/optional-extensions/wordpress-theme.md

# genesis-wordpress-theme-vX.X.X.zip
optional-extensions/wordpress-theme/build/genesis-wordpress-theme-vX.X.X.zip