| name | sync-versions |
| description | Update localhost and the standard Spartan Test server fleet to the latest published release, then compare active stest versions. Use when asked to "update all to latest", synchronize versions, check version drift, or show versions across localhost, p4, rdvp, t4cre-stage, t4cre-rc, t4cre-prod, and t4test. |
Sync Spartan Test Versions
Run from the Spartan Test repository root.
Standard Fleet
localhost, p4, rdvp, t4cre-stage, t4cre-rc, t4cre-prod, t4test.
Workflow
-
Verify the current repository release is committed, tagged, pushed, and published.
-
To update and verify the standard fleet, run:
.codex/skills/sync-versions/scripts/sync_versions.sh
-
To check without updating, use --check.
-
Add --test only when the user requests remote test suites; version synchronization
itself always verifies stest --version.
-
Use --expected=VERSION when the working tree is ahead of the latest published
release and the fleet must remain on that published version.
-
Hosts supplied after options replace the standard remote host list:
.codex/skills/sync-versions/scripts/sync_versions.sh p4 t4test
-
Report a compact version table. Call out unreachable hosts and any version mismatch.
Localhost Rules
- Check both the active
stest from PATH and /usr/local/bin/stest when present.
- Update
/hbfr/homebase/php-tools when installed because $HOME/bin/stest may shadow
/usr/local/bin/stest.
- Do not discard local changes in tool checkouts. Stop and report the dirty checkout;
only remove a temporary change when it was made by the current task and is now safely
present in the published release.
- Use the bundled deploy script for remote updates so PATH, sudo, Bash, and exact-version
checks remain consistent.