Background
The current deploy workflow (.github/workflows/deploy.yml) uses hydephp/action@master:
- uses: hydephp/action@master
Pinning to @master means any breaking changes pushed to that branch are immediately picked up, which is risky — especially during a major Hyde v1 → v2 upgrade.
Task
- Check whether
hydephp/action has a tagged release that supports HydePHP v2.
- Pin the workflow to that tagged release (e.g.
hydephp/action@v2.x.x) rather than @master.
- If no tagged release exists yet, open an issue upstream or monitor for one.
Why now
This came up as part of the HydePHP v2 upgrade work tracked in #14. Decoupled here so it can be tracked and actioned separately.
Background
The current deploy workflow (
.github/workflows/deploy.yml) useshydephp/action@master:Pinning to
@mastermeans any breaking changes pushed to that branch are immediately picked up, which is risky — especially during a major Hyde v1 → v2 upgrade.Task
hydephp/actionhas a tagged release that supports HydePHP v2.hydephp/action@v2.x.x) rather than@master.Why now
This came up as part of the HydePHP v2 upgrade work tracked in #14. Decoupled here so it can be tracked and actioned separately.