Skip to content

build(deps): bump github.com/openclaw/crawlkit from 0.17.5-0.20261113151307-653b46f63cf0 to 0.18.0 - #446

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/go_modules/github.com/openclaw/crawlkit-0.18.0
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/go_modules/github.com/openclaw/crawlkit-0.18.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 19, 2026

Copy link
Copy Markdown
Contributor

Bumps github.com/openclaw/crawlkit from 0.17.5-0.20261113151307-653b46f63cf0 to 0.18.0.

Release notes

Sourced from github.com/openclaw/crawlkit's releases.

v0.18.0

0.18.0 - 2026-11-15

Highlights: Add verified private backup transfers and shared seed APIs, fix scheduler and archive-path handling, and include the Go security fix for GO-2026-6859.

  • Add an opt-in private native backup client and crawlctl preservation upload and download commands. Reuse existing opaque backup bytes, verify immutable chunk and complete-file identities, and restore only into a new directory. Byte verification does not claim native database restore qualification.

  • Add exact file-section inputs to private preservation uploads. Large closed files can be transferred in separately pinned volumes without temporary copies; section receipts do not claim whole-file restore qualification.

  • Use Go 1.27.4 for development and downstream qualification to pick up the standard-library fix for GO-2026-6859.

  • Reject malformed crawlctl logs --tail counts instead of silently accepting an integer prefix.

  • Save discovered executables as absolute paths so relative app selections work from another runner directory.

  • Preserve each job's latest text status when history keys collide or runs finish in the same second.

  • Keep scheduler due checks scoped to the exact job and repository when colon-containing names share a legacy history key.

  • Keep scheduler status scoped to the exact job name when another job or repository history key shares its prefix.

  • Allow native independent review in either Codex or OpenClaw while preserving pinned, isolated, read-only review and existing validation gates.

  • Recognize supported legacy crawl apps selected by executable path while retaining the selected path in their default jobs.

  • Report discovery errors for malformed app metadata or missing manifest IDs while preserving supported legacy fallbacks.

  • Reject fractional-second launchd and systemd intervals instead of silently shortening the requested schedules.

  • Preserve literal SQLite database paths in control metadata so trailing whitespace does not select a different file for size and modification stats.

  • Reject cron paths containing line feeds instead of rendering a broken multiline crontab entry.

  • Preserve percent signs in cron executable, config, and log paths instead of truncating the scheduled command.

  • Update the SQLite driver to v1.62.0 with its required libc v1.80.1 runtime, x/sys to v0.50.0, and the paired CodeQL actions to v4.39.3; retain the Go 1.27.0 minimum.

  • Reject cron intervals that cannot keep a uniform cadence across hour boundaries instead of silently rendering shorter gaps.

  • Bound change and seed receipt reads before decoding and reject trailing response data instead of accepting a valid first JSON object.

  • Add a closed durable-cluster snapshot profile to the existing GitHub seed transport, with a content-bound token and four ordered tables. Existing private-report bytes and validation remain unchanged; projection, source qualification and receiver policy stay with the applications.

... (truncated)

Changelog

Sourced from github.com/openclaw/crawlkit's changelog.

0.18.0 - 2026-11-15

