Should tests depend on Baseline statuses that change over time?

[rviscomi]

The tests in tests/rules/require-baseline.test.js hard-code expected behaviors based on the current Baseline status of specific features. For example, today this test correctly expects container queries not to be Baseline Widely available:

css/tests/rules/require-baseline.test.js

Lines 148 to 162 in a9692b0

	code: "@container (min-width: 800px) { a { color: red; } }",
	errors: [
	{
	messageId: "notBaselineAtRule",
	data: {
	atRule: "container",
	availability: "widely",
	},
	line: 1,
	column: 1,
	endLine: 1,
	endColumn: 11,
	},
	],
	},

However, we know that container queries will become Widely available on August 14, 2025, because it's exactly 30 months after its Newly available date. So the next time web-features is updated and generate-baseline.js runs, this test will start failing because the require-baseline rule will no longer warn about its usage.

Is that intentional?