Skip to content

Move the daily release compat date 7 days into the future#6043

Merged
penalosa merged 5 commits intomainfrom
penalosa/daily-release-week
Feb 19, 2026
Merged

Move the daily release compat date 7 days into the future#6043
penalosa merged 5 commits intomainfrom
penalosa/daily-release-week

Conversation

@penalosa
Copy link
Copy Markdown
Contributor

@penalosa penalosa commented Feb 9, 2026

Fixes #6008

@penalosa penalosa requested review from a team as code owners February 9, 2026 18:23
@kentonv
Copy link
Copy Markdown
Member

kentonv commented Feb 9, 2026

IMO we should also adjust the validation code to still enforce that the date can't be newer than today.

diff --git a/src/workerd/io/compatibility-date.c++ b/src/workerd/io/compatibility-date.c++
index be2ec8b4f..6db121f05 100644
--- a/src/workerd/io/compatibility-date.c++
+++ b/src/workerd/io/compatibility-date.c++
@@ -115,6 +115,16 @@ static void compileCompatibilityFlags(kj::StringPtr compatDate,
                 "date supported by this server binary is \"",
                 SUPPORTED_COMPATIBILITY_DATE, "\"."));
       }
+
+      // workerd is built with SUPPORTED_COMPATIBILITY_DATE set a little bit into the futurue, so
+      // that the build can support setting the compat date to today until the next release is
+      // ready. But we don't want people to actually set their compat date in the future, so let's
+      // check against the clock time as well.
+      if (CompatDate::today() < parsedCompatDate) {
+        errorReporter.addError(
+            kj::str("Can't set compatibility date in the future: ", parsedCompatDate));
+      }
+
       break;
 
     case CompatibilityDateValidation::CURRENT_DATE_FOR_CLOUDFLARE:

@penalosa penalosa requested a review from a team as a code owner February 9, 2026 18:39
@MattieTK
Copy link
Copy Markdown
Member

MattieTK commented Feb 9, 2026

We should do a changelog on this or some other kind of comms. New docs and link to them as part of the error message. Happy to help do that.

@vicb
Copy link
Copy Markdown
Contributor

vicb commented Feb 9, 2026

@penalosa Looks like this test needs to be updated

@codspeed-hq
Copy link
Copy Markdown

codspeed-hq bot commented Feb 17, 2026

Merging this PR will degrade performance by 16.3%

❌ 1 regressed benchmark
✅ 69 untouched benchmarks
⏩ 129 skipped benchmarks1

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Performance Changes

Benchmark BASE HEAD Efficiency
jsonResponse[Response] 39.8 µs 47.5 µs -16.3%

Comparing penalosa/daily-release-week (e14aba6) with main (605e9c5)

Open in CodSpeed

Footnotes

  1. 129 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports.

@codecov-commenter
Copy link
Copy Markdown

codecov-commenter commented Feb 18, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 70.65%. Comparing base (605e9c5) to head (e14aba6).
⚠️ Report is 13 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #6043      +/-   ##
==========================================
- Coverage   70.66%   70.65%   -0.01%     
==========================================
  Files         409      409              
  Lines      109381   109388       +7     
  Branches    18072    18073       +1     
==========================================
- Hits        77289    77284       -5     
- Misses      21244    21256      +12     
  Partials    10848    10848              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@penalosa penalosa disabled auto-merge February 18, 2026 08:58
@penalosa penalosa enabled auto-merge (squash) February 18, 2026 08:58
@penalosa penalosa force-pushed the penalosa/daily-release-week branch from e27fb8b to a211cb8 Compare February 18, 2026 09:44
@penalosa penalosa disabled auto-merge February 18, 2026 10:39
@penalosa penalosa enabled auto-merge (squash) February 18, 2026 10:39
@penalosa penalosa force-pushed the penalosa/daily-release-week branch 3 times, most recently from 6813c4b to ea3dcce Compare February 18, 2026 22:42
@penalosa penalosa force-pushed the penalosa/daily-release-week branch from 86f87b8 to e14aba6 Compare February 19, 2026 16:24
@penalosa penalosa merged commit 7ae2f9d into main Feb 19, 2026
34 of 36 checks passed
@penalosa penalosa deleted the penalosa/daily-release-week branch February 19, 2026 17:29
@ChALkeR
Copy link
Copy Markdown

ChALkeR commented Feb 26, 2026

This is a breaking change that caused a regression when consuming workerd npm package
See #6188

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.

Set the supported compatibility date to a week in the future

7 participants