Run any Skill in Manus with one click

meshsa-schema-version-bump

Stars1

Forks0

UpdatedJune 20, 2026 at 23:00

Use when: changing meshsa Envelope fields, schema_version, MIN_COMPATIBLE_SCHEMA, backward compatibility, wire compatibility, migrations, deprecations, or serialized payload shape.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

ianshank

ianshank/GCP-Drone-Comms-Unit

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	meshsa-schema-version-bump
description	Use when: changing meshsa Envelope fields, schema_version, MIN_COMPATIBLE_SCHEMA, backward compatibility, wire compatibility, migrations, deprecations, or serialized payload shape.
argument-hint	Schema change, compatibility impact, migration path, and affected codecs

Bump MeshSA Schema Version

When to Use

Add, rename, remove, or reinterpret fields on Envelope or wire payloads.
Change compatibility rules in meshsa.version.
Introduce a migration or deprecation path for old nodes.

Procedure

Classify the change:
- Optional additive field with default: usually no schema bump.
- Rename, removal, or semantic change: bump SCHEMA_VERSION.
- Dropping old nodes: raise MIN_COMPATIBLE_SCHEMA and document why.
Update packages/meshsa/src/meshsa/version.py.
Update every codec decode path that checks compatibility.
Add tests for old, current, and incompatible versions.
Add or update serialized snapshot/roundtrip tests when the wire shape changes.
Document the migration path in CHANGELOG.md, docs/ARCHITECTURE.md, and any user-facing config examples.
Run the full package suite and mypy before removing compatibility warnings.

References

packages/meshsa/src/meshsa/version.py
packages/meshsa/src/meshsa/models.py
packages/meshsa/src/meshsa/codec.py
packages/meshsa/src/meshsa/compact.py
packages/meshsa/src/meshsa/cot.py
packages/meshsa/tests/test_version_models.py

More from this repository

same repository

jetson-perception

ianshank/GCP-Drone-Comms-Unit

Use when: working in packages/jetson_yolo_gcs — adding a detector backend (YOLO/Hailo/ONNX/TensorRT), a tracker backend (Norfair/SORT), GStreamer camera/egress pipeline, the MAVLink LANDING_TARGET bridge, precision-landing safety, or the perception pipeline failure policy.

2026-07-161

pre-pr-validator

ianshank/GCP-Drone-Comms-Unit

Use when: running pre-PR checks, performing regression testing, validating ruff linting/formatting, verifying mypy type safety, and checking test coverage before pushing.

2026-07-161

meshsa-inference

ianshank/GCP-Drone-Comms-Unit

Use when: working on the optional NVIDIA Nemotron inference bridge — meshsa.inference, NemotronClient/InferenceService/NemotronConfig, MESHSA_INFERENCE_* env vars, aiohttp session reuse, [AI Insight] feedback-loop filter, or the aioresponses test mocks.

2026-07-081

meshsa-observability

ianshank/GCP-Drone-Comms-Unit

Use when: adding or changing metrics/health export — RouterMetrics, render_prometheus, per-transport counters, the /metrics or /healthz route, HealthConfig fields, or a Grafana golden-signal dashboard.

2026-07-081

meshsa-commanding-safety

ianshank/GCP-Drone-Comms-Unit

Use when: touching the supervised two-way command path (Initiative C) — meshsa.command.*, flightctl/run_commander.py, arm/disarm/RTL/set_mode, COMMAND_INT/ACK, force-disarm, operator confirmation, command audit log, or arm preconditions.

2026-06-301

spec-driven-change

ianshank/GCP-Drone-Comms-Unit

Use when: starting a roadmap/initiative feature, new milestone work, a transport/codec/backend that adds behavior, or any change big enough to need a design. Author or update a spec under docs/specs first; code cites the spec by section.

2026-06-301

name	meshsa-schema-version-bump
description	Use when: changing meshsa Envelope fields, schema_version, MIN_COMPATIBLE_SCHEMA, backward compatibility, wire compatibility, migrations, deprecations, or serialized payload shape.
argument-hint	Schema change, compatibility impact, migration path, and affected codecs

Bump MeshSA Schema Version

When to Use

Add, rename, remove, or reinterpret fields on Envelope or wire payloads.
Change compatibility rules in meshsa.version.
Introduce a migration or deprecation path for old nodes.

Procedure

Classify the change:
- Optional additive field with default: usually no schema bump.
- Rename, removal, or semantic change: bump SCHEMA_VERSION.
- Dropping old nodes: raise MIN_COMPATIBLE_SCHEMA and document why.
Update packages/meshsa/src/meshsa/version.py.
Update every codec decode path that checks compatibility.
Add tests for old, current, and incompatible versions.
Add or update serialized snapshot/roundtrip tests when the wire shape changes.
Document the migration path in CHANGELOG.md, docs/ARCHITECTURE.md, and any user-facing config examples.
Run the full package suite and mypy before removing compatibility warnings.

References

packages/meshsa/src/meshsa/version.py
packages/meshsa/src/meshsa/models.py
packages/meshsa/src/meshsa/codec.py
packages/meshsa/src/meshsa/compact.py
packages/meshsa/src/meshsa/cot.py
packages/meshsa/tests/test_version_models.py