Skip to content

feat: Release version 1.0.0 - Production-ready stable release#38

Merged
nerdCopter merged 5 commits into
masterfrom
20251229_release
Dec 30, 2025
Merged

feat: Release version 1.0.0 - Production-ready stable release#38
nerdCopter merged 5 commits into
masterfrom
20251229_release

Conversation

@nerdCopter
Copy link
Copy Markdown
Owner

@nerdCopter nerdCopter commented Dec 29, 2025

Overview

Release bbl_parser v1.0.0 — the first stable production release.

Changes

  • Version Bump: 0.9.0 → 1.0.0
  • Changelog: Added comprehensive CHANGELOG.md documenting features, roadmap, and acknowledgments
  • crates.io Ready: Updated Cargo.toml description to reflect supported firmware (Betaflight/EmuFlight only)
  • Documentation: Updated README.md and OVERVIEW.md to remove INAV references
  • Build Quality: All mandatory checks verified ✅
    • cargo fmt --all -- --check
    • cargo clippy --all-targets --all-features -- -D warnings
    • cargo test --verbose (62 unit tests pass)
    • cargo build --release (no errors/warnings)

Release Readiness

This release includes:

  • ✅ Complete binary format parser with all frame types (I, P, S, H, G, E)
  • ✅ Library API with 15+ public functions for parsing/export/conversion
  • ✅ CSV/GPX/Event export with production-grade quality
  • ✅ Multi-platform CI/CD with automated testing
  • ✅ Comprehensive documentation (README, OVERVIEW, CRATE_USAGE, 8 examples)
  • ✅ Full test coverage (62 unit tests, 8 integration tests, 3 doc tests)
  • ✅ Zero clippy warnings, proper error handling, type-safe design

Next Steps (Post-Merge)

  1. Configure GitHub secret CARGO_REGISTRY_TOKEN in repository settings
  2. Create GitHub release tag v1.0.0
  3. Release workflow automatically publishes to crates.io

Acceptance Criteria

  • Code review approved
  • Manual merge to master
  • GitHub secret configured
  • Release tag created and published

Summary by CodeRabbit

  • Chores

    • Released version 1.0.0.
  • Documentation

    • Added a comprehensive changelog documenting features, technical highlights, performance notes, compatibility, roadmap, limitations, and acknowledgments.
  • Updates

    • Broadened firmware validation targets (wider compatibility across older releases).
  • Maintenance

    • Adjusted ignore rules to ensure the changelog is tracked in the repository.

✏️ Tip: You can customize this high-level summary in your review settings.

- Bump version from 0.9.0 to 1.0.0
- Add comprehensive CHANGELOG.md documenting features and roadmap
- Remove INAV from crates.io description (Betaflight/EmuFlight only)
- Update README.md and OVERVIEW.md to reflect supported firmware
- Whitelist CHANGELOG.md in .gitignore for version control
- Verified all mandatory checks: format, clippy, tests, build
- Ready for crates.io publishing with CARGO_REGISTRY_TOKEN secret
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Dec 29, 2025

📝 Walkthrough

Walkthrough

Bumps package version to 1.0.0, adds a comprehensive CHANGELOG.md for the 2025-12-29 release, updates GOALS.md firmware validation details, and whitelists CHANGELOG.md in the root .gitignore.

Changes

Cohort / File(s) Summary
Version Release Configuration
Cargo.toml, .gitignore
Cargo.toml: package version changed from "0.9.0" to "1.0.0". .gitignore: added root whitelist entry +!CHANGELOG.md.
Release Documentation
CHANGELOG.md
Added new CHANGELOG.md (Keep a Changelog format) documenting v1.0.0 (2025-12-29) features, technical highlights, performance notes, compatibility, roadmap, limitations, acknowledgments, and version history.
Project Goals
GOALS.md
Updated firmware validation line to include Betaflight 4.0+, EmuFlight, INAV across ~6+ years of releases.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately reflects the main change: a version bump to 1.0.0 for a production release, which aligns with the Cargo.toml version change and new CHANGELOG.md creation.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch 20251229_release

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3668d18 and 3b3614c.

📒 Files selected for processing (2)
  • CHANGELOG.md
  • GOALS.md
✅ Files skipped from review due to trivial changes (1)
  • GOALS.md
