Skip to content

fix(playground): theme-test blueprint via CORS proxy, not git:directory - #103

Merged
dknauss merged 1 commit into
mainfrom
fix/theme-test-blueprint-no-git-directory
Jul 2, 2026
Merged

fix(playground): theme-test blueprint via CORS proxy, not git:directory#103
dknauss merged 1 commit into
mainfrom
fix/theme-test-blueprint-no-git-directory

Conversation

@dknauss

@dknauss dknauss commented Jul 2, 2026

Copy link
Copy Markdown
Owner

The internal blueprint-theme-test.json still used resource: git:directory, which fails on the current Playground build with createHash is not a function (the same regression the public blueprint-main.json/blueprint-stable.json were already moved off of in #102).

This routes the pinned commit archive (cf70cb5) through the official wordpress-playground-cors-proxy.net, matching blueprint-main.json. A direct github.com/.../archive/<sha>.zip is CORS-blocked (no Access-Control-Allow-Origin) when Playground fetches it client-side, so the proxy wrapper is required.

Verified in Playground (headless Chromium, 2026-07-02): theme installs and activates (Active: Dirtbag on themes.php), clean boot, no createHash/CORS/step-execution errors.

🤖 Generated with Claude Code

…:directory

The theme-unit-test blueprint still used resource: git:directory, which
fails on the current Playground build with 'createHash is not a function'.
Route the pinned commit archive (cf70cb5) through the official
wordpress-playground-cors-proxy.net, matching blueprint-main.json.

A direct github.com/.../archive/<sha>.zip is CORS-blocked (no
Access-Control-Allow-Origin) when fetched client-side by Playground, so
the proxy wrapper is required. Verified in Playground: theme installs and
activates (Active: Dirtbag), clean boot, no createHash/CORS errors.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@dknauss
dknauss merged commit 4b7650a into main Jul 2, 2026
9 of 10 checks passed
@dknauss
dknauss deleted the fix/theme-test-blueprint-no-git-directory branch July 3, 2026 08:51
dknauss added a commit that referenced this pull request Jul 4, 2026
…atch, Playground/HelpHub tracking (#107)

* docs: refresh WP contribution status; fix dangling gallery-comment link

- two-factor #877 merged 2026-06-29 (was "proposed")
- two-factor #859 closed by accident, reopened as #917 — point tracker at #917
- gutenberg #79380 now proposed upstream in #79440; note Dirtbag backs that PR
- docs/repro/README.md: the gallery-caption comment draft was never written;
  replace the broken link with an honest "not yet drafted" note

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* docs(repro): add held core fix for gutenberg #79372 (Post Title float)

Post Title links are display:inline-block in the shared style.scss, which stops
the title wrapping around floats / shape-outside on the front end. Archaeology
shows the inline-block was added in gutenberg#30666 solely to silence an editor
RichText "inline container" warning — it has no front-end purpose. The held fix
moves it to an editor-only editor.scss so the front-end link stays inline.

Patch verified to git-apply cleanly against current gutenberg trunk. Held pending
a maintainer signal on the (triaged) issue; theme-side float variant remains the
local fix. Also link the reserve fix from the repro README float section.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* docs: track HelpHub #1817 (shipped) and Playground #3875 contributions

- Documentation-Issue-Tracker #1817: admin-email HelpHub content merged + closed Done
- wordpress-playground #3875: git:directory browser-bundle bug Dan filed (the one
  Dirtbag works around in #102/#103); open, regression-test suggested upstream

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* docs: update Playground #3875 status — fix in flight via #3882

adamziel's #3879 (first pass, closed) consolidated into ashfame's #3882 (open):
isomorphic-git browser-ESM alias across all browser-facing packages + Playwright
git:directory regression test + localhost CORS-proxy bypass. Fixes #3875; Dirtbag
CORS-proxy ZIP workaround retirable once it merges.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* docs: note #3875 fix verified on #3882 preview build

Drove the #3882 Playground preview build (playground.wordpress.net/?pr=3882) with a
git:directory installTheme of dknauss/dirtbag — clones and activates cleanly, no
createHash error. Fix confirmed working, pending merge + production deploy before
switching dirtbag blueprints back off the CORS-proxy ZIP workaround.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
dknauss added a commit that referenced this pull request Jul 4, 2026
…ed in prod

The wordpress-playground git:directory browser bug (#3875) is fixed on trunk (the
vite-resolve-isomorphic-git browser-ESM alias, PR #3882) and deployed to production.
Verified: a git:directory installTheme of dknauss/dirtbag at the pinned v0.1.3 commit
clones and activates on production playground.wordpress.net with no createHash error.

Revert blueprint-theme-test.json off the CORS-proxy archive-ZIP workaround (#102/#103)
back to git:directory, dropping its dependency on the third-party proxy. Refresh the
contributions-tracker #3875 entry to note the production deploy and retirement.
blueprint-main/stable keep the rolling release-asset ZIP by design.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant