v4.2.0 — Remove child theme, versioned Erebus clone#8
Open
harryfinn wants to merge 1 commit into
Open
Conversation
- setup_themes() now clones a tagged Erebus release (default v3.0.0) and activates it directly — no child theme scaffold - EREBUS_VERSION constant pins the default Erebus release - --theme-version flag overrides the Erebus version for a single run - MIMIR_VERSION bumped to 4.2.0 Co-Authored-By: Claude Sonnet 4.6 <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.
Summary
setup_themes()now clones Erebus directly intowp-content/themes/erebusand activates it. All child theme scaffolding removed.git clone --branch <tag> --depth 1so each project gets a pinned, reproducible Erebus version. Default pinned tov3.0.0viaEREBUS_VERSIONconstant.--theme-versionflag —mimir --theme-version=3.1.0overrides the default for a single run (useful when a newer Erebus release is out butMIMIR_VERSIONhasn't been bumped yet)EREBUS_VERSIONis set to3.0.0but thev3.0.0tag doesn't exist on the Erebus repo yet (it's onrelease/v3.0.0branch). The tag must be cut on Erebus before this can be tested end-to-end. In the meantime, test with--theme-version=2.0.1to use the latest existing tag.Test plan
v3.0.0on Erebus (or test withmimir --theme-version=2.0.1in the interim)mimirin a fresh empty directory — confirm Erebus clones towp-content/themes/erebusand activates.gitdirectory is removed from cloned thememimir --theme-version=2.0.1— confirm that specific tag is clonedmimirin the same directory — confirm clone step is skipped (idempotent)mimir version→Mimir v4.2.0mimir --help→ shows--theme-versionflag and default Erebus version🤖 Generated with Claude Code