Booster Workflow Setup Fixture
Disposable public fixture for RAN Booster assisted release workflow proof
by rocketsarenostalgic · github.com/rocketsarenostalgic/booster-fixture-workflow-setup
Install
No release zip yet. The repository archive installs, but the folder name will carry the branch suffix and updates will not flow:
wp plugin install https://github.com/rocketsarenostalgic/booster-fixture-workflow-setup/archive/refs/heads/main.zipDisposable public plugin fixture for the RAN Booster assisted release workflow. It provides a minimal inactive plugin that can be installed for end-to-end release checks. Its initial default branch deliberately contains the package, Release Please configuration, and repository-owned build/upload scripts, but no workflow, tags, or releases.
The Phase 5 product proof uses Booster Release Deployments to inspect that state and open a reviewable pull request adding the managed workflow. Only explicit test control may merge that pull request and the later Release Please pull request. A successful release must contain one exact conventional WordPress ZIP accepted by Booster's existing release verifier.
This repository is durable evidence, not a general template. Existing plugin and theme fixtures remain the positive evidence that conforming external pipelines are accepted without installing this managed workflow.
Release contract
The repository-owned builder accepts an immutable Git ref and exact version:
release_version=0.1.0
bash scripts/build-release.sh "v$release_version" "$release_version"It creates build/booster-fixture-workflow-setup-<version>.zip with one
booster-fixture-workflow-setup/ package root and an exact runtime allowlist.
GitHub's asset digest and the updater's local re-hash bind the ZIP bytes; no
sidecar is published.