[dependabot]

Bumps fsspec from 2025.12.0 to 2026.6.0.

Commits

• a245700 changelog (#2049)
• 652325d Fix async cat ranges on error (#2045)
• 073aac8 Forward kwargs from cat_ranges to cat_file (#2044)
• 2818611 FTP: preserve filenames containing whitespace in _mlsd2 (#2043)
• c879384 Prevent attribute error by checking for 'forced' attribute before flushing ca...
• 71b8a6b Reflect async _walk correctly (#2040)
• 5eec9f9 Fix: Omit threading.get_ident() from cache token for async implementations ...
• 8643878 Small safety improvements (#2039)
• a1c16ab Honour simple_templates everywhere in referenceFS (#2029)
• 85facaa Fix infinite recursion in expand_path when resolving paths with glob magic ch...
• Additional commits viewable in compare view

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)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

---

Summary by cubic

Updates fsspec to 2026.6.0 in uv.lock, replacing the previous version-specific markers for older Python versions with a single version for all supported environments.

^{Written for commit 0fc19d9. Summary will update on new commits.}

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: Repository: JWEB0689/coderabbit/.coderabbit.yaml
• Review profile: CHILL
• Plan: Advanced
• Run ID: aa836505-f80d-478b-9796-f52d4cfda810

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[kilo-code-bot]

Code Review Roast 🔥

Verdict: No Issues Found | Recommendation: Merge

Oh wait, this PR is actually clean. I need to sit down. I had my flamethrower warmed up and everything.

What I checked before throwing it away: the diff touches exactly one file — uv.lock — and it is a generated lockfile, so the "skip lock files" rule applies. But I didn't want to wave it through on a technicality, so I traced the resolution:

• The base lock carried two fsspec entries split at python_full_version < '3.13' (2025.12.0 for 3.12, 2026.6.0 for 3.13+). That fork was a fossil: it traces back to gcsfs/pinecone-datasets in commit 6e13fa66, where gcsfs pins fsspec to an exact matching version and only the 3.13+ gcsfs release was allowed on newer interpreters. When those packages were dropped, the split stayed behind as lockfile sediment.
• This bump re-resolves fsspec across every environment and collapses the fork into one entry, so huggingface-hub now depends on { name = "fsspec" } with no version/marker split. The stale 2025.12.0 entry and every reference to it are gone — no dangling pins left behind.
• fsspec is purely transitive (via huggingface-hub); nothing in pr_agent/ imports it, so no application code paths are in the blast radius.
• Python 3.12 — the project's floor (requires-python = ">=3.12") and the version CI actually runs (unit-tests-native matrix: 3.12 / 3.13 / 3.14, plus the 3.12 publish jobs) — is now covered by the same fsspec build as 3.13/3.14, so the newly-unified environment is exercised by the existing test matrix rather than shipping untested.
• Upstream 2025.12.0 → 2026.6.0 is fixes-only: async cat_ranges error handling, kwargs forwarding to cat_file, FTP whitespace-preserving _mlsd2, referenceFS template handling, expand_path glob-recursion fix, and the threading.get_ident() cache-token fix. No breaking API changes announced.

📊 Overall: Like finding a unicorn in production — I didn't think clean PRs existed anymore, but here we are. A lockfile that deletes 24 lines and adds one, and does it correctly. Somebody read the resolution markers.

Files Reviewed (1 file)

• uv.lock - 0 issues

---

_{Reviewed by free · Input: 49.4K · Output: 14.7K · Cached: 556.9K}