Skip to content

Updating SD.Next

Recommended update flow is to use --update or --upgrade (aliases).

./webui.sh --update   # Linux/macOS
webui.bat --update    # Windows
webui.ps1 --update    # Windows PowerShell

Under the hood, update uses standard Git operations plus extra checks:

  • verifies core repo status and performs auto-repair if needed
  • updates the core SD.Next repo
  • updates built-in submodules
  • synchronizes submodule revisions

Manual Update

Instead of automatic update with --update, you can update SD.Next manually using Git:

git pull

Note

If you have Git conflicts, resolve them before running git pull.

This updates only the core repo. Also check submodule status:

git submodule status
git submodule update

Switching Branch

SD.Next development uses multiple GitHub branches:

  • Stable branch: master Typically updated every few weeks after feature testing.
  • Development branch: dev Updated regularly (often daily) with latest fixes and features. This branch has the newest patches, but is not fully tested. When a release is ready, dev is merged into master.
  • Feature branches: Created as needed for larger features. Merged into dev when complete, then removed.

You can switch branches at any time without a separate SD.Next installation:

git checkout master  # switch to master
git checkout dev     # switch to dev

Tip

Run update before switching branches.

[!WARNING] Large branch differences may trigger installation of additional requirements.