search

gradle-update / update-gradle-wrapper-action

Keep Gradle Wrapper up-to-date with this action.
Apache License 2.0
49 stars 17 forks source link

Action is disabled after 60 days of inactivity #799

Closed ov7a closed 8 months ago

ov7a commented 9 months ago

GitHub disables scheduled action after 60 days of inactivity:

Warning: To prevent unnecessary workflow runs, scheduled workflows may be disabled automatically. When a public repository is forked, scheduled workflows are disabled by default. In a public repository, scheduled workflows are automatically disabled when no repository activity has occurred in 60 days.

This means if there is no new version of Gradle in 60 days, the workflow will be disabled.

This happened with 8.5 and 8.6 - there are 65 days between them.

There are some workarounds like keepalive-workflow, but I'm not sure if it would be healthy for the ecosystem

StefMa commented 8 months ago

I guess you mix things here @ov7a . It doesn't matter if there is a delay between the Gradle releases of more than 60 days. The scheduled workflows will be disabled in case there is no activity on public repositories.

So given the following timetable: 1.1.2024: Gradle 8.5 release happen and will be merged 1.2.2024: Any activity happen to that repo (e.g. update readme should be enough) In this case the workflow will be scheduled to disabled after 60 days from "today" (1.2.2024).

Does this make sense?

ov7a commented 8 months ago

@StefMa oh, I misread “no repository activity” as “no repository activity by the action”. This makes sense. Thank you!