If you already have a script that builds an issue, a scheduled workflow can run it when your laptop is closed. Decide where its state will survive between runners before you enable recurring mail.
Test the script manually
Add a workflow with workflow_dispatch and run the newsletter builder in preview mode. Check the rendered subject, item count and original links in its preview output, with private addresses and credentials omitted.
Add a scheduled trigger
Put the workflow on the default branch. A cron expression of 17 7 * * 1 means Monday at 07:17 with the default UTC schedule. Scheduled runs can be delayed, so determine the issue window from saved state rather than actual job start time.
Keep the issue key outside the runner
Use a persistent private store for an issue ID, cutoff and sending state. Serialize jobs sharing the same issue, and review provider acceptance after any timeout before replaying that issue.
on:
workflow_dispatch:
schedule:
- cron: '17 7 * * 1'
concurrency:
group: weekly-reading-digest
cancel-in-progress: false