update-project

Goal

Perform a full dependency update of the project.

All commands MUST be executed via task. Never run composer, npm, node, or php directly on the host.

Each phase specifies its own error-handling policy. Some phases allow attempting a fix before aborting — follow the per-phase instructions rather than a blanket stop rule.

Commit Strategy

When committing changes at the end of each phase, only stage files that are directly related to that phase's purpose. If other files have changed that are unrelated to the phase (e.g., a markdown file or documentation updated as a side-effect of running a command), commit those separately with a descriptive commit message that reflects what those changes actually are. Never bundle unrelated changes into a phase commit.

Phase 1 --- Repository Safety Checks

1. Ensure the working (git) tree is clean:
   • No staged changes
   • No unstaged changes
   • No untracked files
   • If not clean: Abort immediately
     • Inform the user to commit or stash changes
2. Synchronize with remote: git fetch --prune
3. Check if vendor-updates already exists on the remote. If it does, abort and inform the user to delete the remote branch before continuing.
4. Check if local main branch is up to date with origin/main:
   • If behind → abort and inform the user to pull the latest changes.
   • If ahead with unique commits → abort and inform the user to push or rebase their commits.
   • If diverged → This can occur when testing locally (e.g., running task checkall) — the local branch may have commits not yet pushed to the remote. Ask the user which branch to use as the source for the vendor-updates branch in step 5: origin/main or local main. Choosing local main allows you to test iterations without pushing to the remote.
     Warning: choosing the local main branch may lead to merge conflicts later if the remote main has commits the local branch doesn't know about (common when you don't push test iterations).
5. Prepare branch vendor-updates:
   • If branch does not exist → create from the chosen branch in step 4 (origin/main by default, or local main if the user selected it in a diverged state)
   • If branch exists:
     • If fully merged into main → delete locally and recreate from the chosen branch.
     • If behind on main and has NO unique commits → reset vendor-updates to the chosen branch.
     • If it contains unique commits → abort and notify user.
6. Make sure that there is an auth.json file in the project root with correct credentials for private repositories if the composer.json file contains a repositories section with private repositories like filament. If not, abort and inform the user to create it. Suggest to the user to run task setup:auth.