From a2464619fa2063ff301dd03698901e6bf0a0e672 Mon Sep 17 00:00:00 2001 From: Ray Morris Date: Sun, 20 Sep 2026 10:04:13 -0500 Subject: [PATCH 1/4] Update PR branch-suggestion workflow for the 10.x/11.x cycle maintenance-9.x -> maintenance-10.x (now the compatible/current choice) maintenance-10.x -> maintenance-11.x (now the breaking/next-major choice) maintenance-11.x was just created off maintenance-10.x's tip, per the release process's "create the next major's branch at first RC" rule. --- .github/workflows/pr-branch-suggestion.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/workflows/pr-branch-suggestion.yml b/.github/workflows/pr-branch-suggestion.yml index 110deb98338..06c65bfd2f8 100644 --- a/.github/workflows/pr-branch-suggestion.yml +++ b/.github/workflows/pr-branch-suggestion.yml @@ -20,9 +20,9 @@ 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 If \`master\` is the correct target for this change, no action is needed. From f043c0ba57f97c6e59185a9cafa2977d02be6cfe Mon Sep 17 00:00:00 2001 From: Ray Morris Date: Sun, 20 Sep 2026 10:11:59 -0500 Subject: [PATCH 2/4] Clarify the master-target note in the branch-suggestion comment Merging to master means the change never ends up in any release, rather than implying that's an acceptable default. --- .github/workflows/pr-branch-suggestion.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/pr-branch-suggestion.yml b/.github/workflows/pr-branch-suggestion.yml index 06c65bfd2f8..ffa6e52850e 100644 --- a/.github/workflows/pr-branch-suggestion.yml +++ b/.github/workflows/pr-branch-suggestion.yml @@ -24,7 +24,7 @@ jobs: - **\`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 - 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. --- *This is an automated suggestion to help route contributions to the appropriate branch.*`; From 863c2fa8405e220d28cde2047bbf33ea732e41f8 Mon Sep 17 00:00:00 2001 From: Ray Morris Date: Sun, 20 Sep 2026 14:28:21 -0500 Subject: [PATCH 3/4] docs: update pr-branch-suggestion README entry for 10.x/11.x cycle --- .github/workflows/README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.github/workflows/README.md b/.github/workflows/README.md index fbd80adeda8..e315c472ff1 100644 --- a/.github/workflows/README.md +++ b/.github/workflows/README.md @@ -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 From f3c75c6ee9eb688367f155e8e9a8556f44e34324 Mon Sep 17 00:00:00 2001 From: Ray Morris Date: Sun, 20 Sep 2026 22:26:03 -0500 Subject: [PATCH 4/4] add link to https://inavflight.github.io --- readme.md | 31 ++++--------------------------- 1 file changed, 4 insertions(+), 27 deletions(-) diff --git a/readme.md b/readme.md index b8dbadf3909..ee65067f36f 100644 --- a/readme.md +++ b/readme.md @@ -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. @@ -12,11 +15,7 @@ # 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. @@ -24,28 +23,6 @@ ![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)