GitHub Actions will disable scheduled workflows in certain repos

I just got the following email from GitHub: "Scheduled workflows will be disabled by default in forks of public repos and in public repos with no activity for 60 consecutive days. W e’re making two changes to the usage policy for GitHub Actions. These changes will enable GitHub Actions to scale with the incredible adoption we’ve seen from the GitHub community. Here’s a quick overview: 1. Starting today, scheduled workflows will be disabled by default in new forks of public repositories. 2. Scheduled workflows will be disabled in public repos with no activity for 60 consecutive days." There were some Q&A's below that, but the thing that I'm more nervous about is the fact that 'inactive' repos will not get scheduled runs. I typically use a weekly CI job on every OSS library I set up, and for some of them, I only 'maintain' them once every 3-6 months, since they're feature complete and only need tweaks here and there. This is a little upsetting, and I guess I'll have to write some automation that pushes a pointless commit to a text file every couple months.