Skip to content

Bump wrangler compatibility_date to 2026-04-15#18

Merged
radinhamidi merged 1 commit intomainfrom
chore/bump-compatibility-date
Apr 30, 2026
Merged

Bump wrangler compatibility_date to 2026-04-15#18
radinhamidi merged 1 commit intomainfrom
chore/bump-compatibility-date

Conversation

@radinhamidi
Copy link
Copy Markdown
Member

Summary

Both Pages projects (`querygym-site`, `querygym-leaderboard`) had `compatibility_date: "2025-09-01"` in their `wrangler.jsonc`. Bumping to `2026-04-15` for housekeeping — picks up several months of Workers runtime fixes and default-flag changes.

`compatibility_date` is the Workers runtime version pin. Cloudflare ships behavior changes under dated flags so old deployments don't break when the runtime evolves. The "Workers + Static Assets" mode we use isn't sensitive to most of the dated flags; this is mostly hygiene.

Also updated the comment in `reproducibility/site/wrangler.jsonc` to clarify the bump cadence ("roughly twice a year, or when picking up a new feature") instead of the old "intentionally old-ish."

Test plan

  • `pnpm -F @qg/site build` succeeds.
  • `pnpm -F @qg/leaderboard build` succeeds.
  • CF Pages re-deploys both projects; both serve as before.

🤖 Generated with Claude Code

Both Pages projects were pinned at 2025-09-01 — fine, but stale.
2026-04-15 picks up several months of Workers runtime fixes and
default-flag changes without crossing any documented breaking change
for static-asset projects. The "Workers + Static Assets" mode we use
isn't sensitive to most of the dated flags; this is largely
housekeeping.

Updated the comment in reproducibility/site/wrangler.jsonc to
clarify the bump cadence (roughly twice a year, or when picking up
a new feature) instead of "intentionally old-ish."

Verified both sites build cleanly under the new value.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@radinhamidi radinhamidi merged commit d1ac146 into main Apr 30, 2026
3 checks passed
@radinhamidi radinhamidi deleted the chore/bump-compatibility-date branch April 30, 2026 05:20
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