Repository navigation
release(cli): publish create-wp-ai-plugin 1.1.0 - #10
Merged
Merged
Conversation
npm has been serving 0.1.0 since 2026-05-16. Every `npm create wp-ai-plugin` since then handed out a scaffolder four months stale, missing the main-file rename from v1.0.0 and the PL_Example substitution fix from v1.0.4. cli/package.json said 1.0.0 but that version was never published. Going out as 1.1.0 rather than 1.0.0 so the published artifact cannot be confused with the code carrying the v1.0.0 git tag -- they are not the same tree. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.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
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.
Version bump ahead of the npm publish. No behaviour change — the CLI code is already on
main.Why now
npm view create-wp-ai-plugin version→ 0.1.0, published 2026-05-16.Every
npm create wp-ai-pluginsince then has handed out a scaffolder four months stale, missing:4349f78— renamingpl-example.phpto{slug}.phpat scaffold (v1.0.0)0751a24— thePL_Examplesubstitution fix, without which every generated plugin ships a class calledPL_Example_Pluginthat collides when two kit-scaffolded plugins are active on the same site (v1.0.4)This is the only surface of the whole kit that strangers actually touch, and it has been the most out-of-date thing in the repo.
Why 1.1.0 and not 1.0.0
cli/package.jsonalready said1.0.0, but that version was never published — npm went straight from0.1.0to nothing. Publishing1.0.0now would put a tarball on npm that does not match the tree carrying thev1.0.0git tag, which is a small trap for anyone diffing later.1.1.0keeps those distinct.Contents
npm pack --dry-run: 3 files, 7.4 kB packed, 20.6 kB unpacked —index.js,README.md,package.json. Nothing stray.Publishing immediately after merge, as
pluginslab(confirmed read-write on the package).🤖 Generated with Claude Code