🧰 Additional context used
🧠 Learnings (4)
📓 Common learnings
Learnt from: nerdCopter
Repo: nerdCopter/bbl_parser PR: 2
File: README.md:0-0
Timestamp: 2025-08-29T19:55:43.912Z
Learning: nerdCopter updated the bbl_parser project license from GPL-3.0-or-later to AGPL-3.0-or-later across all repository files (Cargo.toml, LICENSE, README.md) for consistency with the dual-licensing approach that includes a commercial license option.
Learnt from: nerdCopter
Repo: nerdCopter/bbl_parser PR: 0
File: :0-0
Timestamp: 2025-12-08T21:15:02.434Z
Learning: Repo nerdCopter/bbl_parser: For outside-diff review notes, prefer a compact, single-block comment with flat bullets (file:line → note), no nested <details> or admonitions; overflow should be linked via gist. Maintainer: nerdCopter.
Learnt from: nerdCopter
Repo: nerdCopter/bbl_parser PR: 0
File: :0-0
Timestamp: 2025-12-08T21:15:02.434Z
Learning: For bbl_parser reviews: nerdCopter prefers compact, single-block “outside diff” comments without nested <details> or admonitions; use flat bullets with file:line references and link a gist for overflow.
Learnt from: nerdCopter
Repo: nerdCopter/bbl_parser PR: 2
File: LICENSE_COMMERCIAL:1-4
Timestamp: 2025-08-29T19:52:05.099Z
Learning: nerdCopter prefers to avoid publishing personal information in license files for privacy and security reasons, as they are an individual maintainer rather than a company.
Learnt from: nerdCopter
Repo: nerdCopter/bbl_parser PR: 2
File: README.md:520-521
Timestamp: 2025-08-29T19:53:41.354Z
Learning: nerdCopter uses AGPL-3.0-or-later licensing for the bbl_parser project with a dual-licensing approach that includes a separate commercial license option.
Learnt from: nerdCopter
Repo: nerdCopter/bbl_parser PR: 2
File: CONTRIBUTING.md:9-14
Timestamp: 2025-08-21T20:25:45.741Z
Learning: nerdCopter prefers to keep CLA language general using "project maintainer" rather than specifying a legal entity name, as they are an individual maintainer without an associated company.
Learnt from: nerdCopter
Repo: nerdCopter/bbl_parser PR: 2
File: LICENSE_COMMERCIAL:0-0
Timestamp: 2025-08-29T20:15:04.624Z
Learning: nerdCopter prefers clear positive indicators (✅) when describing fixes rather than using ❌ symbols which can be confusing when describing what was corrected in a positive context.
📚 Learning: 2025-12-08T21:15:02.434Z
Learnt from: nerdCopter
Repo: nerdCopter/bbl_parser PR: 0
File: :0-0
Timestamp: 2025-12-08T21:15:02.434Z
Learning: Repo nerdCopter/bbl_parser: For outside-diff review notes, prefer a compact, single-block comment with flat bullets (file:line → note), no nested <details> or admonitions; overflow should be linked via gist. Maintainer: nerdCopter.

Applied to files:

  • CHANGELOG.md
📚 Learning: 2025-12-19T21:17:26.889Z
Learnt from: CR
Repo: nerdCopter/bbl_parser PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-12-19T21:17:26.889Z
Learning: Applies to src/lib.rs : Public API must include: `parse_bbl_file()`, `parse_bbl_bytes()`, `BBLLog`, `ExportOptions`, `export_to_csv()`, `export_to_gpx()`, `export_to_event()`, conversion utilities, parser helpers

Applied to files:

  • CHANGELOG.md
📚 Learning: 2025-08-29T19:55:43.912Z
Learnt from: nerdCopter
Repo: nerdCopter/bbl_parser PR: 2
File: README.md:0-0
Timestamp: 2025-08-29T19:55:43.912Z
Learning: nerdCopter updated the bbl_parser project license from GPL-3.0-or-later to AGPL-3.0-or-later across all repository files (Cargo.toml, LICENSE, README.md) for consistency with the dual-licensing approach that includes a commercial license option.

Applied to files:

  • CHANGELOG.md
🪛 LanguageTool
CHANGELOG.md

[grammar] ~40-~40: Ensure spelling is correct
Context: ...rformance - Efficiently processes large blackbox logs via streaming architecture - Teste...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[grammar] ~93-~93: Ensure spelling is correct
Context: ... ensures compatibility with established blackbox format specifications while providing t...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
  • GitHub Check: Build Release Binaries (macos-latest, bbl_parser-macos-x64, target/release/bbl_parser)
  • GitHub Check: Build Release Binaries (ubuntu-latest, bbl_parser-linux-x64, target/release/bbl_parser)
  • GitHub Check: Build Release Binaries (windows-latest, bbl_parser-windows-x64, target/release/bbl_parser.exe)
🔇 Additional comments (1)
CHANGELOG.md (1)

