Updates

Your purchase includes lifetime access with weekly updates. You pay once; there's no subscription.

How updates are delivered

Weekly updates → your kit repository (main) → your upstream/main → merge into your project

• Every update is pushed to your kit repository (saas-laravel-starter-kit-vue, -react or -svelte).
• We publish updates weekly, and the main branch of your kit repository always has the latest version.
• The Release Notes page lists what changed in each update.
• If you'd like a notification, watch the repository on GitHub (Watch → Custom → Releases/All activity).

Recommended remote setup

We suggest keeping the kit as upstream and your own repository as origin:

Important

Keep your copy of the kit in a private repository. Push it to a public one and anyone can read the full source code of a paid starter kit. Publishing it also isn't allowed under the SaaS Laravel Commercial License.

Pick Private when you create the repository. Already made it public? Go to the repository's Settings → General → Danger Zone → Change visibility and switch it to private.

Private

PublicAnyone on the internet can see this repository.

PrivateYou choose who can see and commit to this repository.

Remote	Points to
origin	Your project, e.g. git@github.com:your-org/my-saas.git
upstream	The kit, e.g. https://github.com/the-erag/saas-laravel-starter-kit-vue.git

Cloned the kit directly

git remote rename origin upstream
git remote add origin git@github.com:your-org/my-saas.git
git push -u origin main

Started from a copy

git remote add upstream https://github.com/the-erag/saas-laravel-starter-kit-vue.git
git fetch upstream
git merge upstream/main --allow-unrelated-histories

You can check the result with git remote -v. If you have the All Starter Kits bundle, add each kit you use as the upstream of the project built on it.

Pulling an update

1. Merge the kit into a separate branch:

   git checkout -b kit-update
   git fetch upstream
   git log --oneline HEAD..upstream/main    # what changed
   git merge upstream/main

2. Fix any conflicts, then update your dependencies, databases and generated files (the commands are below).

3. Once everything passes, merge kit-update into your main branch.

Commands to run after merging

composer install
npm install
php artisan migrate
php artisan tenants:migrate
php artisan erag:generate-lang
php artisan typescript:transform
php artisan wayfinder:generate --with-form
npm run build
php artisan test --compact

Check new migrations

Read any new files in database/migrations and database/migrations/tenant before you run them in production, and back up your databases first. Seeders can change too (menus, permissions), so re-run them where you need to (see Users, roles & permissions).

Fewer conflicts

• Build new features as new modules in Modules/, with new pages and components, rather than editing kit files in place.
• Put your own translations in new files under lang/<locale>/modules/.
• Add new permissions in new files in config/permissions/.
• Generated files (resources/js/lang, resources/js/types) often conflict. Take either side, then re-run the generators above.

Cherry-picking

If you only want one specific fix:

git fetch upstream
git log --oneline upstream/main
git cherry-pick <commit-sha>