Update Guide
How you update depends on how you installed
mdgarden in the first place.
npm
npm install -g mdgarden@latest
Homebrew
brew upgrade mdgarden
Standalone binary
Use the built-in updater:
mdgarden update
It checks GitHub Releases first. If you're already on the latest version it stops; otherwise it upgrades in place.
Add --background if you want the update to run detached and return control
immediately:
mdgarden update --background
Force a reinstall even when you're already current:
mdgarden update --force
It automatically chooses the right update path:
- standalone installs re-run the bundled installer against the current binary directory;
- Homebrew installs use
brew upgrade mdgarden; - npm installs use
npm install -g mdgarden@latest.
If you prefer, you can still re-run the same install script you used the first time — it always fetches the latest release:
curl -fsSL https://raw.githubusercontent.com/THANSHEER/mdgarden/main/scripts/install.sh | sh
irm https://raw.githubusercontent.com/THANSHEER/mdgarden/main/scripts/install.ps1 | iex
Or download the newest binary directly from
GitHub Releases and replace
the old one on your PATH.
Checking your version
mdgarden --version
Compare it against the latest tag on GitHub Releases, where every release lists what changed.
Check the release notes for breaking changes to mdgarden.config.json —
run mdgarden config get after updating to confirm your config still
resolves the way you expect, and see
Troubleshooting if something looks off.