Repository navigation
docs: say that the packages are on npm and Packagist - #6
Merged
Merged
Conversation
Signed-off-by: MobileMage <aidelojejoshua@gmail.com>
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
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.
The four npm packages are now on npm: @gatepost/core 0.1.0-alpha.2, and @gatepost/client,
@gatepost/field and @gatepost/react 0.1.0-alpha.1. gatepost/postcode is on Packagist at
v0.1.0-alpha.1. This sets the state in src/release-state.json to "published" and removes the
"not published yet" sentence from each guide, as the release-state test asks.
The plugin flag stays "not published". The plugin has a GitHub release now, but it is not on
WordPress.org, and the plugin guide changes on its own schedule.
Signed-off-by: MobileMage aidelojejoshua@gmail.com