Skip to content

chore: wrangler audit remediation #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
chitcommit wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore: wrangler audit remediation #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion wrangler.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
#:schema node_modules/wrangler/config-schema.json
name = "chittycharge"
main = "src/index.ts"
compatibility_date = "2025-10-11"
compatibility_date = "2026-03-16"
Copy link
Copy Markdown

@coderabbitai coderabbitai bot Mar 29, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Description: Search for chittytrack service configuration to verify it exists

# Search for chittytrack worker configuration
fd -e toml -e json -e yaml . | xargs rg -l 'name.*=.*"chittytrack"' 2>/dev/null || echo "No chittytrack service found in repo"

# Also search for any references to chittytrack
rg -n "chittytrack" -g '!wrangler.toml'

Repository: chittyapps/chittycharge

Length of output: 103

🌐 Web query:

What is the latest valid compatibility_date for Cloudflare Workers as of March 2026? Are there any breaking changes in Cloudflare Workers compatibility_date 2026-03-16 compared to 2025-10-11?

💡 Result:

The latest valid compatibility_date for Cloudflare Workers as of March 29, 2026, is 2026-03-27. Official documentation examples recommend setting compatibility_date to the current date, with specific instances using "2026-03-27" in wrangler.toml configurations for Node.js compatibility. Additional evidence includes workerd version 1.20260305.0 supporting up to 2026-03-05 (from GitHub issue dated Feb 2026), changelog entries up to 2026-03-20, and other examples like "2026-03-20", "2026-03-17". Compatibility dates are supported indefinitely, but the latest is the most recent date developers should use, typically the current date or the last daily release date. There are breaking changes between compatibility_date 2025-10-11 and 2026-03-16. Compatibility dates opt into backwards-incompatible changes via flags that become default on specific dates. Between these dates, several flags were activated by default, including: - delete_all_deletes_alarm (default 2026-02-24): Durable Object deleteAll now deletes alarms. - containers_pid_namespace (default 2026-04-01, but listed under recent flags): Isolated PID namespace for containers (may apply if date >=2026-03-16). - enable_ctx_exports (2025-11-17): Likely enables ctx.exports. - Other Node.js and runtime updates (e.g., V8 updates, fs APIs in 2025-09-11, MessageChannel 2025-08-11). Full list in compatibility flags docs; developers must check https://developers.cloudflare.com/workers/configuration/compatibility-flags/ and test when upgrading.

Citations:

The "chittytrack" service referenced in tail_consumers does not exist in the repository, and the compatibility_date change introduces breaking changes that require verification.

  1. Missing service reference (lines 17-18): The tail_consumers configuration references a "chittytrack" service that is not found anywhere in the repository. This will cause a configuration error at runtime.

  2. Compatibility_date breaking changes (line 4): The compatibility_date has been advanced from "2025-10-11" to "2026-03-16". While "2026-03-16" is a valid date, the web search shows this introduces multiple breaking changes, including changes to Durable Object behavior (delete_all_deletes_alarm becomes default on 2026-02-24) and other runtime updates. Developers must review https://developers.cloudflare.com/workers/configuration/compatibility-flags/ to verify these changes are intentional and that the application handles them correctly.

🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@wrangler.toml` at line 4, The wrangler.toml references a non-existent
tail_consumer service "chittytrack" and upgrades compatibility_date to
"2026-03-16" which may introduce breaking runtime changes; either add/rename a
service definition for "chittytrack" to match the tail_consumers entry or update
tail_consumers to reference an existing service name, and if keeping
compatibility_date="2026-03-16" run targeted tests and review runtime changes
(especially Durable Object behavior like delete_all_deletes_alarm) to ensure the
app handles them, or revert the compatibility_date to the prior value until
verification is complete.

workers_dev = false
account_id = "0bc21e3a5a9de1a4cc843be9c3e98121"

Expand All @@ -14,6 +14,9 @@ id = "a1685cca731f43c397db4e79b80ea075"
pattern = "charge.chitty.cc/*"
zone_name = "chitty.cc"

[[tail_consumers]]
service = "chittytrack"

[observability]
enabled = true

Expand Down
Loading