[rubas-agent]

Before

task outdated on main:

name    old req compatible latest new req
====    ======= ========== ====== =======
scraper 0.27    0.27.0     0.29.0 0.29

cargo update also found 32 newer compatible versions in Cargo.lock.

Problem

The lock file was behind, and scraper was one major version behind (0.28 was not released on GitHub, so 0.29 is the next one).

After

task outdated shows no update. The search parser still finds the results on a live Kagi page.

Crate	Before	After
scraper (major)	0.27.0	0.29.0
tokio	1.53.1	1.54.1
serde_json	1.0.151	1.0.154
selectors (via scraper)	0.38.0	0.41.0
cssparser (via scraper)	0.37.0	0.38.0
html5ever (via scraper)	0.39.0	0.40.1

Live run with the new parser:

$ kagi-search --limit 3 --output json rust scraper crate | jq -c '{n: (.results|length), first: .results[0].title}'
{"n":3,"first":"scraper - Rust - Docs.rs"}

Details

Changes. Two commits: first cargo update, then scraper 0.27 to 0.29 in Cargo.toml. The version of kagi stays at 0.7.0, so this PR does not start a release.

scraper 0.29. The release notes list docs, a new selectors version, and a new cssparser version with changed error handling inside scraper. Our code in src/parse.rs uses only Html::parse_document, Selector::parse, and select. Their API did not change, and the source of 0.29 marks nothing as deprecated. No code change was necessary.

Checks (local).

• cargo fmt --check, npx dprint check: pass.
• cargo clippy --all-targets -- -D warnings: pass.
• zizmor --offline --persona=pedantic .github/workflows: no findings.
• cargo test: all tests pass, with the 19 parser tests on the HTML fixtures.
• cargo test --test live -- --ignored (real Kagi service): 4 of 4 pass.
• cargo check --release, cargo machete, cargo deny check advisories bans sources: pass.
• Live kagi-search with 0.27 (main) and 0.29 (this branch) gives the same results.