Fix auto-release schedule

[jesseduffield]

It was previously on each saturday. Splitting this out from #4307 in case that takes longer to merge.

• PR Description

• Please check if the PR fulfills these requirements

• Cheatsheets are up-to-date (run go generate ./...)
• Code has been formatted (see here)
• Tests have been added/updated (see here for the integration test guide)
• Text is internationalised (see here)
• If a new UserConfig entry was added, make sure it can be hot-reloaded (see here)
• Docs have been updated if necessary
• You've read through your own file changes for silly mistakes etc

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
Report missing for 101bbb01	✅ ∅

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (101bbb0)	Report Missing	Report Missing	Report Missing
Head commit (a81f9ea)	53095	45994	86.63%

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#4308)	0	0	∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

_{Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more}

Footnotes

1. Codacy didn't receive coverage data for the commit, or there was an error processing the received data. Check your integration for errors and validate that your coverage setup is correct. ↩

[TheFoon]

This might still be the wrong schedule.

I came across this while just browsing the changes in recent releases, so I might be wrong. But basically I think this change is just going to make the problem worse. Cron is a bit weird when it comes to both day of week AND day of month being provided. Most implementations (any I've worked with at least) will 'OR' the two conditions, so your schedule will trigger on the first 7 days of the month, and then also on every Saturday. Relevant SO question I found, you can also see this when clicking 'next' above the expression on crontab.guru

I'm not sure if github does something special, or if they have a different way to provide schedules, but if your goal is to make releases less frequent, I think this needs to be reverted. Again, please double check this info as I'm going solely on intuition and 10 minutes of Googling, but I just wanted to bring this to your attention

[stefanhaller]

@TheFoon Thanks for bringing this up; I think you are right.

Judging from a few other SO posts it seems the only way to solve this is to set the cron schedule back to '0 2 * * 6', and then have an extra CI step that errors if we are not in the first week (e.g. using something like [ $(date +%e) -lt 8 ] || exit 1).

[stefanhaller]

Fixed by #4364 (hopefully).