Upgrading the boilerplate

You own the code, so upgrading is a git merge, not a package bump. Keep a reference to the original repository as a second remote and pull releases when you want them.

Pro plan, lifetime updates

Pro includes every future release. Starter is licensed to the version you downloaded. Either way, the merge workflow below is the same.

Add the upstream remote (once)

git remote add upstream <shipveryfast-repo-url>
git fetch upstream

Create a branch and merge

Never merge straight into main. Branch first so you can review.

git checkout -b upgrade/svf
git merge upstream/main

Resolve conflicts

Conflicts cluster in files you have customized (config, landing copy, pricing). Resolve them, then reinstall in case dependencies changed.

npm install

Run the gate, then merge

npm run lint && npm run test && npm run build

Green across the board? Open a PR from the upgrade branch into main.

Keep your edits localized

The more you keep custom logic in your own files and out of the shipped ones, the smaller every future merge. Prefer adding new modules over editing core files in place.

Next steps

CI/CDRun the gate automatically on every PR.TestingWhat the suite covers.