fix(deps): update dependency fsspec to >=2025.9.0,<=2025.9.0

[dreadnode-renovate-bot]

This PR contains the following updates:

Package	Change	Age	Confidence
fsspec (changelog)	>=2023.1.0,<=2025.3.0 -> >=2025.9.0,<=2025.9.0

---

Release Notes

fsspec/filesystem_spec (fsspec)

v2025.9.0

Compare Source

v2025.7.0

Compare Source

v2025.5.1

Compare Source

v2025.5.0

Compare Source

v2025.3.2

Compare Source

v2025.3.1

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[dreadnode-renovate-bot]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: uv.lock

Command failed: uv lock --upgrade-package fsspec
Using CPython 3.13.7 interpreter at: /opt/containerbase/tools/python/3.13.7/bin/python3
  × No solution found when resolving dependencies for split (markers:
  │ python_full_version >= '3.12' and python_full_version < '3.14'):
  ╰─▶ Because dreadnode[training] depends on datasets>=4.0.0 and only
      datasets<=4.0.0 is available, we can conclude that dreadnode[training]
      depends on datasets==4.0.0. (1)

      Because only the following versions of fsspec[http] are available:
          fsspec[http]<=2023.1.0
          fsspec[http]==2023.3.0
          fsspec[http]==2023.4.0
          fsspec[http]==2023.5.0
          fsspec[http]==2023.6.0
          fsspec[http]==2023.9.0
          fsspec[http]==2023.9.1
          fsspec[http]==2023.9.2
          fsspec[http]==2023.10.0
          fsspec[http]==2023.12.0
          fsspec[http]==2023.12.1
          fsspec[http]==2023.12.2
          fsspec[http]==2024.2.0
          fsspec[http]==2024.3.0
          fsspec[http]==2024.3.1
          fsspec[http]==2024.5.0
          fsspec[http]==2024.6.0
          fsspec[http]==2024.6.1
          fsspec[http]==2024.9.0
          fsspec[http]==2024.10.0
          fsspec[http]==2024.12.0
          fsspec[http]==2025.2.0
          fsspec[http]>=2025.3.0
      and datasets==4.0.0 depends on fsspec[http]>=2023.1.0,<=2025.3.0, we can
      conclude that datasets==4.0.0 depends on fsspec>=2023.1.0,<=2025.3.0.
      And because we know from (1) that dreadnode[training] depends on
      datasets==4.0.0, we can conclude that dreadnode[training] depends on
      fsspec>=2023.1.0,<=2025.3.0.
      And because only fsspec[s3]<=2025.9.0 is available, we can conclude that
      dreadnode[training] and fsspec[s3]==2025.9.0 are incompatible.
      And because your project depends on fsspec[s3]==2025.9.0 and your
      project requires dreadnode[training], we can conclude that your
      project's requirements are unsatisfiable.