This issue is about two related things:

1. Bump all readme.txt tested up to WordPress versions to 6.8.
2. Simplify deploying such a change to WordPress.org without having to publish an actual release.

The first point is obviously very easy and quick. But the second point addresses a problem we've been having: It's an odd requirement to have to publish a release just to bump the "Tested up to" WordPress version.

So let's think about how we can implement the second point:

• There's the https://github.com/10up/action-wordpress-plugin-asset-update GitHub action, which we should probably use for this.
• Since we have multiple plugins, we cannot just use the simple example workflow as listed in that project's readme - instead we have to integrate it without monorepo structure, similarly how we already do in the actual plugin release deployment workflow.
• Ideally this GitHub workflow would not be triggered by a regular GitHub process, but rather via manual workflow_dispatch. Here's why: We don't necessarily want any screenshot, banner, icon, or readme.txt change to be immediately deployed to WordPress.org. For example, if you update a readme to refer to a new plugin feature that it's only going to be available in the next release. Therefore it's safer to deploy manually.
  • It should be possible to either run this for all plugins, or for a specific plugin.
  • Ideally, any plugin should only have their assets deployed if the plugin's "Tested up to" version is higher than the "Tested up to" version from the readme.txt that is currently deployed to .org.
• What would be super neat would be to not just deploy any updated assets, but rather only modify the "Tested up to" version in the readme.txt file from the version that is already deployed to WordPress.org. That would make it 100% safe that no other change in the readme.txt could accidentally be deployed preliminarily.
  • I realize though that implementing this would take extra effort, since it would require more manual work than just deploying entire files from the GitHub repository as-is.
  • So I consider this a stretch goal, which we could also consider further down the road as a v2. I think a manual workflow_dispatch GitHub workflow would work quite well for a start.