1-100: Changelog structure and content are well-organized.

The document follows Keep a Changelog format clearly, with comprehensive sections covering features, technical highlights, performance, compatibility, documentation, roadmap, limitations, and acknowledgments. The level of detail appropriately reflects a 1.0.0 stable release milestone. Once the firmware version and INAV references are corrected, this changelog will be production-ready.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
OVERVIEW.md (1)

116-116: Inconsistent INAV reference not removed.

Line 116 still mentions "Betaflight, EmuFlight, INAV support" which contradicts the PR objective to remove INAV references and is inconsistent with the updates made to Line 29, README.md Line 5, and Cargo.toml Line 7.

🔎 Proposed fix
-- **Firmware Compatibility:** Betaflight, EmuFlight, INAV support
+- **Firmware Compatibility:** Betaflight, EmuFlight support
📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ec21e39 and bc79297.

⛔ Files ignored due to path filters (1)
  • Cargo.lock is excluded by !**/*.lock
📒 Files selected for processing (5)
  • .gitignore
  • CHANGELOG.md
  • Cargo.toml
  • OVERVIEW.md
  • README.md
🧰 Additional context used
📓 Path-based instructions (3)
Cargo.toml

📄 CodeRabbit inference engine (AGENTS.md)

Cargo.toml: CLI uses feature flag cli and entry point is built via default features or explicit --features=cli
Feature flags csv, cli, json, serde control optional dependencies; default: csv + cli
All feature combinations must compile without errors

Files:

  • Cargo.toml
README.md

📄 CodeRabbit inference engine (AGENTS.md)

Maintain a proper README.md file

Files:

  • README.md
OVERVIEW.md

📄 CodeRabbit inference engine (AGENTS.md)

Maintain a proper OVERVIEW.md file

Files:

  • OVERVIEW.md
🧠 Learnings (16)
📓 Common learnings
Learnt from: nerdCopter
Repo: nerdCopter/bbl_parser PR: 0
File: :0-0
Timestamp: 2025-12-08T21:15:02.434Z
Learning: Repo nerdCopter/bbl_parser: For outside-diff review notes, prefer a compact, single-block comment with flat bullets (file:line → note), no nested <details> or admonitions; overflow should be linked via gist. Maintainer: nerdCopter.
Learnt from: nerdCopter
Repo: nerdCopter/bbl_parser PR: 2
File: README.md:0-0
Timestamp: 2025-08-29T19:55:43.912Z
Learning: nerdCopter updated the bbl_parser project license from GPL-3.0-or-later to AGPL-3.0-or-later across all repository files (Cargo.toml, LICENSE, README.md) for consistency with the dual-licensing approach that includes a commercial license option.
Learnt from: nerdCopter
Repo: nerdCopter/bbl_parser PR: 0
File: :0-0
Timestamp: 2025-12-08T21:15:02.434Z
Learning: For bbl_parser reviews: nerdCopter prefers compact, single-block “outside diff” comments without nested <details> or admonitions; use flat bullets with file:line references and link a gist for overflow.
Learnt from: nerdCopter
Repo: nerdCopter/bbl_parser PR: 2
File: LICENSE_COMMERCIAL:1-4
Timestamp: 2025-08-29T19:52:05.099Z
Learning: nerdCopter prefers to avoid publishing personal information in license files for privacy and security reasons, as they are an individual maintainer rather than a company.
Learnt from: nerdCopter
Repo: nerdCopter/bbl_parser PR: 2
File: README.md:520-521
Timestamp: 2025-08-29T19:53:41.354Z
Learning: nerdCopter uses AGPL-3.0-or-later licensing for the bbl_parser project with a dual-licensing approach that includes a separate commercial license option.
Learnt from: nerdCopter
Repo: nerdCopter/bbl_parser PR: 2
File: CONTRIBUTING.md:9-14
Timestamp: 2025-08-21T20:25:45.741Z
Learning: nerdCopter prefers to keep CLA language general using "project maintainer" rather than specifying a legal entity name, as they are an individual maintainer without an associated company.
Learnt from: nerdCopter
Repo: nerdCopter/bbl_parser PR: 2
File: LICENSE_COMMERCIAL:0-0
Timestamp: 2025-08-29T20:15:04.624Z
Learning: nerdCopter prefers clear positive indicators (✅) when describing fixes rather than using ❌ symbols which can be confusing when describing what was corrected in a positive context.
📚 Learning: 2025-12-19T21:17:26.889Z
Learnt from: CR
Repo: nerdCopter/bbl_parser PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-12-19T21:17:26.889Z
Learning: Applies to src/lib.rs : Public API must include: `parse_bbl_file()`, `parse_bbl_bytes()`, `BBLLog`, `ExportOptions`, `export_to_csv()`, `export_to_gpx()`, `export_to_event()`, conversion utilities, parser helpers

Applied to files:

  • CHANGELOG.md
  • Cargo.toml
  • README.md
📚 Learning: 2025-12-19T21:17:26.889Z
Learnt from: CR
Repo: nerdCopter/bbl_parser PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-12-19T21:17:26.889Z
Learning: Applies to src/main.rs : CLI (`src/main.rs`) uses library export functions (`export_to_csv`, `export_to_gpx`, `export_to_event`) with CLI-specific status messages as thin wrapper with zero public functions

Applied to files:

  • CHANGELOG.md
📚 Learning: 2025-12-08T21:15:02.434Z
Learnt from: nerdCopter
Repo: nerdCopter/bbl_parser PR: 0
File: :0-0
Timestamp: 2025-12-08T21:15:02.434Z
Learning: Repo nerdCopter/bbl_parser: For outside-diff review notes, prefer a compact, single-block comment with flat bullets (file:line → note), no nested <details> or admonitions; overflow should be linked via gist. Maintainer: nerdCopter.

Applied to files:

  • CHANGELOG.md
  • README.md
📚 Learning: 2025-08-29T19:55:43.912Z
Learnt from: nerdCopter
Repo: nerdCopter/bbl_parser PR: 2
File: README.md:0-0
Timestamp: 2025-08-29T19:55:43.912Z
Learning: nerdCopter updated the bbl_parser project license from GPL-3.0-or-later to AGPL-3.0-or-later across all repository files (Cargo.toml, LICENSE, README.md) for consistency with the dual-licensing approach that includes a commercial license option.

Applied to files:

  • CHANGELOG.md
  • Cargo.toml
📚 Learning: 2025-12-08T21:15:02.434Z
Learnt from: nerdCopter
Repo: nerdCopter/bbl_parser PR: 0
File: :0-0
Timestamp: 2025-12-08T21:15:02.434Z
Learning: For bbl_parser reviews: nerdCopter prefers compact, single-block “outside diff” comments without nested <details> or admonitions; use flat bullets with file:line references and link a gist for overflow.

Applied to files:

  • README.md
📚 Learning: 2025-12-19T21:17:26.889Z
Learnt from: CR
Repo: nerdCopter/bbl_parser PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-12-19T21:17:26.889Z
Learning: Applies to src/**/*.rs : BEFORE ANY CODE CHANGES: Run `cargo fmt --all -- --check` to ensure formatting compliance

