build(deps): bump the all group with 2 updates

[dependabot]

Bumps the all group with 2 updates: tree-sitter and pytest-gremlins.

Updates tree-sitter from 0.25.2 to 0.26.0

Release notes

Sourced from tree-sitter's releases.

v0.26.0

Breaking changes are marked with !.

Additions:

• Point.edit()
• Point.__repr__()
• QueryCursor.set_containing_byte_range()
• QueryCursor.set_containing_point_range()
• Range.edit()
• tree_sitter.__version__

Removals:

• Language.version: use Language.abi_version !
• Language.query(source): use Query(language, source) !
• Parser.timeout_micros: use the progress_callback in parse() !
• QueryCursor.timeout_micros: use the progress_callback in matches() or captures() !

Changes:

• Point is a tuple subclass rather than a namedtuple object

Commits

• a9e753e ci(pypi): skip riscv64 tests properly
• eeababc chore: release 0.26.0
• dac834e fix(node): fix reference leak
• bdddb61 build: bump tree-sitter-rust from 0.24.1 to 0.24.2
• baa5fd8 ci: bump the actions group across 1 directory with 2 updates
• c680e3b build: bump tree_sitter/core from cd5b087 to 7f53486
• 2d3fb3a ci: bump actions/upload-pages-artifact from 4 to 5 in the actions group
• bae0829 build: bump tree-sitter-rust from 0.24.0 to 0.24.1
• d99f796 build: bump tree_sitter/core from 6f2e8a6 to cd5b087
• a9282df build: bump tree_sitter/core from cd4b6e2 to 6f2e8a6
• Additional commits viewable in compare view

Updates pytest-gremlins from 1.9.0 to 1.11.3

Release notes

Sourced from pytest-gremlins's releases.

v1.11.3 (2026-10-08)

More of your code gets real verdicts. Two kinds of target got verdicts that no test backed. Gremlins in modules that pytest rewrites assertions in (conftest.py, files matching python_files, helpers passed to pytest.register_assert_rewrite) were never activated, so they were reported SURVIVED even when a test caught them. Code that looked up its own source with inspect.getsource failed under every gremlin, so the gremlins its tests ran against were reported ZAPPED (or ERROR, when the lookup ran at import time). Both are fixed. Your score may move either way after upgrading.

Upgrade notes

• Your score may rise if your targets include files pytest rewrites assertions in. Those are conftest.py files, modules matching a custom python_files pattern (for example *_impl.py), and packages passed to pytest.register_assert_rewrite. Their gremlins are now zapped when a test catches them. pytest's assertion rewriting still applies to them, so a test that checks an assert message sees the same message it does without pytest-gremlins. Files named test_*.py, *_test.py or conftest.py inside a target directory are still skipped; they are mutated only when named explicitly in --gremlin-targets. (#603, #616)
• Your score may move if your code or your tests read the source of your code. Under a gremlin, inspect.getsource failed or returned the wrong lines for instrumented code, and linecache and tracebacks showed no source for it. A test that read source failed for that reason alone, so every gremlin it ran against was counted as zapped; those kills no longer count, and the score drops. A lookup at import time (for example in a decorator) made every gremlin in the file ERROR; those gremlins now get real verdicts. (#563, #610)
• The cache is rebuilt once. The cache version changed so that the wrong verdicts above are not replayed. The first run after upgrading re-runs every gremlin. (#610, #616)

Fix

• Gremlins in files that pytest's assertion-rewrite hook loads were always reported SURVIVED. See the upgrade notes above. Plugins that pytest loads before reading conftest.py files (through -p in addopts, entry points or PYTEST_PLUGINS) are still not instrumented, as before. (#603, #616)
• Instrumented code reported a module name instead of its file, and shifted line numbers. Tracebacks, inspect and linecache now see the real file path and the original line numbers. On Python 3.11, a very deeply nested file (a few hundred elif branches) keeps the old behavior. (#563, #610)

What's Changed

• fix: compile instrumented modules under their real filename with original line numbers by @​mikelane in mikelane/pytest-gremlins#610
• fix(instrumentation): instrument assertion-rewrite hook targets by @​mikelane in mikelane/pytest-gremlins#616
• docs: add v1.11.3 changelog entry by @​mikelane in mikelane/pytest-gremlins#619

Full Changelog: mikelane/pytest-gremlins@v1.11.2...v1.11.3

v1.11.2 (2026-10-06)

... (truncated)

Changelog

Sourced from pytest-gremlins's changelog.

v1.11.3 (2026-10-08)

More of your code gets real verdicts. Two kinds of target got verdicts that no test backed. Gremlins in modules that pytest rewrites assertions in (conftest.py, files matching python_files, helpers passed to pytest.register_assert_rewrite) were never activated, so they were reported SURVIVED even when a test caught them. Code that looked up its own source with inspect.getsource failed under every gremlin, so the gremlins its tests ran against were reported ZAPPED (or ERROR, when the lookup ran at import time). Both are fixed. Your score may move either way after upgrading.

Upgrade notes

• Your score may rise if your targets include files pytest rewrites assertions in. Those are conftest.py files, modules matching a custom python_files pattern (for example *_impl.py), and packages passed to pytest.register_assert_rewrite. Their gremlins are now zapped when a test catches them. pytest's assertion rewriting still applies to them, so a test that checks an assert message sees the same message it does without pytest-gremlins. Files named test_*.py, *_test.py or conftest.py inside a target directory are still skipped; they are mutated only when named explicitly in --gremlin-targets. (#603, #616)
• Your score may move if your code or your tests read the source of your code. Under a gremlin, inspect.getsource failed or returned the wrong lines for instrumented code, and linecache and tracebacks showed no source for it. A test that read source failed for that reason alone, so every gremlin it ran against was counted as zapped; those kills no longer count, and the score drops. A lookup at import time (for example in a decorator) made every gremlin in the file ERROR; those gremlins now get real verdicts. (#563, #610)
• The cache is rebuilt once. The cache version changed so that the wrong verdicts above are not replayed. The first run after upgrading re-runs every gremlin. (#610, #616)

Fix

• Gremlins in files that pytest's assertion-rewrite hook loads were always reported SURVIVED. See the upgrade notes above. Plugins that pytest loads before reading conftest.py files (through -p in addopts, entry points or PYTEST_PLUGINS) are still not instrumented, as before. (#603, #616)
• Instrumented code reported a module name instead of its file, and shifted line numbers. Tracebacks, inspect and linecache now see the real file path and the original line numbers. On Python 3.11, a very deeply nested file (a few hundred elif branches) keeps the old behavior. (#563, #610)

v1.11.2 (2026-10-06)

Gremlins are no longer reported as survivors because of how your project is laid out. pytest-gremlins guessed each target file's module name from its path. When the guess didn't match the name your tests import, the mutated code never loaded, and every gremlin in that file was reported SURVIVED, even the ones your tests catch. The mutation run now asks Python's own import system which file an import loads, so no name is guessed.

Upgrade notes

• Your score may rise. Gremlins your tests catch are now zapped in these cases, where they

... (truncated)

Commits

• ee3ff16 bump: version 1.11.2 → 1.11.3
• 7630b98 docs: add v1.11.3 changelog entry (#619)
• 2e32bbb fix(instrumentation): instrument assertion-rewrite hook targets (#616)
• e0b814d fix: compile instrumented modules under their real filename with original lin...
• c79a2ff bump: version 1.11.1 → 1.11.2
• 135261b docs: add v1.11.2 changelog entry (#609)
• 83652ac fix(instrumentation): resolve instrumented modules by import origin, not gues...
• 0f93e38 bump: version 1.11.0 → 1.11.1
• da9d6b8 docs: add v1.11.1 changelog entry (#601)
• decc108 fix(instrumentation): import package init gremlins under the package name...
• 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

[tob-scott-a]

An upstream issue prevents 0.26.0 from being adopted.

[dependabot]

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.

To ignore these dependencies, configure ignore rules in dependabot.yml