Build on a schedule and use latest versions of runners

Jay Berkenbilt
1 parent deeface1
Showing 2 changed files with 8 additions and 8 deletions
.github/workflows/main.yml
TODO
@@ -13,6 +13,12 @@ on:
       - 'README*'
       - 'TODO'
   pull_request:
+  schedule:
+    # Building regularly with cron makes it safe for us to use
+    # *-latest with runs-on. If a new version of tools or agents comes
+    # out, we'll find out fast if our builds break on it because we
+    # have reliable testing.
+    - cron: '12 4 * * 5'
 jobs:
   Distfiles:
     # Generate distfiles.zip, which is a prerequisite for the mac and
@@ -41,7 +47,7 @@ jobs:
           name: distribution
           path: distribution
   Windows:
-    runs-on: windows-2019
+    runs-on: windows-latest
     needs: Distfiles
     strategy:
       fail-fast: false
@@ -67,7 +73,7 @@ jobs:
           name: distribution
           path: distribution
   macOS:
-    runs-on: macos-10.15
+    runs-on: macos-latest
     needs: Distfiles
     steps:
       - uses: actions/checkout@v2
@@ -3,8 +3,6 @@ Candidates for upcoming release
  
 * Easy build/test
   * #460: potential malware in fuzzer seed corpus
-  * Consider building workflow on a schedule to detect build rot. This
-    should enable safe use of *-latest on runners.
  
 * Fuzz crashes
   * See "New" below
@@ -24,10 +22,6 @@ Candidates for upcoming release
   * Complete migration. Do a case-insensitive search for azure to find
     documentation references.
  
-  * Build qpdf weekly so we can notice if things start breaking
-    because of changes in the build environment, library dependencies,
-    compiler upgrades, etc.
-
 * See if we can work in Windows Build/External Libraries (below)
  
 * Remember to check work `qpdf` project for private issues