Run the bump-wasmtime workflow everyday

[fibonacci1729]

Runs everyday and PRs changes only when the release branch needs to bump.

[itowlson]

Could you say more about why you're proposing this? Our actions dashboard is already quite noisy, and a daily action that prints "nothing to do" seems to have limited value. Is it a hedge against Wasmtime changing its release schedule?

[fibonacci1729]

That was my understanding after discussing with @tschneidereit last week. Could you weigh in or correct me if I misunderstood.

[tschneidereit]

Is it a hedge against Wasmtime changing its release schedule?

It is exactly that, yes: we want to maximize the amount of time we have between finding an issue that needs a Wasmtime fix and the Wasmtime release happening, so we want to check as close to the branch date as possible. OTOH, there have been instances of the branch being delayed, so we need to be robust in the face of that.

Our actions dashboard is already quite noisy, and a daily action that prints "nothing to do" seems to have limited value.

I had honestly not considered that there's value in having a clean actions dashboard, because I didn't realize that anyone actively checks that dashboard. If you think that is an important enough thing to optimize for, I can think of some other ways to achieve the goals here, but they involve external mechanisms and a bunch more work, so I'm a bit wary of them.

[itowlson]

Given that the Wasmtime 47 PR has been up for most of a week and nobody has looked at it, we have a ways to go as a project to benefit from "maximis[ing] the amount of time" from finding an issue. grin

For what it's worth, we already delay by a couple of days to allow for small release delays and for "oops we meant to include X" churn in the immediate aftermath of starting a release train. But yes, if the release were delayed longer than that, the cron would miss - I agree it would be nice to be more robust against that.