Barazo AppView backend barazo.forum

fix(ci): route deploy through lockfile sync to prevent stale lockfile (#132) master

Replace the two-step dispatch (deploy + sync in parallel) with a single dispatch to barazo-workspace's sync-lockfile workflow. The sync workflow regenerates the lockfile if needed, then triggers the deploy with the correct refs. This fixes a race condition where the deploy started with a stale workspace lockfile before the sync had committed the updated one, causing frozen-lockfile failures when new dependencies were added.


+6 -11
1 changed file