Skip to content

Release/9.1 to maintenance-10.x #12005

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
sensei-hacker wants to merge 7 commits into
base: maintenance-10.x
Choose a base branch
from
+9 −31
Open

Release/9.1 to maintenance-10.x #12005

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
a246461
Update PR branch-suggestion workflow for the 10.x/11.x cycle
sensei-hacker Sep 20, 2026
f043c0b
Clarify the master-target note in the branch-suggestion comment
sensei-hacker Sep 20, 2026
df1a24b
Merge pull request #11989 from sensei-hacker/update-pr-branch-suggest…
sensei-hacker Sep 20, 2026
863c2fa
docs: update pr-branch-suggestion README entry for 10.x/11.x cycle
sensei-hacker Sep 20, 2026
b41db7f
Merge pull request #11990 from sensei-hacker/update-pr-branch-suggest…
sensei-hacker Sep 20, 2026
f3c75c6
add link to https://inavflight.github.io
sensei-hacker Sep 21, 2026
7cb12ea
Merge pull request #11991 from sensei-hacker/readme-update.md
sensei-hacker Sep 21, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion .github/workflows/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -120,7 +120,8 @@ as `pr-test-builds.yml`** (secrets available even for fork PRs).

#### `pr-branch-suggestion.yml` - Branch Targeting Suggestion
**Triggers:** PRs targeting master branch
**Purpose:** Suggests using maintenance-9.x or maintenance-10.x instead
**Purpose:** Suggests using maintenance-10.x (backward-compatible) or
maintenance-11.x (breaking compatibility) instead

#### `non-code-change.yaml` - Non-Code Change Detection
**Triggers:** Pull requests
Expand Down
6 changes: 3 additions & 3 deletions .github/workflows/pr-branch-suggestion.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,11 +20,11 @@ jobs:

You've targeted the \`master\` branch with this PR. Please consider if a version branch might be more appropriate:

- **\`maintenance-9.x\`** - If your change is backward-compatible and won't create compatibility issues between INAV firmware and Configurator 9.x versions. This will allow your PR to be included in the next 9.x release.
- **\`maintenance-10.x\`** - If your change is backward-compatible and won't create compatibility issues between INAV firmware and Configurator 10.x versions. This will allow your PR to be included in the next 10.x release.

- **\`maintenance-10.x\`** - If your change introduces compatibility requirements between firmware and configurator that would break 9.x compatibility. This is for PRs which will be included in INAV 10.x
- **\`maintenance-11.x\`** - If your change introduces compatibility requirements between firmware and configurator that would break 10.x compatibility. This is for PRs which will be included in INAV 11.x

@qodo-free-for-open-source-projects qodo-free-for-open-source-projects Bot Sep 22, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Remediation recommended

2. Suggested 11.x changes lack nightly builds 🐞 Bug ☼ Reliability

The updated suggestion directs breaking changes to maintenance-11.x, but the nightly build
workflow has no maintenance-11.x push trigger. Contributors following the new instruction can
therefore merge changes to that branch without the repository’s nightly firmware build running for
it.
Agent Prompt 
## Issue description
The branch suggestion introduces `maintenance-11.x` as the destination for breaking changes, but the nightly build workflow does not run on pushes to that branch. This leaves the newly recommended release branch without nightly build coverage.

## Fix Focus Areas
- .github/workflows/pr-branch-suggestion.yml[25-25]
- .github/workflows/nightly-build.yml[5-13]

## Recommended Fix
Add `maintenance-11.x` to the nightly build workflow's branch trigger list, or update the branch suggestion to target only branches that are currently covered by the release validation workflows.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


If \`master\` is the correct target for this change, no action is needed.
Merging to \`master\` would mean your change never ends up in any release.

@qodo-free-for-open-source-projects qodo-free-for-open-source-projects Bot Sep 22, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Remediation recommended

1. Master changes can miss every release 🐞 Bug ≡ Correctness

The branch-suggestion comment now tells contributors that merging to master means their change
never reaches a release. The documented release workflow merges the current maintenance branch into
master and then propagates master into the next version branch, so contributors may incorrectly
retarget valid changes away from the repository’s intended integration path.
Agent Prompt 
## Issue description
The branch-suggestion comment claims that changes merged to `master` never reach a release, but the repository's documented release workflow explicitly propagates changes from `master` into the next maintenance branch. This can cause contributors to target the wrong branch.

## Fix Focus Areas
- .github/workflows/pr-branch-suggestion.yml[27-27]
- docs/development/Development.md[170-198]

## Recommended Fix
Replace the absolute statement with wording that explains the intended role of `master` and directs contributors to the appropriate maintenance branch when they want a change included in a specific release. Keep the guidance consistent with the documented `maintenance-9.x -> master -> maintenance-10.x` propagation flow.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


---
*This is an automated suggestion to help route contributions to the appropriate branch.*`;
Expand Down
31 changes: 4 additions & 27 deletions readme.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,8 @@
# INAV - navigation capable flight controller

