fix(playground): install stable demo from WordPress.org, not git:directory - #73
Closed
dknauss wants to merge 1 commit into
Closed
fix(playground): install stable demo from WordPress.org, not git:directory#73dknauss wants to merge 1 commit into
dknauss wants to merge 1 commit into
Conversation
…ctory The stable "Try it live" demo cloned the plugin via a git:directory resource pinned to the release tag with path "/", which pulled the entire 6.2 MB / 322-file dev repo (.planning, tests, CI configs, docs) into the plugin folder — slow, unreliable, and not what users actually install. Maestro is published on WordPress.org, so install it from the directory via the "plugins" shorthand instead: byte-identical to a real install, served from the Playground CDN, and it auto-tracks the current Stable tag. This also removes the per-release blueprint ref-bump: prep-release.sh no longer edits any blueprint, and the "Release rule" docs are updated to match. blueprint-hosted.json still uses git:directory for bleeding-edge main (the only zero-infra way to demo unreleased code). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Owner
Author
|
Superseded by #75, which fixed the |
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.
What & why
The stable "Try it live" Playground demo — the primary link in the README — installed the plugin via a
git:directoryresource pinned to the release tag withpath: "/". That pulled the entire 6.2 MB / 322-file dev repo (.planning/,tests/,.github/,docs/,bin/, phpcs/phpstan configs,package.json, …) intoplugins/maestro-menu-editor/:git:directoryis Playground's slowest, flakiest resource type (git-over-HTTP proxy) vs. the wp.org CDN Playground caches..distignore-filtered payload (includes/,assets/,languages/, two PHP files, readme), not the whole dev tree.refevery release viabin/prep-release.sh.Maestro is published on WordPress.org, so this switches the stable demo to install from the directory via the
"plugins"shorthand (same mechanism already used foruser-switchingin the same file). Result: byte-identical to a real install, CDN-fast, and auto-tracks the current Stable tag — no per-release edits.Changes
playground/blueprint-stable.json— drop thegit:directoryinstallPluginstep; addmaestro-menu-editorto the"plugins"array.bin/prep-release.sh— no longer edits any blueprint (nothing to bump).playground/README.md/README.md— update descriptions; remove the now-obsolete "Release rule" / post-tag-automation section.blueprint-hosted.json(bleeding-edgemain) intentionally keepsgit:directory— it's the only zero-infra way to demo unreleased code.Verification
blueprint-stable.jsonis valid JSON;prep-release.shpassesbash -n.wordpress.org/plugins/maestro-menu-editor/and the plugin-info API both return 200, confirming the slug resolves.mainand confirm it boots into edit mode with the plugin active. (The raw blueprint URL is served frommain, so the demo reflects this change only after merge.)🤖 Generated with Claude Code