With recent releases, I can't do this anymore:

import { compatibilityDate } from 'workerd'

And then use that supplied compatibilityDate in the config.

workerd complains: Can't set compatibility date in the future: "2026-03-05". Today's date (UTC) is "2026-02-26".

But:

> require('workerd').version
'1.20260305.0'
> require('workerd').compatibilityDate
'2026-03-05'

This worked just a few weeks ago

This is a breaking change for the workerd package and it should have been 2.202603... then instead of 1.202603....

Why is it even checking the system clock, I'm using the exact same compatibilityDate which it claims to support and exports.

Why is that exported at all if it doesn't work when supplied in config?
What does that exported compatibilityDate even mean then?