docs: add general INAV upgrade guide to Getting Started - #22
Open
Raffi1202 wants to merge 1 commit into
Open
Conversation
Ports the wiki page "Upgrading from an older version of INAV to the current version" into the docs site as a version-independent procedure: back up the configuration, note version and target, adjust the settings for the new release, flash with Full chip erase, restore, upload the OSD font again, recalibrate and check on the bench. The wiki text was stale, so every step was checked against the current sources instead of transcribed. Configurator button labels and the backup, restore and migration flow come from the Configurator source (locale/en/messages.json, tabs/cli.html, tabs/firmware_flasher.html, tabs/firmware_flasher_restore.js, js/backup_restore.js, js/migration). The CLI behaviour of diff, diff all, dump, defaults and save comes from the firmware source (src/main/fc/cli.c), and the OSD font warning from src/main/io/osd.c. Release-specific settings changes are not duplicated here, the page points at the release notes for those. Both links to the old wiki page in the release notes now point at the new page.
Raffi1202
marked this pull request as ready for review
September 11, 2026 14:55
Code Review by Qodo🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)
Great, no issues found!Qodo reviewed your code and found no material issues that require reviewTip of the day💡 Did you know, you can switch off images and animations for a plain-text comment |
PR Summary by QodoAdd version-independent INAV upgrade guide
AI Description
Diagram
High-Level Assessment
Files changed (2)
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of moving the GitHub wiki onto the docs site. Ports "Upgrading from an older version of INAV to the current version" to
docs/03-getting-started/07-upgrade-inav.mdx.Written version-independent on purpose
The wiki page was pinned to specific releases and went stale every cycle. This one describes the procedure instead: back up the configuration, note version and target, adjust the settings the new release changed, flash with Full chip erase, restore, upload the OSD font again, recalibrate, and check on the bench before flying.
Release-specific settings changes are deliberately not duplicated here - the page points at the release notes, which is the one place they are maintained.
Checked, not transcribed
The wiki text was stale, so every step was verified against the current sources:
locale/en/messages.json,tabs/cli.html,tabs/firmware_flasher.html,tabs/firmware_flasher_restore.js,js/backup_restore.js,js/migrationdiff,diff all,dump,defaultsandsave:src/main/fc/cli.csrc/main/io/osd.cAlso
Both links to the old wiki page in
docs/02-release-notes.mdxnow point at the new page.That file is also touched by #19, on different lines. The two merge cleanly, checked with
git merge-tree.