Highlights: Add verified private backup transfers and shared seed APIs, fix scheduler and archive-path handling, and include the Go security fix for GO-2026-6859.

  • Add an opt-in private native backup client and crawlctl preservation upload and download commands. Reuse existing opaque backup bytes, verify immutable chunk and complete-file identities, and restore only into a new directory. Byte verification does not claim native database restore qualification.

  • Add exact file-section inputs to private preservation uploads. Large closed files can be transferred in separately pinned volumes without temporary copies; section receipts do not claim whole-file restore qualification.

  • Use Go 1.27.4 for development and downstream qualification to pick up the standard-library fix for GO-2026-6859.

  • Reject malformed crawlctl logs --tail counts instead of silently accepting an integer prefix.

  • Save discovered executables as absolute paths so relative app selections work from another runner directory.

  • Preserve each job's latest text status when history keys collide or runs finish in the same second.

  • Keep scheduler due checks scoped to the exact job and repository when colon-containing names share a legacy history key.

  • Keep scheduler status scoped to the exact job name when another job or repository history key shares its prefix.

  • Allow native independent review in either Codex or OpenClaw while preserving pinned, isolated, read-only review and existing validation gates.

  • Recognize supported legacy crawl apps selected by executable path while retaining the selected path in their default jobs.

  • Report discovery errors for malformed app metadata or missing manifest IDs while preserving supported legacy fallbacks.

  • Reject fractional-second launchd and systemd intervals instead of silently shortening the requested schedules.

  • Preserve literal SQLite database paths in control metadata so trailing whitespace does not select a different file for size and modification stats.

  • Reject cron paths containing line feeds instead of rendering a broken multiline crontab entry.

  • Preserve percent signs in cron executable, config, and log paths instead of truncating the scheduled command.

  • Update the SQLite driver to v1.62.0 with its required libc v1.80.1 runtime, x/sys to v0.50.0, and the paired CodeQL actions to v4.39.3; retain the Go 1.27.0 minimum.

  • Reject cron intervals that cannot keep a uniform cadence across hour boundaries instead of silently rendering shorter gaps.

  • Bound change and seed receipt reads before decoding and reject trailing response data instead of accepting a valid first JSON object.

  • Add a closed durable-cluster snapshot profile to the existing GitHub seed transport, with a content-bound token and four ordered tables. Existing private-report bytes and validation remain unchanged; projection, source qualification and receiver policy stay with the applications.

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [github.com/openclaw/crawlkit](https://github.com/openclaw/crawlkit) from 0.17.5-0.20261113151307-653b46f63cf0 to 0.18.0.
- [Release notes](https://github.com/openclaw/crawlkit/releases)
- [Changelog](https://github.com/openclaw/crawlkit/blob/main/CHANGELOG.md)
- [Commits](https://github.com/openclaw/crawlkit/commits/v0.18.0)

---
updated-dependencies:
- dependency-name: github.com/openclaw/crawlkit
  dependency-version: 0.18.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot requested a review from a team as a code owner November 19, 2026 18:43
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file go Pull requests that update go code labels Nov 19, 2026
@clawsweeper

clawsweeper Bot commented Nov 19, 2026 •

Copy link
Copy Markdown

🦞👀
ClawSweeper picked this up.

Pull request received. I will update this pull request when review starts.

ClawSweeper review complete

ClawSweeper finished reviewing this revision. The review result is being finalized.

View the workflow run.

@clawsweeper clawsweeper Bot added P3 Low-risk cleanup, docs, polish, ergonomics, or speculative feature. rating: 🦐 gold shrimp Decent PR readiness signal, but merge confidence is limited. status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR. labels Nov 19, 2026
@clawsweeper

clawsweeper Bot commented Nov 19, 2026

Copy link
Copy Markdown

Codex review: needs maintainer review before merge.

What this changes

This PR updates Crawlkit to v0.18.0 and replaces its module checksums.

Example: A remote change receipt contains valid JSON followed by another JSON object.

  • Before: The older transport can discard the trailing object and accept the receipt.
  • After: Crawlkit v0.18.0 rejects the complete response as an invalid receipt.

Review scores

Measure Result What it means
Overall readiness 🦐 gold shrimp (3/6) Focused, useful dependency update with passing exact-head CI and no actionable finding; validation evidence consists of automated checks rather than exercised Gitcrawl runtime behavior.
Proof confidence 🦐 gold shrimp (3/6) This Dependabot maintenance PR is outside the contributor runtime-proof gate; exact-head CI supports compatibility, and no target code was executed during this read-only review.
Patch quality 🐚 platinum hermit (4/6) No actionable review findings were identified.

Product

Kind: Maintenance · Worth it: Yes · Fix scope: Complete
User problem: Gitcrawl remains pinned to a development revision that lacks subsequent remote-receipt and database-path fixes.
Reason: The published release preserves the required APIs, supplies relevant fixes, and matches Gitcrawl's existing SQLite and platform dependency versions.

Merge readiness

✅ Ready for maintainer review

Keep open: main still pins the older Crawlkit revision, and this focused update brings useful upstream fixes without a concrete regression found.

Priority: P3
Reviewed head: 24af10022fb29d5161d6b03bc7e56b1d0cfe4994

Before merge

None.

Findings

None.

Agent review details

How this fits together

Gitcrawl uses Crawlkit for archive storage helpers, control metadata, and authenticated remote transport; saved delivery batches enter the transport and verified receipts return to Gitcrawl.

flowchart LR
  A[Gitcrawl CLI] --> B[Delivery outbox]
  B --> C[Crawlkit client]
  C --> D[Remote archive]
  D --> E[Receipt validation]
  E --> B
Loading

Technical review

Best possible solution:

Land the focused published-tag update through the existing dependency-update workflow.

Do we have a high-confidence way to reproduce the issue?

This dependency update reports no Gitcrawl reproduction; source inspection confirms that Gitcrawl consumes the changed receipt transport.

Is this the best way to solve the issue?

Updating the existing direct dependency and checksums is the smallest complete way to consume the published fixes.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning medium; reviewed against f200e3eef1cb.

Provenance checked

  • Crawlkit module version and checksums keeps the original intent (673da05: Select the shared APIs needed to export bounded native cluster snapshots.)

Testing

Proof path: unit tests only.

Security

None.

Evidence

What I checked:

  • Exact introduced change remains absent from main: The pinned diff changes only the Crawlkit requirement and two checksum entries; current default branch remains f200e3e with the older pseudo-version. (go.mod:15, 24af10022fb2)
  • Dependency contract applies: Gitcrawl directly calls Crawlkit ApplyChanges and records its verified receipt, making Crawlkit remote transport behavior and repository compatibility policy relevant. (internal/remotedelivery/deliver_changes.go:109, f200e3eef1cb)
  • Published tag preserves required APIs and adds bounded receipt reads: The old revision is an ancestor of v0.18.0. The comparison retains seed APIs and introduces bounded receipt reads through the existing authenticated transport; fix(remote): reject oversized and trailing receipt data crawlkit#234 explains the oversized and trailing-response failures. (remote/changes.go:107, 6dfd4d83a556)
  • Existing pin provenance: The pseudo-version was selected alongside bounded native cluster snapshot support; the update advances to a descendant release rather than removing those APIs. (go.mod:15, 673da0531e69)
  • Exact-head validation: The reviewed head has seven successful checks and neutral CodeQL, including Linux, macOS, Windows, documentation, container, and secret-scanning checks; no check failed. (.github/workflows/ci.yml:19, 24af10022fb2)
  • Policy and inspection limits: Read the complete root policy and verification checklist; no maintainer-notes directory or pr-simplify skill exists. The task's single-reviewer and read-only rules override independent review and local test execution. Older follow-history encounters an unavailable object; the relevant pin history is available. Final status is clean, and no worktree was created. (AGENTS.md:3, 24af10022fb2)

Likely related people:

  • Peter Steinberger: Raw commit 144860b adds go.mod:18 relative to its recorded parents. This identifies author metadata, not feature responsibility or a PR merger. (role: source-line author; confidence: high; commits: 144860b762b0; files: go.mod)

Preflight source

Source unknown. Source comparison at the observed PR snapshot only. Completion is self-reported; body, policy, tests, execution, and report bytes are not verified.

Labels

Label changes:

  • add P3: Routine dependency maintenance with useful upstream fixes and no demonstrated urgent Gitcrawl failure.
  • add rating: 🦐 gold shrimp: Overall readiness is 🦐 gold shrimp; proof is 🦐 gold shrimp and patch quality is 🐚 platinum hermit.
  • add status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR.

Label justifications:

  • P3: Routine dependency maintenance with useful upstream fixes and no demonstrated urgent Gitcrawl failure.
  • rating: 🦐 gold shrimp: Overall readiness is 🦐 gold shrimp; proof is 🦐 gold shrimp and patch quality is 🐚 platinum hermit.
  • status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR.

Rating scale

6/6 🦀 challenger crab · 5/6 🦞 diamond lobster · 4/6 🐚 platinum hermit · 3/6 🦐 gold shrimp · 2/6 🦪 silver shellfish · 1/6 🧂 unranked krab. Overall follows the weaker of proof and patch quality; ✨ marks media proof (a screenshot, video, or linked artifact) that directly shows the changed behavior.

Workflow

ClawSweeper edits this one comment on every review. Comment @clawsweeper re-review for a fresh review only. Repair and merge execution lanes are retired.

Reviewed November 19, 2026, 1:56 PM ET / 18:56 UTC.

This branch has not been deployed

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

Labels

dependencies Pull requests that update a dependency file go Pull requests that update go code P3 Low-risk cleanup, docs, polish, ergonomics, or speculative feature. rating: 🦐 gold shrimp Decent PR readiness signal, but merge confidence is limited. status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants