What changes in an update
Each theme has a CHANGELOG.md listing every release. Updates fix bugs, keep up with new Astro and Tailwind versions, and sometimes add pages or sections. Download the latest version the same way you got the original.
Apply an update with Git
The trick is to keep an untouched copy of the theme on its own branch. If you followed Getting started, you already have it. If not, create it from your first commit:
git branch theme $(git rev-list --max-parents=0 HEAD)When an update arrives:
git checkout theme
# Delete everything except .git, then unzip the new version here
git add -A
git commit -m "Theme 1.2.0"
git checkout main
git merge themeGit applies only what changed between versions on top of your work. If you and the update both edited the same lines, Git marks the conflict and you pick what to keep. Run npm install and npm run build afterwards.
No Git? Read the changelog, then copy over only the files it mentions.
Keep dependencies current
Between theme updates you can upgrade Astro and friends yourself:
npx @astrojs/upgrade # Astro and its integrations
npm outdated # everything elseRun npm run typecheck and npm run build after upgrading.
Support
Send a message through the contact form with your theme name and what you’ve tried. We reply within one business day.
| Covered | Not covered |
|---|---|
| Installing and running the theme | Building custom features |
| Bugs in the theme | Problems caused by your own changes |
| Questions about these docs | Hosting or domain setup beyond the Deploy guide |