Avoid pushing unreleased `Stable tag` to SVN trunk

[kasparsd]

Is your enhancement related to a problem? Please describe.

During the release process (described in RELEASING.md) we're currently:

1. creating a pull request with the release changes (version bump, readme updates, etc.),
2. merging in the pull request to `master,
3. creating a new release in GitHub which creates a new tag for that latest revision of master.

With the introduction of master deploys to WP-org trunk in #734, it now:

1. pushed the upcoming release to WP-org SVN trunk (even though it hasn't been tagged and deployed yet).
2. pushes the SVN tag/x.x.x when the release is tagged and the CI runs.

This leads to the following warning on WP.org during step 1 and 2:

Proposed Solution

Introduce a trunk branch which is updated only after releases (possibly by the release workflow)?

Use it for isolated updates to readme and WP-org assets. Automatically merge it back to master if there are differences.

Designs

No response

Describe alternatives you've considered

No response

Please confirm that you have searched existing issues in this repository.

Yes

[kasparsd]

@dd32 Do you have a suggestions for how to handle this (how are other community plugins doing this)? The goal is to allow readme and asset updates without pushing a release.

[dd32]

Not sure, I don't think most plugins bother with updating trunk regularly. It's annoying at times, beneficial at others. The only thing I can really suggest I think is KISS and don't set things unless you really need to.

Most plugins probably tag/release and only update the readme.txt Stable Tag only after everything is released.

I imagine you probably want to have Stable Tag reference the version inside the tag though... not that it matters to anything.

You could also slot in a step that modifies the readme.txt to reference the latest release on GitHub whose actions have all completed? that seems overkill though.