Smoke tests only ran astro dev, which uses Vite's on-demand compilation
and never invokes the adapter build pipeline. Build failures in
cloudflare/playground demos (or any adapter-dependent site) passed CI
undetected. Add a build verification suite that runs astro build for
every site in the matrix before the existing runtime tests.
Bumps smoke test CI timeout from 15 to 30 minutes to accommodate.
* fix(ci): query check runs instead of commit statuses for CLA labels
The CLA Assistant action (contributor-assistant/github-action) reports
results as check runs, not commit statuses. The labeling step was
querying listCommitStatusesForRef which always returned an empty array,
so CLA labels were never applied to PRs.
Switch to checks.listForRef and match on the CLAssistant check run name
and conclusion. Add checks: read permission.
* fix(ci): split CLA labeling into separate job to avoid race condition
The label step was in the same job as the CLA check, so the CLAssistant
check run was still in_progress when queried — labels were never applied.
Move labeling to a separate job with needs: CLAssistant so the check run
is completed before we read its conclusion.
Also add issues: write permission for creating repo-level labels.
* refactor: split smoke and integration test configs into separate CI jobs
* fix: move CLA labeling from triage to CLA workflow
* fix: install formatters in temp dir to avoid catalog: protocol error
* fix: handle 404 when removing labels that don't exist on the PR
* docs: add changeset guidelines to contributing docs
Contributors and agents need to know when and how to add changesets.
Without one, changes to published packages won't trigger a release.
- CONTRIBUTING.md: full Changesets section with when/when-not, how to
add, writing descriptions, examples for patch/minor/major
- AGENTS.md: concise changeset subsection using --empty for
non-interactive use, added as step in PR flow
- PR template: changeset checkbox in checklist
* docs: note that multiple changes need separate changesets
Node 22 ships npm 10.x which doesn't support trusted publishing via
OIDC (requires npm 11.5.1+). Node 24 bundles it natively, removing the
need for the `npm install -g npm@latest` step which was failing with a
`Cannot find module 'promise-retry'` error due to npm corrupting itself
during self-upgrade.
Add a rollup job that gates on all 8 E2E shards so it can be a single
required check. Exempt emdashbot from PR template validation alongside
dependabot and renovate.
GITHUB_TOKEN can't trigger CI on PRs it creates, so the changesets
release PR could never pass required checks. Use a GitHub App token
instead, which triggers workflows normally.
Also pins all actions to commit SHAs and uses frozen lockfile.
* chore: add PR template, issue templates, and contribution policy
Drive-by feature PRs are becoming a problem. This adds guardrails:
- PR template with type selection, checklist, and AI disclosure
- Bug report issue template (structured YAML form)
- Issue config that redirects features to Discussions and disables blank issues
- PR compliance workflow that enforces template completion and requires
a Discussion link for feature PRs
- Contribution policy in CONTRIBUTING.md (acceptance tiers, AI PR rules)
- Agent-facing rules in AGENTS.md (follow the template, no bulk changes)
* fornat