# INAV Documentation
> For documentation on using INAV, see our new docs site at [inavflight.github.io](https://inavflight.github.io/)

# F411 PSA

> INAV no longer accepts targets based on STM32 F411 MCU.
Expand All @@ -12,40 +15,14 @@

# M7, M6 and older UBLOX GPS units PSA

> INAV 8.0 will mark those GPS as deprecated and INAV 9.0.0 will require UBLOX units with Protocol version 15.00 or newer. This means that you need a GPS unit based on UBLOX M8 or newer.

> If you want to check the protocol version of your unit, it is displayed in INAV's 7.0.0+ status cli command.
> INAV 8.0.0 will warn you if your GPS is too old.
> ```GPS: HW Version: Unknown Proto: 0.00 Baud: 115200 (UBLOX Proto >= 15.0 required)```
> INAV 8.0 marked those GPS as deprecated and INAV 9.0.0 and higher require UBLOX units with Protocol version 15.00 or newer. This means that you need a GPS unit based on UBLOX M8 or newer.


> M8, M9 and M10 GPS are the most common units in use today, are readly available and have similar capabilities.
>Mantaining and testing GPS changes across this many UBLOX versions is a challenge and takes a lot of time. Removing the support for older devices will simplify code.

![INAV](http://static.rcgroups.net/forums/attachments/6/1/0/3/7/6/a9088858-102-inav.png)

# PosHold, Navigation and RTH without compass PSA

Attention all drone pilots and enthusiasts,

Are you ready to take your flights to new heights with INAV 7.1? We've got some important information to share with you.

INAV 7.1 brings an exciting update to navigation capabilities. Now, you can soar through the skies, navigate waypoints, and even return to home without relying on a compass. Yes, you heard that right! But before you launch into the air, there's something crucial to consider.

While INAV 7.1 may not require a compass for basic navigation functions, we strongly advise you to install one for optimal flight performance. Here's why:

🛰️ Better Flight Precision: A compass provides essential data for accurate navigation, ensuring smoother and more precise flight paths.

🌐 Enhanced Reliability: With a compass onboard, your drone can maintain stability even in challenging environments, low speeds and strong wind.

🚀 Minimize Risks: Although INAV 7.1 can get you where you need to go without a compass, flying without one may result in a bumpier ride and increased risk of drift or inaccurate positioning.

Remember, safety and efficiency are paramount when operating drones. By installing a compass, you're not just enhancing your flight experience, but also prioritizing safety for yourself and those around you.

So, before you take off on your next adventure, make sure to equip your drone with a compass. It's the smart choice for smoother flights and better navigation.

Fly safe, fly smart with INAV 7.1 and a compass by your side!

# INAV Community

* [INAV Discord Server](https://discord.gg/peg2hhbYwN)
Expand Down
Loading