Schedule weekly content updates on Tuesday at 09:17 Brasilia

Author: ovvesley

.github/workflows/pages.yml

@@ -4,8 +4,8 @@ on:
   push:
     branches: [main]
   schedule:
-    # Brasília is UTC-3: Monday 09:00 = Monday 12:00 UTC.
-    - cron: '0 12 * * 1'
+    # Brasília is UTC-3: Tuesday 09:17 = Tuesday 12:17 UTC.
+    - cron: '17 12 * * 2'
   workflow_dispatch:
     inputs:
       refresh_content:

README.md

@@ -4,7 +4,7 @@ Public website: https://uffescience.github.io/
 
 The live website is a static Next.js application in [`web/`](web/README.md). GitHub Actions exports and deploys it to GitHub Pages. Content and archived images are versioned in `web/data/`; there are no runtime Next.js APIs.
 
-[Update and deployment workflow](https://github.com/UFFeScience/uffescience.github.io/actions/workflows/pages.yml) runs weekly on Monday at 09:00 Brasília and can be run manually. Apify credentials are stored only in Actions Secrets and ignored local environment files.
+[Update and deployment workflow](https://github.com/UFFeScience/uffescience.github.io/actions/workflows/pages.yml) runs weekly on Tuesday at 09:17 Brasília and can be run manually. Apify credentials are stored only in Actions Secrets and ignored local environment files.
 
 See [development and content documentation](web/README.md) for local preview, synchronization, storage and deployment details.
 

web/README.md

@@ -40,7 +40,7 @@ The site reads only stored files during the build. Visits do not call GitHub or
 
 ## Weekly update and deployment
 
-`.github/workflows/pages.yml` is the only active schedule: Monday 12:00 UTC, equivalent to 09:00 Brasília. GitHub may delay scheduled jobs. Prior Apify and macOS schedules were disabled.
+`.github/workflows/pages.yml` is the only active schedule: Tuesday 12:17 UTC, equivalent to 09:17 Brasília. GitHub may delay scheduled jobs. Prior Apify and macOS schedules were disabled.
 
 The workflow updates GitHub data, people and LinkedIn, commits changed content with GITHUB_TOKEN, builds and deploys Pages. Shared concurrency prevents overlapping runs. Bot commits do not trigger another workflow; `[skip ci]` adds a second safeguard. Pushes to main deploy without collecting LinkedIn. Concurrent human changes are rebased without force-pushing; conflicts stop publication instead of overwriting work.