Drop Point Release in favour of Rolling Release#158
Conversation
…e to `2024-7-21` The `-1.0.0` suffix indicates this version is the development branch of Version 1.1.0, and is considered a "pre-release".
…ault for this branch
…NABLED` and `CRSF_DEBUG_ENABLE_VERSION_OUTPUT` are both set to `1`
Development focus is now on the upcoming Version 1.1.0 of CRSF for Arduino.
These were obliterated in the previous re-base.
Three new callback functions are added to the Serial Receiver Interface: - `onLinkDownCallback` Runs when no CRSF data is received within `CRSF_FAILSAFE_STAGE1_MS` (default is 300 milliseconds), and this may be used to facilitate fail-safe conditions. - `onLinkUpCallback` Runs when a reconnection is established, and this may be used to facilitate fail-safe recovery. - `onRawDataCallback` Runs whenever individual bytes from the raw CRSF data stream is received, and this may be used to facilitate UART pass-through. Signed-off-by: Dmytro <ddanilchenko@dataxdev.com> Co-authored-by: Cassandra "ZZ Cat" Robinson <nicad.heli.flier@gmail.com>
CRSF for Arduin is now developed in a Dev Container.
## Changes This is a Python rewrite of the old Bash scripts used to start the Quality Control CI pipeline. ## Breaking changes This pull request breaks the existing QC and vulnerability scanning CI workflows, because I changed the directories around to be more aligned with CFA's development container and I moved the main `platformio.ini` file away into a folder that houses the build script to run everything from there. So, the existing CI is expecting that `platformio.ini` file to still be present in CFA's root.
When I initially containerised CFA, I had the hare-brained idea of using absolute paths in CFA's configuration files. Turns out, this led to obscure permission denial errors whenever I tried to run both PlatformIO commands or CFA's `build.py` script as a part of the QC and QL workflows. This resolves the broken QC and QL workflows. Everything should run as expected now.
Signed-off-by: Cassandra "ZZ Cat" Robinson <nicad.heli.flier@gmail.com>
This is a remnant of the point release system and is not relevant to CFA's new rolling release model.
… and `pull_request` events
…ge matrix Because I am scripting CFA's Quality Control using Python, it's fair to check the scripts for any nasties too. =^/.~=
|
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
|
Right! I am merging this into the Main-Trunk as is. There are some other things I want to do with CFA regarding the security of its infrastructure, but that is now out-of-scope of this Pull Request. I'll see what happens anyway. |
github-project-automation
bot
moved this from In Progress
to Done
in Development Schedule
2 participants
I am merging the entirety of the
Version-1.1.0-Developmentbranch as-is into theMain-Trunkin accordance with my last announcement regarding dropping the Point Release system for Rolling Release.This means updates to CFA may be smaller or less frequent, but this is proportional to balancing my workload here with everything else I have going on in my life.
I love working on CRSFforArduino, but not at the expense of burning myself out—especially constantly. Adopting the Rolling Release system means when I do work on CFA, I can put my focus on what matters to the project and not bog myself down with overload.
The upcoming release is no longer named "Version 1.1.0".
It is now labelled based on ISO 8601 date the release is made. The numbering will look something like "YYYY.MM.DD" or "2025.8.30" to remain backward-compatible with existing Semantic Versioning that both PlatformIO and Arduino IDE uses.
The full release title shall look something like this: "Release 2025-08-30", but both the
library.propertiesandlibrary.jsonfiles will show "2025.8.30" in their respective version fields.More information will be added here as I update this Pull Request.
Currently, I am finalising the
Version-1.1.0-Developmentbranch and by the time I am finished, it will be merged into the Main-Trunk and CFA's first Rolling Release will be made.