Repository navigation
Run the canary's paid Scraper API job weekly; free jobs stay daily - #4
Merged
Merged
Conversation
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
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem: the canary runs daily, and its
scraper-apijob calls the paid Scraper API with theTWOCAPTCHA_KEYsecret (set in this repo, so every daily run billed a call), so it billed on every scheduled run. Theprofilesjob 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 getsif: 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_dispatchstill runs every job.Evidence: the edited workflow parses as YAML and its
on.schedule/ jobif:values were printed from the parsed file (listed above). The offline suite runs in this PR'stestsworkflow on the head commit. No paid call was made to check this change.🤖 Generated with Claude Code
https://claude.ai/code/session_01CKsd7q25N19WzUZjrAdzx8