Repository navigation
v1.1.0: Version bump and changelog - #266
Merged
Merged
Conversation
Contributor
Author
|
Folded the dependabot batch in here. Closes #267, #269, #272 and #274 - #268, #270, #271 and #273 were already covered by the dependency refresh that was on this branch.
#272 I removed instead of bumping. Two things this turned up that I did not fix here, filed as #275: |
This was referenced Sep 20, 2026
Closed
bd-viget
force-pushed
the
bd/v1.1.0-prep
branch
from
September 23, 2026 15:41
656cdc6 to
9cd7f3c
Compare
bd-viget
changed the title
bd-viget
force-pushed
the
bd/v1.1.0-prep
branch
from
September 23, 2026 17:02
9cd7f3c to
53dcb48
Compare
packages.json 1.0.24 to 1.1.0, and the 1.1.0 entry. The entry moved from README.md to CHANGELOG.md, which is where #262 relocated the history - the README section is now a pointer, so adding to it conflicted. Folded into the v1.1.0 section #281 opened rather than starting a second one. Two corrections while moving it: the Blocks Toolkit line says 1.1.9, which is what the theme lock picks up once that tag lands, and the >=8.2 PHP requirement declared in #282 is user-facing so it gets a line. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DR1cWHgptENsJa7GTrmtQ3
v1.1.9 is tagged and on Packagist, so the theme lock picks it up. Item 2 of the 1.1.0 release checklist. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DR1cWHgptENsJa7GTrmtQ3
#262 closed seven issues and none of them were listed. Adds the create-project git protection, the Twig/vendor pruning fix, the DDEV escape codes, the skill path correction, the licensing clarification, sync-version.mjs, and the changelog move. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DR1cWHgptENsJa7GTrmtQ3
The committed copy was 6.8.2. It is not Composer-managed - the starter ships it so a fresh create-project runs with no license key - so nothing updates it automatically and it has to be refreshed by hand at release time. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DR1cWHgptENsJa7GTrmtQ3
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DR1cWHgptENsJa7GTrmtQ3
Five files survive into a generated project still referencing wp-starter: .gitattributes theme.json path .github/dependabot.yml two theme directory paths AGENTS.md theme paths in example links bin/check-event-handlers.php theme composer.json path PostInstallScript.php the PROJECT_SLUG fallback Confirmed against the generated project rather than by reading the script - these are the five that still matched after a real create-project run. AGENTS.md needed three examples changed first. They used `wp_starter_`, which is neither a token the script searches for nor what the theme actually uses (`wpstarter_`), so a blanket replace left them half-rewritten: "e.g. acme-museum -> wp_starter_". They use a generic example now, so they read correctly with or without the rename. Left `<theme-slug>` placeholders alone. The document defines them in a table and tells the agent to resolve them from the directory, so they stay correct if the theme is ever renamed again. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DR1cWHgptENsJa7GTrmtQ3
bd-viget
force-pushed
the
bd/v1.1.0-prep
branch
from
September 23, 2026 19:23
b65ebb7 to
b924dba
Compare
bd-viget
marked this pull request as ready for review
September 23, 2026 19:34
The examples were changed to a generic acme-museum, which meant a generated project read someone else's project name. Back to wp-starter and wpstarter_, which are both tokens the rename searches for, so the examples come out as the project's own names. The blocker before was that the examples used wp_starter_, which is not what the theme uses (wpstarter_) and not a token the script searches for, so a rename left them half-rewritten. Using the prefix the theme actually uses fixes that, and the function-prefix group runs before the slug group so wpstarter_ is consumed first. Loosened the rule wording in the prefix table row, since the starter's own prefix drops the dash and the old wording contradicted its own example. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DR1cWHgptENsJa7GTrmtQ3
matthisamoto
approved these changes
Sep 23, 2026
matthisamoto
left a comment
matthisamoto
left a comment
There was a problem hiding this comment.
create project and ddev start both work great, versions and file deletions check out!
Drops PostInstallScript.php, which came back out of the replacement list, and notes that the AGENTS.md naming examples resolve to the project's own prefix. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DR1cWHgptENsJa7GTrmtQ3
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
2 participants
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.
Summary
Release PR for 1.1.0.
packages.json1.0.24 → 1.1.0CHANGELOG.mdcomposer.lock→ Viget Blocks Toolkit 1.1.9The dependency updates, Actions bumps and
prettier.config.cjsrename that were originally on this branch went out in #282.Minor rather than patch - WordPress 7.1 support and the theme.json helpers are both new behavior.
Checklist - all clear
All other open PRs merged- Repo hygiene and create-project fixes #262, [N/A] Mark vendored and generated files for diffs #281 and Update dependencies for 1.1.0 #282 are all in.viget-blocks-toolkitv1.1.9 tagged and on Packagist, thencomposer updatein the themenode bin/sync-version.mjs --checkpassesVersion 1.1.0 is good. Theme pinned at 0.1.0.Both CI jobs green, no conflicts, branch is level with
main.Changelog is 32 entries, not 24
#262 closed seven issues and none of them had made it in. Added:
create-projectinstalling over locally cloned plugins and themes ([Bug] Git-repo plugin protection (PreScripts) silently never runs in generated projects, and only covers a hardcoded plugin list #237)vendor/, plus the.twigglob that missed nested block templates ([Bug] Choosing PHP templates still installs Timber/Twig (removed from composer.json but not composer.lock/vendor) #236)create-projectoutput ([Bug] Stray terminal escape sequences leak into create-project output #233)AGENTS.mdand the theme README ([Bug] Broken agent-skill path in AGENTS.md and theme README #243)bin/sync-version.mjsand theCHANGELOG.mdmove ([Bug] Theme version stuck at 0.1.0 while project ships v1.0.24 #248)Also corrected the Blocks Toolkit line from 1.1.8 to 1.1.9, added the
>=8.2PHP requirement declared in #282 since Composer now enforces it, and noted the ACF Pro bump.The ACF Pro bump is why the diff is big
ACF Pro is committed rather than Composer-managed - the starter ships it so a fresh
create-projectruns with no license key - so nothing updates it automatically and it gets refreshed by hand at release time. 6.8.2 → 6.8.10 is 203 files.13 of those are new in 6.8.10: the email opt-in banner (PHP, JS, images, icons) and two new language packs (
bn_BD,es_AR). No deletions. I scanned the diff for license keys and stray files before committing - the onlyacf_pro_licensehits are ACF's own option and constant names, and there are no hardcoded key literals,.envfiles or.DS_Store.Two earlier notes, now resolved
The changelog originally wrote to
README.md, which #262 turned into a pointer - moved intoCHANGELOG.md, folded into the## v1.1.0section #281 opened.This branch was also 3 commits behind
mainand itsbuild.yamlwas missing theComposer Scripts Testsjob, which would have deleted it on merge. The rebase ontomainfixed that; the job is present.Still outstanding, not blocking
.nvmrc(24.13.0, matching DDEV). CI has been building on Node 22.12.0 / npm 10.9, below the theme's ownengines.npm >=11.0.0. Separate PR, safe to merge after this.Issues
Testing Instructions
composer create-projectoff this branch end to end.ddev starton a fresh clone of a generated project.packages.jsonandCHANGELOG.mdare both gone from the generated project, and the theme is still at0.1.0.