…obufs master (meshtastic#112)
* build(deps): take meshtastic from python master for the 2.8 protos
No meshtastic release carries the 2.8 protos: 2.7.11 on PyPI predates
xeddsa_signed, packet_signature_policy and the mesh_beacon module config,
so the tools can't read a packet's signature flag or a node's signing
policy, and config_diff can't see a policy change. python master
(0a183576) carries the v2.8.1 protos.
The pin is a [tool.uv.sources] override, so it reaches the lock and every
uv sync or uv run of a checkout while the published requirement stays
meshtastic>=2.7.8. It goes once a release carries the protos.
Signed-off-by: James Rich <james.a.rich@gmail.com>
* build(deps): take meshtastic at protobufs master 4c80682
python master stops at protobufs v2.8.1, before ClientNotification.type and
DeviceMetadata.ble_address. meshtastic/python#1005 regenerates the protos
from protobufs master 4c80682; take its commit until a release carries them.
Signed-off-by: James Rich <james.a.rich@gmail.com>
* Revert "build(deps): take meshtastic at protobufs master 4c80682"
This reverts commit 2f8b4b9.
Signed-off-by: James Rich <james.a.rich@gmail.com>
* Revert "build(deps): take meshtastic from python master for the 2.8 protos"
This reverts commit 492d6f8.
Signed-off-by: James Rich <james.a.rich@gmail.com>
* feat(protos): serve meshtastic.protobuf from protos generated at protobufs master
The meshtastic library has had no release since 2.7.11 in July, so no
release carries any 2.8 protos and the tools can't read xeddsa_signed,
packet_signature_policy, the mesh_beacon config or ClientNotification.type.
meshtastic_mcp.protos puts a finder ahead of the library's modules, so every
meshtastic.protobuf.*_pb2 import resolves to protos/generated/, built from
meshtastic/protobufs 4c80682 by scripts/regen_protos.sh with the library's
own regen steps. It installs when meshtastic_mcp is imported, and stands
aside with a warning if the library's protos were loaded first. The
meshtastic requirement and lock are unchanged.
Signed-off-by: James Rich <james.a.rich@gmail.com>
---------
Signed-off-by: James Rich <james.a.rich@gmail.com>
Brings the protos to protobufs master
4c80682ahead of the next tag, so a consumer can use what landed after v2.8.2:ClientNotification.type,DeviceMetadata.ble_addressandbootloader_version, and the field metadata tags.meshtastic-mcptakes it until a release carries them.Regenerated with
bin/regen-protobufs.sh's steps (nanopb 0.4.8 protoc, mypy-protobuf 3.6.0 from the lock).pytest -m unitpasses (386 passed, 2 skipped), and mypy reports the same 14 errors as master, all outside the generated code.Summary by CodeRabbit
New Features
Documentation