2.5 years / 47 commits since the last release - time for a new release?
Are these commits being held for a future date (BF 4.6?) Or is this just a backlog that nobody got to? (If so, I get it! :) ) Should people pull scripts from master branch? Or could the release process be automated via GitHub Actions, maybe?
FYI, GitHub previously offered an Action to do this kind of thing, but have deprecated it and refer to third-party Actions (of which they link 4): https://github.com/actions/create-release
This could be configured to run after every commit or just every week/month/whatever.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within a week.
Yes, a new release should definitely be considered. In the current state, in some scenarios the latest release does not work at all, where the current branch has already fixed these issues (e.g. if the flight controller has no support for VTX, the script does not open - this was fixed in January 2024, but is not released yet)
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within a week.
Does everything work with 2025.12 ?