Use the date that the plugin is built as the default compatibility date (#13653)

Author: jamesopstad

.changeset/silent-bananas-shop.md

@@ -0,0 +1,7 @@
+---
+"@cloudflare/vite-plugin": patch
+---
+
+Use the date that the plugin is built as the default compatibility date.
+
+When no compatibility date was set by the user, the plugin was falling back to the current date. This meant that the date could get ahead of the latest date supported by the installed version of workerd. We now populate the default compatibility date when the plugin is built. This means that it is updated with each release but then stays fixed.

packages/vite-plugin-cloudflare/playground/bindings/__tests__/shortcuts.spec.ts

@@ -1,7 +1,7 @@
 {
 	"name": "worker",
 	"main": "./src/index.ts",
-	"compatibility_date": "2024-12-30",
+	// compatibility date omitted to test fallback
 	"services": [
 		{
 			"binding": "TEST_IF_VITE_CRASH_WITH_UNKNOWN_NAMED_ENTRYPOINT",

packages/vite-plugin-cloudflare/playground/bindings/wrangler.auxiliary.jsonc

@@ -553,9 +553,8 @@ describe("resolvePluginConfig - zero-config mode", () => {
 
 		expect(result.type).toBe("assets-only");
 		const assetsOnlyResult = result as AssetsOnlyResolvedConfig;
-		expect(assetsOnlyResult.config.compatibility_date).toMatch(
-			/^\d{4}-\d{2}-\d{2}$/
-		);
+		// The compatibility date is mocked for the tests
+		expect(assetsOnlyResult.config.compatibility_date).toBe("2024-01-01");
 	});
 
 	test("should allow config() to add main in zero-config mode", ({