build(deps): bump bitarray from 3.9.2 to 3.10.0

[dependabot]

Bumps bitarray from 3.9.2 to 3.10.0.

Changelog

Sourced from bitarray's changelog.

Change log

3.10.0 (2026-07-31):

• add free threading support <free_threading.rst>__
• add bitarray/test_free_threading.py - these free-threading tests are imported when Python was compiled using --disable-gil
• add official support for decodetree methods .nodes() and .todict()
• util.huffman_code() and util.canonical_huffman() return codedicts mapping symbols to frozenbitarrays
• fix free-threading bug in binode_make_tree()
• use a private capsule to safely share the bitarray type between the _bitarray and _util extension modules
• bitarrays in prefix codes passed to .decode() or decodetree() cannot exceed 256 bits
• the following methods/functions also accept a frozendict (added in Python 3.15): .decode(), decodetree(), .encode(), util.huffman_code() and util.canonical_huffman()
• make C code more cohesive

3.9.2 (2026-07-25):

• add more critical sections in Python-facing operations
• optimize mask indexing operations for sparse and dense masks
• move tests for internal _ssqi() to devel/test_sum_indices.py
• remove all occurrences of PySlice_GetIndicesEx (deprecated since Python 3.6.1)

3.9.1 (2026-07-19):

• improving free-threading readiness, see also [#251](https://github.com/ilanschnell/bitarray/issues/251) <https://github.com/ilanschnell/bitarray/issues/251>__:
  • initialize tables at module import, not lazily
  • remove caching imported Python objects (which are already caches)
  • added 75 critical sections in Python-facing operations
  • updated Trove Classifier to Free Threading :: 2 - Beta
• clip arguments in .bytereverse() instead of raising IndexError
• remove ssize_richcompare() in favor of Py_RETURN_RICHCOMPARE macro
• add tests for frozenbitarrays created by methods when self is a frozenbitarray, e.g. slicing a frozenbitarray

3.9.0 (2026-07-10):

• add .rotate() method, rotate bitarray in-place by k positions
• expose the decodeiterator class, and add .skipbits() method as well as .index data descriptor, see [#252](https://github.com/ilanschnell/bitarray/issues/252) <https://github.com/ilanschnell/bitarray/issues/252>__
• fix random_p() silently producing all-zero bitarrays for small n

... (truncated)

Commits

• 8926f6b add release date - update docs
• 99f03fa improve frozendict support
• 3d96382 prepare tests for Python 3.15
• 78983d2 move testing private _huffman_tree() into devel/test_huffman.py
• 0ba41b7 avoid common tests to be discovered multiple times
• eaa0b0d add CommonHuffmanTests
• 776cead update readme
• ad55cd0 formatting
• a9f7b47 util.huffman_code() and util.canonical_huffman() return codedict mapping to f...
• 626759d add comment
• 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)

[dependabot]

Labels

The following labels could not be found: dependencies, python. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[github-actions]

👋 Hello! Thanks for your contribution. We will review this and get back to you as soon as possible. — th30d4y