chore(deps): bump the python-app-and-dev group with 2 updates

[dependabot]

Updates the requirements on meshtastic and pytest to permit the latest version.
Updates meshtastic to 2.7.9

Release notes

Sourced from meshtastic's releases.

Meshtastic Python 2.7.9

What's Changed

• protobufs updated
• Inject options in nanopb .options files into the protobuf files used for code generation by @​ianmcorvidae in meshtastic/python#922
• Refactor the Meshtastic TCP pub/sub example to ensure proper resource cleanup and clearer exception handling. by @​dim5x in meshtastic/python#899
• Add textchat.py and replymessage.py examples by @​SilverBull239 in meshtastic/python#913
• Fix position overwrite by lower-precision data by @​syn-ack-ai in meshtastic/python#911
• Update factory reset to use integer for config reset by @​thebentern in meshtastic/python#917
• Filter --reply based on specified channel index by @​thatSFguy in meshtastic/python#883
• Make Serial and TCP interfaces more closely respect connectNow when false by @​Travis-L-R in meshtastic/python#857
• StreamInterface: prevent socket/reader-thread leak on handshake failure by @​nightjoker7 in meshtastic/python#918
• Fix some leaks/hangs on close: unstarted StreamInterface streams & TCP reader unblock by @​ianmcorvidae in meshtastic/python#923
• Give TCPInterface reconnect logic on write errors by @​jerub in meshtastic/python#901
• Container: Add initial container for meshtastic-cli by @​oliv3r in meshtastic/python#847
• Make examples more regularized and focused, and add contribution guidelines for the examples folder by @​ianmcorvidae in meshtastic/python#928
• Added example script : meshtastic_serial_message_reader.py by @​henri in meshtastic/python#739
• Fix up the container build by @​ianmcorvidae in meshtastic/python#932

New Contributors

• @​dim5x made their first contribution in meshtastic/python#899
• @​SilverBull239 made their first contribution in meshtastic/python#913
• @​syn-ack-ai made their first contribution in meshtastic/python#911
• @​thatSFguy made their first contribution in meshtastic/python#883
• @​nightjoker7 made their first contribution in meshtastic/python#918
• @​jerub made their first contribution in meshtastic/python#901
• @​oliv3r made their first contribution in meshtastic/python#847
• @​henri made their first contribution in meshtastic/python#739

The build process for this release failed to produce the ubuntu binary. This will need to be fixed at a later time, but for now please use pip or pipx install methods, or use the new docker container.

Full Changelog: meshtastic/python@2.7.8...2.7.9

Commits

• 6eeb900 bump version to 2.7.9
• e216848 Merge pull request #932 from ianmcorvidae/fixup-container
• dd1df47 Fix up the container build to use a multi-stage build, cache better, and most...
• 8f0faf5 One more dependency update
• ab656d5 More lockfile updates now that dependabot woke up
• c575547 Merge branch 'review/pr-894'
• 0bef137 tests of new BLEError functionality
• f9a1357 Add a BLEError 'kind' field and branch on it instead of string matching
• d1f3552 Merge pull request #928 from ianmcorvidae/examples
• 81ae8b6 Make examples more regularized and focused, and add contribution guidelines f...
• Additional commits viewable in compare view

Updates pytest to 9.1.0

Release notes

Sourced from pytest's releases.

9.1.0

pytest 9.1.0 (2026-06-13)

Removals and backward incompatible breaking changes

• #14533: When using --doctest-modules, autouse fixtures with module, package or session scope that are defined inline in Python test modules (not plugins or conftests) will now possibly execute twice.

  If this is undesirable, move the fixture definition to a conftest.py file if possible.

  Technical explanation for those interested: When using --doctest-modules, pytest possibly collects Python modules twice, once as pytest.Module and once as a DoctestModule (depending on the configuration). Due to improvements in pytest's fixture implementation, if e.g. the DoctestModule collects a fixture, it is now visible to it only, and not to the Module. This means that both need to register the fixtures independently.

Deprecations (removal in next major release)

• #10819: Added a deprecation warning for class-scoped fixtures defined as instance methods (without @classmethod). Such fixtures set attributes on a different instance than the test methods use, leading to unexpected behavior. Use @classmethod decorator instead -- by yastcher.

  See 10819 and 14011.

• #12882: Calling request.getfixturevalue() <pytest.FixtureRequest.getfixturevalue> during teardown to request a fixture that was not already requested is now deprecated and will become an error in pytest 10.

  See dynamic-fixture-request-during-teardown for details.

• #13409: Using non-~collections.abc.Collection iterables (such as generators, iterators, or custom iterable objects) for the argvalues parameter in @pytest.mark.parametrize <pytest.mark.parametrize ref> and metafunc.parametrize <pytest.Metafunc.parametrize> is now deprecated.

  These iterables get exhausted after the first iteration, leading to tests getting unexpectedly skipped in cases such as running pytest.main() multiple times, using class-level parametrize decorators, or collecting tests multiple times.

  See parametrize-iterators for details and suggestions.

• #13946: The private config.inicfg attribute is now deprecated. Use config.getini() <pytest.Config.getini> to access configuration values instead.

  See config-inicfg for more details.

• #14004: Passing baseid to ~pytest.FixtureDef or nodeid strings to fixture registration APIs is now deprecated. These are internal pytest APIs that are used by some plugins.

  Use the node parameter instead for fixture scoping. This enables more robust node-based matching instead of string prefix matching. If you've used nodeid=None, pass node=session instead.

  This will be removed in pytest 10.

• #14335: The method of configuring hooks using markers, deprecated since pytest 7.2, is now scheduled to be removed in pytest 10. See hook-markers for more details.

• #14434: The --pastebin option is now deprecated.

... (truncated)

Commits

• b2522cf Prepare release version 9.1.0
• 368d2fc [refactor] Tighten SetComparisonFunction to Iterator[str] (#14587)
• ff77cd8 [refactor] Make base assertion comparisons return an iterator instead of a li...
• 0d8491a build(deps): Bump actions/stale from 10.2.0 to 10.3.0
• 4a809d9 Merge pull request #14568 from pytest-dev/register-fixture
• 5dfa385 Fix recursion traceback test to cover all styles (#14582)
• f52ff0c Add pytest.register_fixture
• a8ac094 Merge pull request #14567 from pytest-dev/more-visibility-deprecate
• e5620cd [pre-commit.ci] pre-commit autoupdate (#14577)
• 2ce9c6d Merge pull request #14540 from minbang930/fix-14533-doctest-module-fixtures
• 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