Release version 1.1.6 #273

This issue is for tracking changes for the 1.1.6 release. Target release date: September 2026.

Partially triggering due to #271 failing on the WPORG readme updater action.

Pre-release steps

• fix test failure and merge Bump WordPress tested-up-to 7.1, min to 6.9 #272
• Review and merge Bump the npm_and_yarn group across 1 directory with 17 updates #264
• update docs Docs: Note cross-domain limitations for JWT token in readme/FAQ. #252

Release steps

• Branch: Starting from develop, cut a release branch named release/1.1.6 for your changes.
• Version bump: Bump the version number in maps-block-apple.php, readme.txt, package.json and package-lock.json if it does not already reflect the version being released. Update both the plugin "Version:" property and the plugin MAPS_BLOCK_APPLE_VERSION constant in maps-block-apple.php.
• Changelog: Add/update the changelog in CHANGELOG.md and readme.txt.
• Set release date in CHANGELOG.md and readme.txt.
• Props: update CREDITS.md with any new contributors, confirm maintainers are accurate.
• New files: Check to be sure any new files/paths that are unnecessary in the production version are included in .distignore.
• Readme updates: Make any other readme changes as necessary. README.md is geared toward GitHub and readme.txt contains WordPress.org-specific content. The two are slightly different.
• Merge: Make a non-fast-forward merge from your release branch to develop (or merge the pull request), then do the same for develop into trunk, ensuring you pull the most recent changes into develop first (git checkout develop && git pull origin develop && git checkout trunk && git merge --no-ff develop). trunk contains the stable development version.
• Push: Push your trunk branch to GitHub (e.g. git push origin trunk).
• Compare trunk to develop to ensure no additional changes were missed.
• Test the pre-release ZIP locally by downloading it from the Build release zip action artifact and installing it locally. Ensure this zip has all the files we expect, that it installs and activates correctly and that all basic functionality is working.
• Release: Create a new release, naming the tag and the release with the new version number, and targeting the trunk branch. Paste the changelog from CHANGELOG.md into the body of the release and include a link to the closed issues on the milestone.
• SVN: Wait for the GitHub Action to finish deploying to the WordPress.org repository. If all goes well, users with SVN commit access for that plugin will receive an emailed diff of changes.
• Check WordPress.org: Ensure that the changes are live on WordPress.org. This may take a few minutes.
• Close the milestone: Edit the milestone with release date (in the Due date (optional) field) and link to GitHub release (in the Description field), then close the milestone.
• Punt incomplete items: If any open issues or PRs which were milestoned for 1.1.6 do not make it into the release, update their milestone to 1.2.0 or Future Release.