chore(deps): Bump the datalad group in /services/datalad with 5 updates

[dependabot]

Bumps the datalad group in /services/datalad with 5 updates:

Package	From	To
bidsschematools	1.1.6	1.2.0
boto3	1.42.39	1.42.44
taskiq-redis	1.2.1	1.2.2
coverage	7.13.2	7.13.4
ruff	0.14.14	0.15.0

Updates bidsschematools from 1.1.6 to 1.2.0

Release notes

Sourced from bidsschematools's releases.

v1.2.0

Changes

• Update Pipfile.lock #144 (franklin-feingold)
• [MRG] clarify encoding of README, CHANGES, TSV, and JSON files #140 (sappelhoff)
• Update site_name and release protocol #137 (franklin-feingold)
• BF: Example for IntendedFor was missing session indicator in the filename #129 (yarikoptic)
• Add "part" keyword for mag/phase BOLD images (based on BEP001). #128 (tsalo)
• Update to Release_Protocol.md #126 (franklin-feingold)
• Update tag naming convention #123 (chrisfilo)
• [MRG] Merge bep006 and bep010 #108 (sappelhoff)
• Adding formal decision-making rules #104 (chrisfilo)
• [MRG] number of small corrections to the specification #98 (robertoostenveld)

Changelog

Sourced from bidsschematools's changelog.

Release Procedure

When it is time to release, use a pull request to put the repository into a releasable state, allowing testing and edits prior to merging to master. The following procedure ensures a predictable release.

The protocol assumes that you have a fork of the bids-standard/bids-specification repository and have cloned your fork locally to a directory called bids-specification.

0. Generate the changelog

tools/make_changelog.py

This script will prompt you for a GitHub token with the "Read access to metadata and pull requests" permission.

Running the script once will populate a section with the titles of the pull requests merged since the most recent tag. Review those titles, and update them on GitHub for style and clarity.

Note that the audience for the changelog is the people reading the specification. Many pull requests, although valuable, are not relevant to that audience and should be tagged with the exclude-from-changelog label.

The script will overwrite any existing changelog since the most recent tag, so it can be run repeatedly until it looks right.

1. Fetch the latest version of the master branch of the BIDS-specification

You should have a remote, which we will call upstream, for the bids-standard/bids-specification repository:

git remote get-url upstream
git@github.com:bids-standard/bids-specification.git

If you do not, add it with:

cd bids-specification
git remote add upstream git@github.com:bids-standard/bids-specification.git

Fetch the current repository state and create a new rel/<version> branch based on upstream/master. For example, if releasing version 1.2.0:

... (truncated)

Commits

• dbdf32e Merge pull request #161 from chrisfilo/rel/1.2.0
• 07d466e REL: v1.2.0
• efd2a97 [DOC] Auto-generate changelog entry for PR #108
• a308032 Merge pull request #108 from sappelhoff/merge_bep006
• 15668dc add CPernet to Codeowners
• e450e13 [DOC] Auto-generate changelog entry for PR #144
• 1aae509 Merge pull request #144 from franklin-feingold/pipfile
• 637740c adjust heading in coords appendix to be more specific
• 23ea300 add link to fieldtrip wikifor ACPC, linter fixes
• d64d019 fix ACPC, overhaul coordinates appendix, clarify iEEG coordsystem field
• Additional commits viewable in compare view

Updates boto3 from 1.42.39 to 1.42.44

Commits

• 451ee66 Merge branch 'release-1.42.44'
• eb28403 Bumping version to 1.42.44
• 0b2df35 Add changelog entries from botocore
• 630ab63 Merge branch 'release-1.42.43'
• 1bfdbb3 Merge branch 'release-1.42.43' into develop
• 53542d4 Bumping version to 1.42.43
• c4bf448 Add changelog entries from botocore
• 79499f4 Merge branch 'release-1.42.42'
• 857e330 Merge branch 'release-1.42.42' into develop
• f649133 Bumping version to 1.42.42
• Additional commits viewable in compare view

Updates taskiq-redis from 1.2.1 to 1.2.2

Release notes

Sourced from taskiq-redis's releases.

1.2.2

What's Changed

• fix: add a timeout to RedisSteamBroker xautoclaim lock to prevent infinite locking by @​FlorianLB in taskiq-python/taskiq-redis#107

Full Changelog: taskiq-python/taskiq-redis@1.2.1...1.2.2

Commits

• 374c789 Merge pull request #107 from FlorianLB/fix-autoclaim-infinite-locking
• e997423 fix: add a timeout to RedisSteamBroker xautoclaim lock to prevent infinite lo...
• See full diff in compare view

Updates coverage from 7.13.2 to 7.13.4

Changelog

Sourced from coverage's changelog.

Version 7.13.4 — 2026-02-09

• Fix: the third-party code fix in 7.13.3 required examining the parent directories where coverage was run. In the unusual situation that one of the parent directories is unreadable, a PermissionError would occur, as described in issue 2129_. This is now fixed.

• Fix: in test suites that change sys.path, coverage.py could fail with "RuntimeError: Set changed size during iteration" as described and fixed in pull 2130_. Thanks, Noah Fatsi.

• We now publish ppc64le wheels, thanks to Pankhudi Jain <pull 2121_>_.

