Skip to content

Run the canary's paid Scraper API job weekly; free jobs stay daily - #4

Merged
jehrr merged 1 commit into
mainfrom
ci/weekly-paid-canary-2026-10-16
Oct 16, 2026
Merged

jehrr merged 1 commit into
mainfrom
ci/weekly-paid-canary-2026-10-16

Conversation

@jehrr

@jehrr jehrr commented Oct 16, 2026

Copy link
Copy Markdown
Collaborator

Problem: the canary runs daily, and its scraper-api job calls the paid Scraper API with the TWOCAPTCHA_KEY secret (set in this repo, so every daily run billed a call), so it billed on every scheduled run. The profiles job need no secret and cost nothing.

Change: a second schedule, 41 6 * * 1 (Mondays, at the daily run's hour and minute), is added. The paid job gets if: github.event_name != 'schedule' || github.event.schedule == '41 6 * * 1', so it runs on the weekly schedule and on any manual dispatch, and is skipped on the daily one. The free jobs are not gated and keep running daily. The README paragraph about the second job now says it runs weekly.

Not changed: what each canary job runs and asserts, its thresholds, and its behaviour when a secret is missing (a paid job without its secret still fails with an ::error:: naming it, now on its weekly run). workflow_dispatch still runs every job.

Evidence: the edited workflow parses as YAML and its on.schedule / job if: values were printed from the parsed file (listed above). The offline suite runs in this PR's tests workflow on the head commit. No paid call was made to check this change.

🤖 Generated with Claude Code

https://claude.ai/code/session_01CKsd7q25N19WzUZjrAdzx8

Paid canary paths (proxy, Scraping Browser, captcha) run weekly on Mondays;
free paths keep their daily schedule. A manual dispatch runs everything.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CKsd7q25N19WzUZjrAdzx8
@jehrr
jehrr merged commit 839c748 into main Oct 16, 2026
7 checks passed
jehrr added a commit that referenced this pull request Oct 16, 2026
## Problem

The canary ran daily, and a second Monday cron (added earlier today in
#4) was the only scheduled run allowed to start the paid part, through
`github.event.schedule` gating. The owner's decision (2026-10-16) is now
that every canary runs weekly, free and paid alike, which makes that
gating pointless.

## Resulting behaviour

- `canary.yml` has exactly one cron, `"41 6 * * 1"` (Mondays). The daily
cron is removed.
- The `github.event.schedule` gate on the paid part is removed, so the
Monday run and a manual dispatch run every job the same way.
- A job that needs a secret still fails with an `::error::` naming it
when the secret is missing. Nothing else about the jobs changed.
- Comments and docs that said the canary runs daily (or every morning /
the next day) now say weekly (Mondays). Dated, historical statements
about earlier daily runs are left as they were.
- CHANGELOG: one CI-only line under `[Unreleased]` → Changed, replacing
this morning's "paid canary weekly" line.

Files: `.github/workflows/canary.yml`, `CHANGELOG.md`,
`CONTRIBUTING.md`, `README.md`.

## Evidence

- Every edited workflow parsed with PyYAML: one schedule entry (`"41 6 *
* 1"`), `workflow_dispatch` kept, no `event.schedule` reference and no
job-level schedule `if:` left.
- CI (`tests` workflow) on the exact head commit is checked before
merge.
- No canary was dispatched and no paid call was made.

## Not changed

- Release/version: none. Dependabot and audit schedules are untouched.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

https://claude.ai/code/session_01CKsd7q25N19WzUZjrAdzx8

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant