Skip to content

Milestone: v0.10.1, what the docs promised #120

Closed

Description

@tamnd

Tracking issue for the v0.10.1 milestone. It is a patch release for the things v0.10.0 shipped with, plus the one item v0.10.0 could not measure.

Goal

Close the gap between what a page of documentation promises and what the binary does, and land the CDX filter push once the index server is reachable enough to measure it.

Checklist

Documentation that described something that did not exist:

Messages and checks:

Carried over from v0.10.0, and carried on to v0.10.2:

Ship gate for v0.10.1

  • every command the docs describe is a command the binary has
  • the dataset card names the dataset it is committed to
  • every flag an error message names is a flag that exists
  • the JSON a command writes uses one set of field names
  • every word the help prints is a word someone wrote
  • a rank lookup answers with no flags, the way the host commands do
  • a script can tell an unreachable Common Crawl from a command that is wrong
  • a command refuses a request it cannot satisfy instead of working for half an hour and returning nothing
  • an index server outage does not take out the commands that read from data.commoncrawl.org
  • every read command honours -o, and two names for the same question give the same answer
  • --data-dir moves the whole tree, and config show names what followed it
  • a number a command did not measure is absent from its output rather than zero
  • a connection lost mid-response exits 8, and a missing local file still does not
  • a format nobody can encode is refused rather than rendered as something else
  • every command that has more than one fact to report can report them as data
  • ci is green on main
  • E16: push search filters to the CDX server #60 measured against the live index, or moved out with the reason written down

Open question for the maintainer

main has no branch protection, so gh pr merge --auto merges as soon as GitHub considers a PR mergeable, whether or not ci passed. That is how #118 merged with docs-drift red. Making the ci checks required is a repository setting rather than a code change, so it is a call for you.

Process

Every PR that lands against this milestone gets a comment on this issue with the PR number and one line on what changed, and the matching checklist box is ticked when the linked issue closes. Automated by .github/workflows/milestone-tracker.yml. #110 and #88 merged before this issue existed, so their boxes are ticked by hand here.

Activity

  1. added this to the v0.10.1 milestone on Aug 12, 2026
  2. tamnd commented on Aug 12, 2026

    @tamnd
    OwnerAuthor

    Merged #118, Make the content commands do what the guide said they did.

    Closes:

    The guide promised content quality - reading URLs from stdin, six output fields, a --warc flag and a --lang flag, none of which existed. All four content commands now take - and read a URL per line, a JSON line with a url field works too so search and crawl fetch output pipes straight in, a URL that fails is named and skipped, and the guide was rewritten from what the commands actually emit. Two more real doc errors turned up on the way: the CLI reference claimed content outlinks carries anchor text, and the requirements page claimed crawl fetch reads robots.txt when it only does with --robots.

  3. tamnd commented on Aug 12, 2026

    @tamnd
    OwnerAuthor

    Merged #119, Name the repo the card is committed to.

    Closes:

    The card is now built from the repo the run is pushing to, so a run publishing to somebody else's dataset gets snippets pointing at theirs instead of ours, and local_dir follows the repo name. A card rendered outside a run falls back to ccrawl.DefaultMarkdownRepo, which is also the export flag default now, so the two cannot drift apart again.

  4. github-actions commented on Aug 12, 2026

    @github-actions

    Merged #123, Check the requirements page against the crawl commands too.

    Closes:

  5. github-actions commented on Aug 12, 2026

    @github-actions

    Merged #124, Stop printing flags that do not exist.

    Closes:

  6. github-actions commented on Aug 12, 2026

    @github-actions

    Merged #126, Give the WAT and WET records their JSON names.

    Closes:

  7. github-actions commented on Aug 12, 2026

    @github-actions

    Merged #128, Stop printing help nobody wrote.

    Closes:

  8. github-actions commented on Aug 12, 2026

    @github-actions

    Merged #130, rank: find the table instead of demanding one.

    Closes:

  9. github-actions commented on Aug 12, 2026

    @github-actions

    Merged #132, exit 8 when Common Crawl cannot be reached.

    Closes:

  10. github-actions commented on Aug 12, 2026

    @github-actions

    Merged #136, Refuse crawl seed --max-tier 1 instead of scanning for nothing.

    Closes:

  11. github-actions commented on Aug 12, 2026

    @github-actions

    Merged #139, Keep working from a cached crawl list when the index server is down.

    Closes:

  12. github-actions commented on Aug 12, 2026

    @github-actions

    Merged #142, Make crawls info an operation so -o works.

    Closes:

  13. github-actions commented on Aug 12, 2026

    @github-actions

    Merged #143, Make --data-dir move the cache with it.

    Closes:

  14. github-actions commented on Aug 12, 2026

    @github-actions

    Merged #145, Leave out host counts nothing measured.

    Closes:

  15. github-actions commented on Aug 12, 2026

    @github-actions

    Merged #147, Give a read that fails partway through a response exit 8.

    Closes:

  16. github-actions commented on Aug 12, 2026

    @github-actions

    Merged #148, Refuse an output format nothing can encode.

    Closes:

  17. github-actions commented on Aug 13, 2026

    @github-actions

    Merged #151, Let ccrawl version render as data.

    Closes:

  18. github-actions commented on Aug 13, 2026

    @github-actions

    Merged #134, docs: release notes for v0.10.1.

  19. tamnd commented on Aug 13, 2026

    @tamnd
    OwnerAuthor

    v0.10.1 is out: https://github.com/tamnd/ccrawl-cli/releases/tag/v0.10.1

    Sixteen issues closed and seventeen pull requests merged. Every box above is ticked. The release notes are at docs/content/release-notes/v0-10-1.md.

    One thing this milestone set out to do is not done. #60 wanted a byte count for the pushed CDX filters, and index.commoncrawl.org has been refusing connections for twenty two days, so the measurement cannot be taken. The change itself is written and green in PR #112, but the whole claim it makes is a number, and there is no honest way to publish a number nobody took. #60 and #112 have moved to v0.10.2 and the release notes say plainly that the promise made in v0.10.0 is not kept yet and why.

    Checked against the published darwin arm64 binary rather than a local build:

    $ ccrawl version
    ccrawl 0.10.1 (commit 7813222, built 2026-08-13T02:47:33Z, darwin/arm64, go1.26.5)
    
    $ ccrawl version -o json | jq -r .commit
    7813222
    
    $ ccrawl search 'example.com/*' -o csvv; echo $?
    ccrawl: -o csvv: unknown output format, use one of auto, table, markdown, list, json, jsonl, csv, tsv, url, raw, md, section, sections, template, parquet
    2
    
    $ ccrawl content quality http://127.0.0.1:9/gone -o jsonl; echo $?
    Fetch http://127.0.0.1:9/gone: Get "http://127.0.0.1:9/gone": dial tcp 127.0.0.1:9: connect: connection refused.
    8
    
    $ ccrawl content quality 'http://[::1' -o jsonl; echo $?
    Fetch http://[::1: parse "http://[::1": missing ']' in host.
    1
    

    Closing this one. v0.10.2 is open and has #60 in it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions