Release 1.0.1 as the WordPress.org debut - #7
Merged
Conversation
v1.0.0 is already tagged and its release asset unpacks to citecue/. Every change since then — the directory name, the text domain, the connect-gated cron — would otherwise ship under that same version number, leaving two materially different artifacts both calling themselves 1.0.0. The changelog is corrected along with it. Two entries describing work that landed after v1.0.0 was cut had been written into the 1.0.0 section, where they claimed behaviour that release does not have; they move to 1.0.1. The upgrade notice is aimed at whoever installed the GitHub zip: the folder rename is the one part of this that is not automatic, and settings survive it because they live in the database.
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.
Bumps the three version strings the build script cross-checks, and corrects
the changelog ahead of tagging
v1.0.1.v1.0.0is already tagged and its release asset unpacks tocitecue/.Everything that landed in #6 — the directory name, the text domain, the
connect-gated cron — would otherwise ship under that same version number,
leaving two materially different artifacts both calling themselves 1.0.0.
Two changelog entries describing post-v1.0.0 work had been written into the
1.0.0 section, where they claimed behaviour that release does not actually
have. They move to 1.0.1.
The upgrade notice is aimed at whoever installed the GitHub zip: the folder
rename is the one part of this that is not automatic, and settings survive it
because they live in the database, not the plugin directory.
After merge
Tagging
v1.0.1builds the release asset; that zip is what goes towordpress.org.
🤖 Generated with Claude Code