Skip to content

v0.6.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 12 Sep 12:12
· 13 commits to main since this release
v0.6.0
337eb48

FlightLens 0.6.0

FlightLens expands backup comparison with explicit feature, serial-port and mode
assignments, receiver ranges and failsafes, and VTX tables. Filters and source
lines make differences traceable; missing or invalidated declarations remain
unknown. Preserved CLI collection text is also available for comparison.

Four parameter mappings—motor poles and three battery cell-voltage thresholds—
now support certified cross-version comparison between official Betaflight
4.5.0–4.5.5 and 2025.12.1–2025.12.5. The firmware-family gate now works with actual
parser output. Other cross-version settings remain uncertified.

The new feedback button prepares a report for review, opens a prefilled GitHub
issue in the browser, and optionally copies a redacted configuration for the user
to submit. FlightLens does not send it itself. Preview consent and attachment-size
checks protect against submitting stale previews or oversized issue text.

GPS rescue bounds for Betaflight 4.4 and LED STATUS lookup handling are corrected.

Upgrade and compatibility

No breaking changes are known. No migration or other user action is required.
Saved workspace paths and settings retain their existing format; portable
.flightlens sessions are not yet supported. Source backups remain read-only,
and inspection and comparison remain offline. Submitting feedback uses the
user's browser and GitHub account.

Bundled schemas continue to cover Betaflight 4.2, 4.3, 4.4, 4.5 and 2025.12.
Receiver-range, receiver-failsafe and VTX-table semantic comparisons require
matching verified official versions in 4.5.0–4.5.5 or 2025.12.1–2025.12.5.
Vendor and cross-version collection comparisons remain uncertified. Existing
export formats and explicit-input validation requirements are preserved; these
new semantic collection comparisons do not add collection export.

Known limitations

  • VTX activation and adjustment-range semantic comparison remain outstanding.
    The initial official 4.5 activation scope is documented; 2025.12 needs verified
    build-capacity evidence. Equal VTX declarations do not establish equal RF output.
  • Three-backup comparison, saved comparison selections and broader cross-version
    equivalence remain outstanding.
  • Twelve 2025.12 settings still have unresolved bounds. Hardware-specific schema
    entries, arrays and full unsigned 32-bit values need additional coverage.
  • Packaged Windows/macOS native integration and feedback hand-off still need
    manual verification. Installers remain unsigned; macOS notarization is absent.

Release validation includes the full local test suite, parser corpus checks and
README screenshot checks. GitHub workflows build and publish both desktop installers.

Assets 5
Loading