Skip to content

Move README CLI commands to CLI 0.4.0 and catch CLI drift daily - #1

Merged
anil-bd merged 2 commits into
mainfrom
fix/cli-0.4-pipelines
Oct 20, 2026
Merged

anil-bd merged 2 commits into
mainfrom
fix/cli-0.4-pipelines

Conversation

@anil-bd

@anil-bd anil-bd commented Oct 20, 2026

Copy link
Copy Markdown
Collaborator

Fixes the failing weekly Live check (run 39253245551, block 10 "Coding agents").

Why it failed

@brightdata/cli 0.4.0 (released 12 Oct 2026) removed bdata pipelines <type>:

✗ Pipeline types were removed in 0.4.0. Find the scraper with:
  brightdata pipelines search instagram posts

Every CLI line in the README was broken for readers, who get the newest CLI through npx -p @brightdata/cli. Only block 10 went red. Blocks 11-14 stayed green because the workflow ran them on a pinned 0.3.4.

README

  • Uses bdata pipelines run <dataset_id> collect_by_url <url> with the four Instagram dataset IDs from bdata pipelines search instagram
  • Drops the 0.3.x console output sample and the pipelines list line, which no longer exist
  • Removes "the CLI has no route for it": 0.4.0 has discover_by_url on the Posts scraper (not documented here, since it is untested)

Workflows

  • New cli-syntax job, no secret, runs on every push and schedule. It installs the newest CLI and runs every README CLI line with a key the API rejects. A line the CLI still accepts gets a 401. A line it no longer accepts fails before reaching the API. This catches the 12 Oct break the same day, for free, and warns when a new CLI release is out.
  • One BDATA_CLI pin, also applied to npx -p @brightdata/cli lines, so the jobs that hold the secret run a known version
  • plan and block share one parser in .github/scripts/readme_blocks.py instead of two copies
  • A failing block now shows its last six lines and exit code. Before, the summary showed only the hint line and hid the cause.
  • The bot commit message reads "Last check failed …" on failure. It used to say "Last verified" even on a red run.
  • The badge and field-table commits only run from main, so a manual run on a branch no longer tries to push main
  • A failed scheduled run opens one "Live check is failing" issue, or comments on the open one
  • The scrape job no longer installs the CLI it never used
  • pip cache, plus ci.yml concurrency and timeouts

Verified

  • Locally, with CLI 0.4.0, readme_blocks.py cli-syntax passes on this README and fails all five lines on the old one
  • ruff, pytest (16 passed) and actionlint pass. The only actionlint output is three info-level shellcheck notes that predate this PR.
  • Live API run of blocks 10-14 on this branch: running now via workflow_dispatch

…daily

CLI 0.4.0 (12 Oct) removed 'bdata pipelines <type>', so every CLI line in the
README failed for readers. The Monday run caught only block 10: blocks 11-14
ran a pinned 0.3.4 and stayed green.

- README: pipelines run <dataset_id> collect_by_url, with the four Instagram IDs
- live.yml: one parser in .github/scripts/readme_blocks.py for plan and block jobs
- live.yml: new secretless cli-syntax job runs every README CLI line on the newest
  CLI with a rejected key, on every push and schedule
- live.yml: one BDATA_CLI pin, applied to npx lines too; unused CLI install dropped
- live.yml: failing blocks show their last six lines; bot commit names the real state
- live.yml: a failed scheduled run opens or comments on one issue
- ci.yml: concurrency, timeouts, pip cache
@anil-bd
anil-bd merged commit 7ba67d9 into main Oct 20, 2026
14 checks passed
@anil-bd
anil-bd deleted the fix/cli-0.4-pipelines branch October 20, 2026 06:23
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