Skip to content

Automated patch release: 2.14.1 #1092

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
May 29, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 7 additions & 7 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,15 +22,15 @@ Alternatively, check the updater endpoint for the latest version at: https://hii

# Releasing Updates

To prepare a release, run the `Newfold Prepare Release` workflow. Select the release level (patch, minor or major) and the target branch (where the release PR should target, nearly always `main`), and the source branch (typically `develop`, but could be another branch for hotfix releases). The workflow will create a release branch with updated versions, build files and language files and then create a PR for review.

This plugin has version number set in 3 distinct places in 2 files:

- the plugin header info (wp-plugin-hostgator/wp-plugin-hostgator.php line 14) - this is used in the plugin php code.
- the constant HOSTGATOR_PLUGIN_VERSION (wp-plugin-hostgator/wp-plugin-hostgator.php line 34) - this is used by
WordPress.
- in the package.json version value (wp-plugin-hostgator/package.json line 5) this is used by the build step to place
the release files within a matching version directory for convenient cache busting. All 3 instances need to be
incremented in conjuction with new releases via github tagging.
(In a perfect world, we have a runner increment and/or validate this)
- the plugin header info (`wp-plugin-hostgator.php` line 14) - this is used in the plugin php code.
- the constant HOSTGATOR_PLUGIN_VERSION (`wp-plugin-hostgator.php` line 34) - this is used by WordPress.
- in the package.json version value (`package.json` line 5) this is used by the build step to place the release files within a matching version directory for convenient cache busting.

All 3 instances need to be incremented in conjuction with new releases via github tagging.

# Languages & Regions
There are some parts to the hostgator plugin that adapt depending on the region and/or language which is chosen. This not only relies on the language setting (which is set automatically on installs in HostGator Latam Brazil for example), but also on the `mm_brand` value being set to `hostgator-latam` and an additional option `hg_region` being set to `BR` in the case of Brazil. Features should all function in both US and BR setups. See the `region.cy.js` and `region-help.cy.js` cypress integration tests for example.
Expand Down
2 changes: 1 addition & 1 deletion composer.json
Original file line number Diff line number Diff line change
Expand Up @@ -86,7 +86,7 @@
"newfold-labs/wp-module-help-center": "^2.3.1",
"newfold-labs/wp-module-loader": "^1.0.12",
"newfold-labs/wp-module-marketplace": "^2.6.2",
"newfold-labs/wp-module-migration": "^1.2.3",
"newfold-labs/wp-module-migration": "^1.5.3",
"newfold-labs/wp-module-notifications": "^1.6.8",
"newfold-labs/wp-module-onboarding": "^2.6.2",
"newfold-labs/wp-module-patterns": "^2.9.1",
Expand Down
42 changes: 21 additions & 21 deletions composer.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
{
"translation-revision-date": "2025-01-10 08:42+0000",
"generator": "WP-CLI\/2.11.0",
"source": "build\/2.14.0\/index.js",
"source": "build\/2.14.1\/index.js",
"domain": "messages",
"locale_data": {
"messages": {
Expand Down
Loading