decision: keep or revert deploy-web.yml trigger change (PR #215)

[LucasSantana-Dev]

What to build

PR #215 (fix/deploy-trigger-on-release) changes the deploy-web.yml trigger from push on main (filtered by paths) to release: types: [published] + workflow_dispatch. A decision is needed before this can merge or be closed.

Option A — Keep the change (merge PR #215): Web deploys only fire when a GitHub Release is published. Aligns with the release cadence; prevents partial-commit deploys mid-release. Risk: a published release that skips the path filter no longer gates on changed web files.

Option B — Revert (close PR #215): Keep the existing push-to-main + paths trigger. Simpler, more immediate feedback loop. Risk: every main push touching web files triggers a deploy.

Acceptance criteria

• PR fix(ci): deploy only on release published or manual dispatch #215 is either merged or closed with a comment explaining the decision
• If merged: confirm Cloudflare Pages deploy fires on the next published release
• If closed: no further action needed

Blocked by

None — can start immediately.