Skip to content

feat: install and upgrade Data Machine from GitHub release zips - #849

Merged
chubes4 merged 3 commits into
mainfrom
fix/issue-848-wp-coding-agents
Oct 31, 2026
Merged

chubes4 merged 3 commits into
mainfrom
fix/issue-848-wp-coding-agents

Conversation

@chubes4

@chubes4 chubes4 commented Oct 31, 2026

Copy link
Copy Markdown
Member

Summary

Implemented #848 and committed as 8bb53aa. Targeted tests and bash syntax checks pass.

What changed

  • Added paginated release discovery supporting component and legacy tags via gh or authenticated curl.
  • Switched Data Machine installs and upgrades to prebuilt zips with version checks and update-result reporting.
  • Added clean git migration, dirty-checkout protection, dry-run output, fixtures, and targeted tests.
  • Updated Roadie recovery guidance.
  • Supports legacy vX.Y.Z and data-machine-vX.Y.Z releases. wp-codebox, CHANGELOG, and version strings remain unchanged.

Verification

  • bash -n lib/wordpress.sh lib/data-machine.sh upgrade.sh && bash tests/plugin-upgrade-bounds.sh passed on 09e7c5f. Base main@dfc2682 unchanged.
  • CI: pending
Cook run
  • Gate 1: tree 0bee8cb62b3260bf1b6634264c021b38fcf108d8, fingerprint de6b04a4c852a228811d6c2632b4f73c33fb9a417318aff74a5a701b1e7761e6
  • Publication identity: ambient_gh

AI assistance

Tool: Homeboy (pi) · Model: gpt-6.1-sol (tier roadie/cook-heavy) · Used for: Data Machine installation and upgrades before and after the monorepo cutover.

Closes #848

Requested by: wordpress:/var/www/extrachill.com:1

chubes4 and others added 2 commits October 31, 2026 17:05
Only git checkouts (migrated once) and installs this tool recorded in
wp_coding_agents_release_zip_plugins are upgraded from release zips. A plain
directory placed by a deploy pipeline or wp-admin keeps today's skip behavior
instead of getting a second writer that bypasses its deploy gates.
@chubes4

chubes4 commented Oct 31, 2026

Copy link
Copy Markdown
Member Author

Review fix pushed: fix: leave externally managed Data Machine installs alone.

The problem: before this PR, the upgrader skipped any plugin directory that wasn't a git checkout. As written, the PR upgraded any directory to the newest zip. On extrachill.com, Data Machine is deployed by the Homeboy deploy pipeline, behind the network rig gate. An upgrade.sh run would have become a second writer of that directory and could ship a release before the gate approved it.

What changed:

  • Upgrades now touch only:
    • git checkouts, which are converted once, as in the PR;
    • installs this tool recorded itself in the wp_coding_agents_release_zip_plugins option. A fresh install and a migration both record it.
  • Any other directory is skipped and logged, which is today's behavior.
  • Setup leaves an existing foreign install in place and only makes sure it's active.

Verification:

  • tests/plugin-release-zips.sh passes, including a new case: a foreign-managed install is left alone by both upgrade and setup.
  • tests/plugin-upgrade-bounds.sh and tests/upgrade-help.sh pass.

🤖 Extra Chill Bot (Claude)

@chubes4
chubes4 merged commit 76e5071 into main Oct 31, 2026
87 checks passed
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.

Install and upgrade Data Machine from release zips instead of git clones (monorepo prerequisite)

1 participant