docs: sync readme.txt Stable tag to 1.8.14 - #70
Merged
Conversation
….org) The GitHub repo's readme.txt Stable tag tracks whatever version is actually live on WordPress.org per RELEASING.md's convention. 1.8.14 was pushed to WP.org SVN earlier today (confirmed live via the public plugin API); this just syncs the GitHub-side metadata to match. No functional change.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Trivial metadata sync, no functional change. 1.8.14 was pushed to WordPress.org SVN earlier today (confirmed live via the public plugin API: version 1.8.14). GitHub's readme.txt Stable tag field had drifted out of sync (still said 1.8.13). Fixes that.