Applied to files:

  • .gitignore
📚 Learning: 2025-12-19T21:17:26.889Z
Learnt from: CR
Repo: nerdCopter/bbl_parser PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-12-19T21:17:26.889Z
Learning: Applies to src/**/*.rs : BEFORE ANY CODE CHANGES: Run `cargo clippy --all-targets --all-features -- -D warnings` to catch all issues

Applied to files:

  • .gitignore
📚 Learning: 2025-12-19T21:17:26.889Z
Learnt from: CR
Repo: nerdCopter/bbl_parser PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-12-19T21:17:26.889Z
Learning: Applies to OVERVIEW.md : Maintain a proper `OVERVIEW.md` file

Applied to files:

  • .gitignore
📚 Learning: 2025-12-19T21:17:26.889Z
Learnt from: CR
Repo: nerdCopter/bbl_parser PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-12-19T21:17:26.889Z
Learning: Only commit files: `src/**/*.rs`, `Cargo.*`, `README.md`, `OVERVIEW.md`, `.gitignore`, and `.github/**`; never use `git add .` or `git add -A`; follow `.gitignore`

Applied to files:

  • .gitignore
📚 Learning: 2025-12-19T21:17:26.889Z
Learnt from: CR
Repo: nerdCopter/bbl_parser PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-12-19T21:17:26.889Z
Learning: Applies to src/{lib.rs,parser/**/*.rs,export.rs} : Core logic in `src/lib.rs` with parser modules (`src/parser/`) and export functions (`src/export.rs`) shared by both library and CLI

Applied to files:

  • .gitignore
📚 Learning: 2025-12-19T21:17:26.889Z
Learnt from: CR
Repo: nerdCopter/bbl_parser PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-12-19T21:17:26.889Z
Learning: Applies to src/**/*.rs : ALWAYS run `cargo fmt --all` after making ANY code changes before moving to next steps

Applied to files:

  • .gitignore
