docs: backport live-docs 8bfa0eb5f to master - #3695
Merged
Merged
Conversation
…add myNode The published page listed RaspiBlitz and myNode as supported and named four separate per-platform actions. None of that matches the 0.4 LND package: there is one Initialize Wallet action with a method selector, RaspiBlitz was never carried over, and myNode is only supported as of lnd-startos 0.21.1-beta:12. StartOS-to-StartOS, which has worked all along, was missing from the page entirely. Rewrites the platform list, the action names, and the steps around them, including the Bitcoin backend task and the bolt-to-SQLite conversion that now runs before an imported node starts. The claim that starting the service creates a wallet is also gone — in 0.4 the wallet is created by the action, and it is an existing wallet that blocks a migration. Replaces the hand-copy instructions with the safe route for an unsupported platform: close channels first and recover on-chain. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> (cherry picked from commit b3fc628)
…-start flow The action no longer performs the copy: it verifies it can sign in to the origin and schedules the migration, and starting LND stops the origin, copies the data, converts the database, and comes online — with progress under Health Checks (Wallet Import, then Database Conversion). Reorder the steps to match (backend before start; disconnect the old node after the migration completes, since the origin must be reachable when LND starts), reach Initialize Wallet via its task rather than an Actions menu it does not appear in, note that stopping LND mid-migration resumes safely and that rebooting a migrated Umbrel or myNode brings its LND back, and split troubleshooting into submit-time and start-time failures. Matches Start9Labs/lnd-startos#178 as it ships in 0.21.1-beta:12. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> (cherry picked from commit b78ebb7)
…uninstalled The import script no longer uninstalls the origin's LND — its data stays as the fallback until the migrated node has proven itself, and a stopped StartOS service stays stopped across reboots. Also note the failure path: after a few failed attempts LND stops itself and re-posts the Initialize Wallet task, which is how the user corrects the details and retries. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> (cherry picked from commit 2a0561e)
Contributor
|
The fallback that opened this PR was spurious — Fix in #3696 — with it, this exact range ( |
dr-bonez
pushed a commit
that referenced
this pull request
Aug 12, 2026
…us PR (#3696) A PR merged into live-docs with the merge button puts a merge commit in the pushed range, and cherry-pick refuses one without -m ("is a merge but no -m option was given"). The step treats any nonzero exit as a conflict, so it opened a PR saying "resolve the conflicts before merging" against a branch with none, and the per-commit fallback loop then hit the same error and warned the merge was "not included" when its content was already there. It fired on every merge-commit push so far: #3657, #3691, #3695. Pick the first-parent list with -m 1, so a merged PR is one patch: the merge's own net change. -m 1 is a no-op on a non-merge, so squash-merge pushes are unaffected. Two smaller corrections in the same step, both observed on those PRs: the conflict wording now belongs to the conflict reason alone rather than to every unexpected failure, and a branch whose conflicts were resolved by keeping the markers now names those files in the body — #3657 shipped 130 markers across 14 files, including start-sdk's StartSdk.ts, and GitHub still reported it mergeable.
dr-bonez
approved these changes
Aug 12, 2026
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
3 participants
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.
Automated backport of the documentation change published to docs.start9.com from
live-docs(8bfa0eb).Until this lands, master's copy of the docs is out of step and the next tag will revert the published fix.
Body corrected by hand — the original was wrong on both counts. It said "could not be applied to master unattended — resolve the conflicts before merging" and warned that
8bfa0eb5fwas "not included" and had to be applied by hand. Neither is true:mergeable: true, and this branch is content-complete:git diff <branch> 8bfa0eb5f -- projects/start-docs/is empty.8bfa0eb5fis the merge of docs(start-docs): correct the LND migration guide — drop RaspiBlitz, add myNode #3663. It is a clean, non-evil merge (git diff-tree --cc 8bfa0eb5fprints no file rows), so it carries no content of its own — the three commits it merged are all here.The backport fell back to a PR because
git cherry-pickrefuses a merge commit without-m, and the workflow reads any nonzero exit as a conflict. Fix in #3696; with it, this range lands on master unattended.Merge this rather than closing it.
docs-backport.ymlhas noworkflow_dispatch, and the next push'sgithub.event.beforewill be8bfa0eb5f, so these commits will not appear in a range again.