Release 1.2.0

[peterwilsoncc]

Functional updates

Fairly generously defined as PRs that:

• Bump WP tested up to or minimum supported version
• Update wp-scripts as that may modify deployed files
• touches source code

PRs

• Update WordPress version compatibility to 7.1 #219
• Replace deprecated ${var} with {$var}. #213
• Fix: trim whitespace from slot ID exclusions to prevent space-padded … #205
• Update npm dependencies #186
• Bump wp min to 6.6 #175
• Bump WordPress "tested up to" version 6.8 #176
• Update all actions we use in our workflows to pull from specific pinned commits #172
• Feature/cypress test #148
• Bump WordPress version 6.7 #166
• Bump WordPress "tested up to" version 6.7 on trunk #167
• Bump the npm_and_yarn group across 1 directory with 3 updates #163
• Bump tested up to header to indicate WordPress 6.9 support. #184
• Add FAQ section for security bug reporting #185
• Plugin Compatibility Testing With Wordpress 6.8-RC2 #174

Non-functional updates

PRs that don't do any of the above, mostly dependabot updates.

• Bump the npm_and_yarn group across 1 directory with 2 updates #216
• Bump the npm_and_yarn group across 1 directory with 2 updates #227
• Bump fast-uri from 3.1.4 to 3.1.5 in the npm_and_yarn group across 1 directory #228
• Bump postcss from 8.5.14 to 8.5.23 in the npm_and_yarn group across 1 directory #226
• Bump the npm_and_yarn group across 1 directory with 3 updates #225
• Bump shell-quote from 1.8.4 to 1.10.0 in the npm_and_yarn group across 1 directory #223
• Bump axios from 1.16.0 to 1.18.1 in the npm_and_yarn group across 1 directory #222
• Bump the npm_and_yarn group across 1 directory with 2 updates #221
• Bump the npm_and_yarn group across 1 directory with 1 update #220
• Bump form-data from 4.0.5 to 4.0.6 in the npm_and_yarn group across 1 directory #218
• Bump launch-editor from 2.12.0 to 2.14.1 in the npm_and_yarn group across 1 directory #217
• Bump tmp from 0.2.5 to 0.2.7 in the npm_and_yarn group across 1 directory #215
• Bump systeminformation from 5.31.1 to 5.31.6 in the npm_and_yarn group across 1 directory #214
• Bump @babel/plugin-transform-modules-systemjs from 7.28.5 to 7.29.4 in the npm_and_yarn group across 1 directory #212
• Bump fast-uri from 3.0.6 to 3.1.2 in the npm_and_yarn group across 1 directory #211
• Bump the npm_and_yarn group across 1 directory with 3 updates #210
• Bump ip-address from 10.1.0 to 10.2.0 in the npm_and_yarn group across 1 directory #209
• Bump follow-redirects from 1.15.11 to 1.16.0 in the npm_and_yarn group across 1 directory #208
• Bump basic-ftp from 5.2.1 to 5.2.2 in the npm_and_yarn group across 1 directory #207
• Bump axios from 1.13.2 to 1.15.0 in the npm_and_yarn group across 1 directory #206
• Bump basic-ftp from 5.2.0 to 5.2.1 in the npm_and_yarn group across 1 directory #204
• Bump lodash from 4.17.23 to 4.18.1 in the npm_and_yarn group across 1 directory #203
• Bump lodash-es from 4.17.23 to 4.18.1 in the npm_and_yarn group across 1 directory #202
• Bump node-forge from 1.3.3 to 1.4.0 in the npm_and_yarn group across 1 directory #201
• Bump picomatch from 2.3.1 to 2.3.2 in the npm_and_yarn group across 1 directory #199
• Bump flatted from 3.3.3 to 3.4.2 in the npm_and_yarn group across 1 directory #198
• Bump simple-git from 3.30.0 to 3.33.0 in the npm_and_yarn group across 1 directory #197
• Bump svgo from 3.3.2 to 3.3.3 in the npm_and_yarn group across 1 directory #196
• Bump immutable from 5.1.4 to 5.1.5 in the npm_and_yarn group across 1 directory #195
• Bump basic-ftp from 5.1.0 to 5.2.0 in the npm_and_yarn group across 1 directory #194
• Update how we run PHPUnit #192
• Bump systeminformation from 5.30.4 to 5.31.1 in the npm_and_yarn group across 1 directory #193
• Bump qs from 6.14.1 to 6.14.2 in the npm_and_yarn group across 1 directory #191
• Bump webpack from 5.98.0 to 5.105.0 in the npm_and_yarn group across 1 directory #190
• Bump phpunit/phpunit from 8.5.30 to 8.5.52 in the composer group across 1 directory #189
• Bump lodash-es from 4.17.22 to 4.17.23 in the npm_and_yarn group across 1 directory #188
• Bump lodash from 4.17.21 to 4.17.23 in the npm_and_yarn group across 1 directory #187
• Update permissions to allow release asset attachment during release deploys #179
• Bump the npm_and_yarn group across 1 directory with 2 updates #178
• Resolved issues #180
• Bump the npm_and_yarn group across 1 directory with 6 updates #170
• Fix/workflow perms #177
• fix/build-release: add workflow_call trigger #169
• Update Cypress workflow to use release ZIP #168
• add WP and PHP minimum badges #164
• add banner image, tweak badges #162
• Bump webpack from 5.92.1 to 5.94.0 in the npm_and_yarn group across 1 directory #161
• Bump axios from 1.7.2 to 1.7.4 in the npm_and_yarn group across 1 directory #160

---

• Branch: Starting from develop, cut a release branch named release/X.Y.Z for your changes.
• Version bump: Bump the version number in ad-refresh-control.php, package.json, package-lock.json and readme.txt if it does not already reflect the version being released. In ad-refresh-control.php update both the plugin "Version:" property and the plugin AD_REFRESH_CONTROL_VERSION constant.
• Changelog: Add/update the changelog in both CHANGELOG.md and readme.txt.
• Props: Update CREDITS.md file with any new contributors, confirm maintainers are accurate.
• 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.
• New files: Check to be sure any new files/paths that are unnecessary in the production version are included in .distignore.
• 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 (e.g. https://github.com/10up/ad-refresh-control/milestone/#?closed=1).
• 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 https://wordpress.org/plugins/ad-refresh-control/. This may take a few minutes.
• Close 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 X.Y.Z do not make it into the release, update their milestone to X.Y.Z+1, X.Y+1.0, X+1.0.0 or Future Release.

[peterwilsoncc]

Deployed to WordPress plugin repo:

• GitHub action run
• SVN Commit

Live on the plugin repo, updates will begin flowing once the PTS delay has passed.