chore: Update Python support, datalad and git-annex deps

[effigies]

No description provided.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 78.42%. Comparing base (9be9c31) to head (04644e0).
⚠️ Report is 8 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #143   +/-   ##
=======================================
  Coverage   78.42%   78.42%           
=======================================
  Files           7        7           
  Lines         394      394           
  Branches       66       66           
=======================================
  Hits          309      309           
  Misses         61       61           
  Partials       24       24           

Flag	Coverage Δ
api,datalad	53.29% <ø> (ø)
api,dls3	40.60% <ø> (ø)
api,s3	64.21% <ø> (ø)
config	57.36% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[effigies]

Delaying merge pending decision about squashing skeleton updates.

@oesteban I pinged you on Slack, but in case it's easier to respond here:

Any opposition to squashing

commit 1a41e808676cc4e257722a1cf47cf741268a6f56 (origin/master, origin/HEAD)
Author: templateflow-bot <nipreps@gmail.com>
Date:   Mon Aug 11 18:05:33 2025 +0000

    auto: Update S3 skeleton file and checksum [skip ci]

commit db83f2480ec8176d6ad1a993aa17603dd24564cf
Author: templateflow-bot <nipreps@gmail.com>
Date:   Fri Aug 8 18:02:08 2025 +0000

    auto: Update S3 skeleton file and checksum [skip ci]

commit 29df5d7d1ea210e8ba352816cd8a67d906e71380
Author: templateflow-bot <nipreps@gmail.com>
Date:   Fri Aug 8 17:03:38 2025 +0000

    auto: Update S3 skeleton file and checksum [skip ci]

[...]

so that a bunch of 1MB files that will never be pushed to PyPI don't need to be in templateflow's history?

[oesteban]

Sorry I missed it, thanks for the update. No opposition at all! Cheers, oe Oscar Esteban

…

On Mon, Aug 11, 2025, 20:59 Chris Markiewicz ***@***.***> wrote: *effigies* left a comment (templateflow/python-client#143) <#143 (comment)> Delaying merge pending decision about squashing skeleton updates. @oesteban <https://github.com/oesteban> I pinged you on Slack, but in case it's easier to respond here: Any opposition to squashing commit 1a41e80 (origin/master, origin/HEAD) Author: templateflow-bot ***@***.***> Date: Mon Aug 11 18:05:33 2025 +0000 auto: Update S3 skeleton file and checksum [skip ci] commit db83f24 Author: templateflow-bot ***@***.***> Date: Fri Aug 8 18:02:08 2025 +0000 auto: Update S3 skeleton file and checksum [skip ci] commit 29df5d7 Author: templateflow-bot ***@***.***> Date: Fri Aug 8 17:03:38 2025 +0000 auto: Update S3 skeleton file and checksum [skip ci] [...] so that a bunch of 1MB files that will never be pushed to PyPI don't need to be in templateflow's history? — Reply to this email directly, view it on GitHub <#143 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAESDRSHJKQ5LSZZGXW4IQT3NDRYRAVCNFSM6AAAAACDUFIVEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCNZWGM4TOMJXGA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[effigies]

Done. Merging without waiting on CI, due to the no-change diff