[Feature Request] Update readme.txt while deploying

[toolstack]

Is your enhancement related to a problem? Please describe.
Currently the deployment script pushing the readme.txt file to wordpress.org as is, without doing any sanity checking/updating on the "Stable tag" or "Tested up to" fields.

This can cause issues if you forget to update these items before depoloyment, requiring a second deployment or manual updates on both GIT and SVN repos.

Describe the solution you'd like
The release script should automatically check these values and update them if required. Comminitting and pushing them back to GIT before deployment to the wordpress.org SVN.

Designs
Have PR... will submit it shortly 😁

It is in early stages and probably needs more options, like being able to disable the behaviour if it isn't wanted, but it gets the job done at the moment.

Describe alternatives you've considered
Keep doing it manually and hope my memory improves.

Additional context
None at this time.

[jeffpaul]

@toolstack is the use case here where you attempt to do a deploy to WP.org and the "stable tag"/version from GH matches what's already the latest noted on WP.org? If so, I would expect that we might have the action fail rather than pick the next version number (as who's to say how it should increment in that case).

I also do not feel that we should automatically be bumping the "tested up to" if that doesn't match the latest major WP version number as some folks may not have tested that their latest plugin version in fact works with the latest WP major version.

[toolstack]

@jeffpaul Use case is when deploying a new version of a plugin and you've forgotten to update the "stable tag" version in the readme file. This will cause the newly deployed version to not be used, but instead the old version still being zipped by wordpress.org for download. This is because wordpress.org uses the readme.txt's "stable tag" from trunk to determine which tag to actaully build from. If the readme has already been updated, no change will be made.

I was on the fence about disabling the "tested up to" check by default, it could go either way. Personally I think if you're deploying a new version of your plugin, you'd better have tested it on the latest releae of WordPress 🤷.

[aaronware]

@toolstack you may want to take a look at release-please https://github.com/google-github-actions/release-please-action it's an action that does bumping of version numbers in any file you define