In situ edits of readme does not update properly

[Ipstenu]

Edited since this is a little bigger.

Originally:

If a plugin enables release notifications and later makes cosmetic edits to a plugin (such as bumping 'tested up to') _WITHOUT_ making a new version, the change will not be noticed or set live.

This results in developers asking plugins to remove the feature from their plugins.

Recommendation:

If an _active_ tag is changed, allow a release notification

Updated:

Making any edits to the readme without bumping versions results in nothing changing on the front end. This means it's a requirement to release new versions in order to update tested-up-to (for example).

[dd32]

If a plugin enables release notifications and later makes cosmetic edits to a plugin (such as bumping 'tested up to') _WITHOUT_ making a new version, the change will not be noticed or set live.

This was kind-of by design. The intention is that the release should not change after approved, even if the tag changes (which realistically, should never happen).

Unfortunately, as we all know though, plugins often need to update tags for readme changes..

I would love if the fix for this wasn't to support tag-updates, but to remove the need to alter the tag.

[Ipstenu]

Updated because this is actually related to the issue where updating a readme won't update the front end of WP or rebuild, so now it's causing people to complain that they updated the readme and it doesn't show any changes.

[dd32]

I'm unable to duplicate this now.

There was a change quite some time ago that caused the tagged readme to be imported, which in turn allows the tested up to version to change.

The only case where this is not working AFAIK, is when the release is pending confirmation, the changes won't be reflected on the site until the release is confirmed.