📚 Learning: 2025-12-19T21:17:26.889Z
Learnt from: CR
Repo: nerdCopter/bbl_parser PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-12-19T21:17:26.889Z
Learning: Applies to src/**/*.rs : Code must pass `cargo fmt --all -- --check` without any formatting issues

Applied to files:

  • .gitignore
📚 Learning: 2025-12-19T21:17:26.889Z
Learnt from: CR
Repo: nerdCopter/bbl_parser PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-12-19T21:17:26.889Z
Learning: Applies to src/**/*.rs : Only commit if: `cargo clippy --all-targets --all-features -- -D warnings`, `cargo fmt --all -- --check`, `cargo test --verbose`, `cargo test --features=cli --verbose`, and `cargo build --release` all pass with no errors or warnings

Applied to files:

  • .gitignore
📚 Learning: 2025-12-19T21:17:26.889Z
Learnt from: CR
Repo: nerdCopter/bbl_parser PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-12-19T21:17:26.889Z
Learning: Applies to src/**/*.rs : Ensure `cargo build --release` has no errors or warnings

Applied to files:

  • .gitignore
📚 Learning: 2025-12-19T21:17:26.889Z
Learnt from: CR
Repo: nerdCopter/bbl_parser PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-12-19T21:17:26.889Z
Learning: Applies to src/**/*.rs : After running `cargo fmt --all`, ALWAYS verify with `cargo fmt --all -- --check` before proceeding

Applied to files:

  • .gitignore
🪛 LanguageTool
CHANGELOG.md

[grammar] ~40-~40: Ensure spelling is correct
Context: ...rformance - Efficiently processes large blackbox logs via streaming architecture - Teste...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[grammar] ~93-~93: Ensure spelling is correct
Context: ... ensures compatibility with established blackbox format specifications while providing t...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Test (windows-latest)
🔇 Additional comments (9)
README.md (1)

5-5: LGTM!

The removal of INAV from the supported firmware list is clear and aligns with the PR objectives and Cargo.toml description update.

.gitignore (1)

9-9: LGTM!

Adding CHANGELOG.md to the root whitelist is appropriate for tracking release notes in version control. The placement follows the existing pattern in the file.

Cargo.toml (2)

3-3: LGTM!

Version bump from 0.9.0 to 1.0.0 is appropriate for the first stable production release as described in the PR objectives.


7-7: LGTM!

Description update correctly removes INAV and now states "Parser for Betaflight/EmuFlight blackbox log files" which is consistent with README.md Line 5 and OVERVIEW.md Line 29.

CHANGELOG.md (5)

1-7: LGTM!

The changelog header follows the Keep a Changelog format and properly references Semantic Versioning, which is appropriate for a 1.0.0 stable release.


8-20: LGTM!

The initial features list is comprehensive and accurately describes the major capabilities of the 1.0.0 release, including the BBL parser, library API, export formats, and CLI functionality.


22-31: LGTM!

The remaining features in the Added section accurately describe the unit conversions, test coverage, documentation, and CI/CD capabilities of the release.


32-43: LGTM!

The Technical Highlights and Performance sections provide valuable context about the implementation approach and performance characteristics of the parser.


50-101: LGTM!

The remaining sections (Documentation, Future Roadmap, Known Limitations, Acknowledgments, and Version History) are well-structured and provide comprehensive information about the project's current state and future direction.

Comment thread CHANGELOG.md
Comment thread CHANGELOG.md
Comment thread OVERVIEW.md Outdated
- CHANGELOG.md (lines 46, 274): Remove INAV from firmware compatibility
- OVERVIEW.md (lines 116, 274): Remove INAV from firmware support statements

Ensures consistency across Cargo.toml, README.md, OVERVIEW.md, and CHANGELOG.md
which now all declare support for Betaflight and EmuFlight only.
INAV compatibility verified via comprehensive testing:
- 6 INAV files tested (142,734 frames, 18 flight logs)
- RUST parser: 100% success rate
- Exceeds external decoders (handles INAV 7.1.0 that fails elsewhere)
- All INAV versions supported (4.0.0, 4.1.0, 7.1.0, 8.0.0)

Restored references to Cargo.toml, README.md, OVERVIEW.md, CHANGELOG.md
Comprehensive compatibility testing validates support for Betaflight 4.0
through 4.5.x (6+ years of releases):
- Tested: 4.0.2 (2019), 4.1.1 (2020), 4.3.x (2022), 4.4.x-4.5.x (2023+)
- Result: 100% success rate across 60+ flight logs
- CSV export verified working on all tested versions
- Multi-log handling consistent across versions

Removed overly-conservative version limitation.
@nerdCopter nerdCopter merged commit 03b87d3 into master Dec 30, 2025
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant