Repository navigation
Move README CLI commands to CLI 0.4.0 and catch CLI drift daily - #1
Merged
Merged
Conversation
…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
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.
Fixes the failing weekly Live check (run 39253245551, block 10 "Coding agents").
Why it failed
@brightdata/cli0.4.0 (released 12 Oct 2026) removedbdata pipelines <type>: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
bdata pipelines run <dataset_id> collect_by_url <url>with the four Instagram dataset IDs frombdata pipelines search instagrampipelines listline, which no longer existdiscover_by_urlon the Posts scraper (not documented here, since it is untested)Workflows
cli-syntaxjob, 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.BDATA_CLIpin, also applied tonpx -p @brightdata/clilines, so the jobs that hold the secret run a known versionplanandblockshare one parser in.github/scripts/readme_blocks.pyinstead of two copiesmain, so a manual run on a branch no longer tries to pushmainscrapejob no longer installs the CLI it never usedci.ymlconcurrency and timeoutsVerified
readme_blocks.py cli-syntaxpasses on this README and fails all five lines on the old oneruff,pytest(16 passed) andactionlintpass. The only actionlint output is three info-level shellcheck notes that predate this PR.