Change daily release version patch to 0

[DaniFoldi]

I noticed that lately the automatically released versions of workerd and workers-types end with .1. I found that 586925d introduced

workerd/.github/workflows/release.yml

Lines 33 to 37 in e612e24

	- id: echo
	run: |
	echo "date=$(cat src/workerd/io/release-version.txt)" >> $GITHUB_OUTPUT;
	echo "version=${{ (github.event_name != 'push' && inputs.prerelease == true) && '0' || '1'}}.$(cat src/workerd/io/release-version.txt | tr -d '-').${{ github.event_name == 'push' && '1' || inputs.patch }}" >> $GITHUB_OUTPUT;
	echo "types_version=${{ (github.event_name != 'push' && inputs.prerelease == true) && '0' || '4'}}.$(cat src/workerd/io/release-version.txt | tr -d '-').${{ github.event_name == 'push' && '1' || inputs.patch }}" >> $GITHUB_OUTPUT;

and I believe the && '0' -> && '1' changes weren't intentional. cc @penalosa as the author of the daily versioning script, apologies if I missed something that makes it necessary.

[penalosa]

Thanks for this! For context, this was changed because we had a period in early March where the minor version of workerd was conflicting with already publishd versions, and so we wanted to keep daily publishes succeeding and not conflicting.

[codspeed-hq]

Merging this PR will degrade performance by 28.58%

⚠️ Different runtime environments detected

Some benchmarks with significant performance changes were compared across different runtime environments,
which may affect the accuracy of the results.

Open the report in CodSpeed to investigate

❌ 1 regressed benchmark
✅ 71 untouched benchmarks
⏩ 129 skipped benchmarks¹

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

Performance Changes

	Benchmark	BASE	HEAD	Efficiency
❌	simpleStringBody[Response]	19.2 µs	26.9 µs	-28.58%

---

_{Comparing DaniFoldi:fix-release-patch-version (894b495) with main (e612e24)}

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. ↩