Skip to content
WPTomWPTom docs

Keep your site up to date

Templates get new versions: fixes, new sections, new integrations. Your license includes them for life. wptom update brings a new version into your site and keeps everything you changed. Full reference: wptom update.

Is there a new version?

Section titled “Is there a new version?”
  • What’s new on wptom.com lists every release.
  • In your project, npx wptom update --dry-run checks and shows what would change, without changing anything.
  • Your AI assistant can check too, through the MCP server (get_project_info).

Update, step by step

Section titled “Update, step by step”

  1. Save your work first. In the project folder:

    Terminal window
    git add .
    git commit -m "Before update"

    This is your safety net: you can always go back.

  2. See what will happen:

    Terminal window
    npx wptom update --dry-run
    ◇  aurora 1.0.0 → 1.1.0
    ◇  3 updated · 0 conflicts · 0 removed ──────────╮
    │                                                 │
    │  ~ src/components/Header.astro                  │
    │  ⇄ src/content/singletons/ui.json  merged with your edits │
    │  + src/components/sections/Logos.astro          │
    │  = src/styles/global.css  kept (yours)          │
    ├─────────────────────────────────────────────────╯
    └  Dry run: nothing was written.
    Mark Meaning
    ~ You never changed this file: it takes the new version
    ⇄ You and the update both changed it, in different places: merged
    + A new file in this version
    - Removed in this version (you never changed it)
    ! Both changed the same lines: a conflict for you to resolve
    ? A binary file (e.g. a photo) changed on both sides: the new one is saved next to yours
    = Kept as it is (you changed it and the update didn’t, or you deleted it)

  3. Update:

    Terminal window
    npx wptom update

    If there are conflicts, it asks Some files need your attention afterwards. Apply the update? first.

  4. Install, check, commit:

    Terminal window
    npm install
    npm run build
    git add .
    git commit -m "Update to 1.1.0"

    npm install picks up new or updated packages. If npm run build passes, push to publish.

Resolving a conflict

Section titled “Resolving a conflict”

A conflict means you and the update changed the same lines. The file then contains both versions between markers:

<<<<<<< yours: src/content/singletons/site.json
  "tagline": "Ship faster with Northlight",
=======
  "tagline": "Find the signal in your product data.",
>>>>>>> wptom update
  1. Open the file. VS Code highlights conflicts and offers Accept Current (yours), Accept Incoming (the update) or Accept Both above each one.
  2. Keep what you want and delete the marker lines (<<<<<<<, =======, >>>>>>>).
  3. Search the project for <<<<<<< to be sure none is left, then build and commit.

For a photo or other binary file that changed on both sides, you keep yours and the new one is saved next to it as photo.jpg.wptom-new: compare, keep one, delete the other.

Something went wrong?

Section titled “Something went wrong?”

Undo the whole update with Git:

Terminal window
git restore .
git clean -fd

This puts every file back as it was at your last commit (and removes files the update added).