Skip to content

1.4: Keep unknown MAVLink endpoints when downgrading from 1.5 - #4169

Draft
joaoantoniocardoso wants to merge 6 commits into
bluerobotics:1.4-devfrom
joaoantoniocardoso:fix/1.4-skip-unknown-mavlink-endpoints
Draft

1.4: Keep unknown MAVLink endpoints when downgrading from 1.5#4169
joaoantoniocardoso wants to merge 6 commits into
bluerobotics:1.4-devfrom
joaoantoniocardoso:fix/1.4-skip-unknown-mavlink-endpoints

Conversation

@joaoantoniocardoso

@joaoantoniocardoso joaoantoniocardoso commented Aug 14, 2026

Copy link
Copy Markdown
Member

Summary

  • 1.5 persists endpoint types that 1.4 does not know (zenohraw in particular), so pydantic rejected them and ardupilot_manager crashed on downgrade.
  • Unknown connection types are now first-class endpoint records: they load and save, show as disabled in the API and UI, and are omitted from the router command line.
  • Creating or updating an unknown type returns 422. Deleting one is allowed even if 1.5 marked it protected.

Fixes #4162

Test plan

  • On 1.5, persist a 1.5-only endpoint (e.g. zenohraw), then boot this 1.4 build
  • ardupilot_manager starts; settings.json still contains the unknown endpoint
  • GET /endpoints lists it as disabled; the UI shows the type, with enable/edit off and delete available
  • Deleting the unknown endpoint succeeds
  • POST/PUT of an unknown type returns 422
  • Known endpoints still create, enable, disable, edit, and delete as before

…nt types

Unknown connection types construct as records. They are omitted from
routing and reported disabled by as_api_dict.
@joaoantoniocardoso
joaoantoniocardoso force-pushed the fix/1.4-skip-unknown-mavlink-endpoints branch from 0b2ecc6 to 9355fcc Compare August 14, 2026 23:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant