Skip to content

Releasing

Nick Cernis edited this page Mar 31, 2026 · 14 revisions

Release the WP.org plugin version (updates from WP.org, deployed using SVN)

  1. Create a branch release/x.x.x off develop.
  2. Bump the plugin version.
  3. Open a PR to develop. CI/CD will fail if the version isn't bumped in the right places. (If you have already merged version bumps to develop, you can skip steps 1-3.)
  4. Draft a new release, tagging the commit you want to release in the 1.2.3 format.
  5. Publish that release.
  6. Wait for CI/CD to deploy to wp.org svn.
  7. You will need to log in at https://wordpress.org/plugins/genesis-custom-blocks (talk to your team for access if needed), click the "This plugin has a pending release that requires confirmation" banner on the plugin page, and approve the release.

Release the WPE plugin version (updates from WPE servers)

  1. Download the WPE zip and the info.json files created under the CircleCI 'zip' artifacts tab for the tagged release commit. Important to use the zip from the WPE folder, not the WP.org one (which is for testing purposes only).
  2. Use the "Internal Plugin Release" pipeline in #wpe-wordpress-plugins in WPE Slack.

Release Genesis Custom Blocks Pro

  1. See release notes for Genesis Custom Blocks Pro. It will automatically pull in the latest GCB free version from WP.org once that is live.