No results found.

Dev tooling

FishPig WordPress Theme for Composer

The theme from FishPig's Magento 2 WordPress integration, built for every upstream release so Composer-managed WordPress can pin it to the module's version.

Source on GitHub ↗View on Packagist ↗

Tagged releases
247
FishPig versions covered
2.x and 3.x
Missing versions built per daily run
3

FishPig’s Magento 2 WordPress integration, by Ben Tideswell, needs a matching WordPress theme. On a Composer-managed WordPress install, such as Bedrock, that theme should come from Composer, pinned to the same version as the Magento module. This repository builds it from source for every upstream release and publishes it to Packagist as samjuk/wp-theme-fishpig.

How do I install the theme?

Require the version that matches your FishPig Magento module:

composer require samjuk/wp-theme-fishpig:3.32.3

The README recommends pinning both, for compatibility. For a Bedrock site running locally in Warden, the Warden Bedrock docs page covers the nginx changes.

How does a new FishPig release reach Packagist?

Without anyone touching it. A GitHub Actions watcher runs every day at 05:30 UTC, lists upstream’s tags and its own, and builds up to three that are missing:

TAGS=$(grep -vxf <(fetch_tags $downstream) <(fetch_tags $upstream) | tail -n3 | jq -R | jq --slurp | jq -rc)

Each missing tag goes to a Docker container action that builds the theme and its Composer manifest. A bot commits the result, tags it and triggers a release, and each release links to the upstream compare view for that tag.

I built it over 11 days in January 2025. It has published 247 tagged releases unattended since, the latest 3.32.3 on 2nd July 2026. As of 11th October 2026 that matches upstream’s 247 tags.

Has the theme actually changed?

Not always. Versions mirror upstream one to one, so some releases change nothing in the theme. Each release carries an update.flag file holding a hash of the theme content, also written into the commit message, so a changed hash means changed theme files.

To see what changed, compare two tags with GitHub’s two-dot comparison, for example 3.0.1..3.1.1.