.. _pull 2121: coveragepy/coveragepy#2121 .. _issue 2129: coveragepy/coveragepy#2129 .. _pull 2130: coveragepy/coveragepy#2130

.. _changes_7-13-3:

Version 7.13.3 — 2026-02-03

• Fix: in some situations, third-party code was measured when it shouldn't have been, slowing down test execution. This happened with layered virtual environments such as uv sometimes makes. The problem is fixed, closing issue 2082_. Now any directory on sys.path that is inside a virtualenv is considered third-party code.

.. _issue 2082: coveragepy/coveragepy#2082

.. _changes_7-13-2:

Commits

• 4f78d57 build: no need to publish status.json
• f8616ff docs: sample HTML for 7.13.4
• fcf8c68 docs: prep for 7.13.4
• 189ecfd docs: thanks Pankhudi Jain for ppc64le wheels #2121
• 58aade0 build: add support for ppc64le architecture (#2121)
• 8ea42c8 chore: bump actions/attest-build-provenance (#2131)
• c09595f docs: Janine put a lot of effort into debugging issue #2128
• 8ee1760 docs: Greg wrote a great issue: #2129
• 76ba043 docs: thanks, Noah Fatsi
• 371fcc5 fix: set fixed paths_list in TreeMatcher init (#2130)
• Additional commits viewable in compare view

Updates ruff from 0.14.14 to 0.15.0

Release notes

Sourced from ruff's releases.

0.15.0

Release Notes

Released on 2026-02-03.

Check out the blog post for a migration guide and overview of the changes!

Breaking changes

• Ruff now formats your code according to the 2026 style guide. See the formatter section below or in the blog post for a detailed list of changes.

• The linter now supports block suppression comments. For example, to suppress N803 for all parameters in this function:

  # ruff: disable[N803]
  def foo(
      legacyArg1,
      legacyArg2,
      legacyArg3,
      legacyArg4,
  ): ...
  # ruff: enable[N803]

  See the documentation for more details.

• The ruff:alpine Docker image is now based on Alpine 3.23 (up from 3.21).

• The ruff:debian and ruff:debian-slim Docker images are now based on Debian 13 "Trixie" instead of Debian 12 "Bookworm."

• Binaries for the ppc64 (64-bit big-endian PowerPC) architecture are no longer included in our releases. It should still be possible to build Ruff manually for this platform, if needed.

• Ruff now resolves all extended configuration files before falling back on a default Python version.

Stabilization

The following rules have been stabilized and are no longer in preview:

• blocking-http-call-httpx-in-async-function (ASYNC212)
• blocking-path-method-in-async-function (ASYNC240)
• blocking-input-in-async-function (ASYNC250)
• map-without-explicit-strict (B912)
• if-exp-instead-of-or-operator (FURB110)
• single-item-membership-test (FURB171)
• missing-maxsplit-arg (PLC0207)
• unnecessary-lambda (PLW0108)
• unnecessary-empty-iterable-within-deque-call (RUF037)
• in-empty-collection (RUF060)
• legacy-form-pytest-raises (RUF061)
• non-octal-permissions (RUF064)

... (truncated)

Changelog

Sourced from ruff's changelog.

0.15.0

Released on 2026-02-03.

Check out the blog post for a migration guide and overview of the changes!

Breaking changes

• Ruff now formats your code according to the 2026 style guide. See the formatter section below or in the blog post for a detailed list of changes.

• The linter now supports block suppression comments. For example, to suppress N803 for all parameters in this function:

  # ruff: disable[N803]
  def foo(
      legacyArg1,
      legacyArg2,
      legacyArg3,
      legacyArg4,
  ): ...
  # ruff: enable[N803]

  See the documentation for more details.

• The ruff:alpine Docker image is now based on Alpine 3.23 (up from 3.21).

• The ruff:debian and ruff:debian-slim Docker images are now based on Debian 13 "Trixie" instead of Debian 12 "Bookworm."

• Binaries for the ppc64 (64-bit big-endian PowerPC) architecture are no longer included in our releases. It should still be possible to build Ruff manually for this platform, if needed.

• Ruff now resolves all extended configuration files before falling back on a default Python version.

Stabilization

The following rules have been stabilized and are no longer in preview:

• blocking-http-call-httpx-in-async-function (ASYNC212)
• blocking-path-method-in-async-function (ASYNC240)
• blocking-input-in-async-function (ASYNC250)
• map-without-explicit-strict (B912)
• if-exp-instead-of-or-operator (FURB110)
• single-item-membership-test (FURB171)

... (truncated)

Commits

• ce5f7b6 Bump 0.15.0 (#23055)
• b4e40f5 [ty] Fix __contains__ to respect descriptors (#23056)
• 848cb72 [ty] Fix narrowing of nonlocal variables with conditional assignments (#22966)
• da7f33a [ty] Add a diagnostic for Final without assignment (#23001)
• e65f9a6 Document markdown formatting feature (#22990)
• c0c1b98 Format markdown code blocks with line-by-line regex parse (#22996)
• 9f8f3e1 Allow positional-only params with defaults in method overrides (#23037)
• ef83810 [ty] ecosystem-analyzer: Support bare git repositories (#23054)
• 54dfee4 Customize where the fix_title sub-diagnostic appears (#23044)
• b534607 2026 Ruff Formatter Style (#22735)
• 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions