Skip to content

Keep Synthetic demo green before Pages is enabled - #18

Merged
mohsinht merged 2 commits into
mainfrom
fix/optional-pages-deploy
Aug 24, 2026
Merged

Keep Synthetic demo green before Pages is enabled#18
mohsinht merged 2 commits into
mainfrom
fix/optional-pages-deploy

Conversation

@mohsinht

Copy link
Copy Markdown
Owner

What changed

  • always build, validate, budget-check, and upload the public demo artifact on main
  • deploy only after ZAATI_ENABLE_DEMO_PAGES=true or an explicit manual deploy input
  • add the official Pages configuration step
  • upgrade the Pages actions to Node 24 versions and pin every action to an immutable SHA
  • document the one-time Pages setup for maintainers and forks

Why

The asset-path failure is fixed in #17. The remaining red run is repository configuration: GitHub returns 404 because Pages has never been enabled. A fresh fork should not report broken CI merely because an optional public deployment has not been configured.

Verification

  • Prettier passes
  • repository policy passes for all workflows and exact dependency pins
  • workflow YAML parses successfully

After this merges, normal pushes stay green. Enabling Pages plus the documented variable turns deployment on.

@mohsinht
mohsinht merged commit 7d944f2 into main Aug 24, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant