Skip to content

Updates

A Premium site has three things that update on their own schedules.

WhatHow
New templatesgit pull in your clone of the Premium repository
The Premium Kitpnpm kit:update inside your site
Velocitypnpm create velocity-astro@latest upgrade inside your site

Kit fixes and new components land in kit/ in the Premium repository, and kit/CHANGELOG.md says what changed. Run this inside your site:

Terminal window
pnpm kit:update --check # see what would change
pnpm kit:update # update

The command fetches the latest kit with your own GitHub access, the account your purchase invited. It holds no token, so it only works for an account with access to the repository. Then it:

  • replaces kit files you haven’t touched,
  • adds new kit files and removes ones the kit dropped,
  • leaves any kit file you edited alone and lists it,
  • prints the changelog entries newer than your kit,
  • records the new version in src/components/premium/kit.json.

Review the result with git diff and run pnpm validate.

FlagDescription
--checkShow what would change, change nothing
--forceAlso replace kit files you edited
--from=<path>Use a local clone of the Premium repository instead of fetching

If git can’t reach the repository, see Get Access for signing git in, or clone it yourself and use --from:

Terminal window
pnpm kit:update --from=../templates

Templates are normal Velocity projects with a .velocity.json, so the upgrade command works from day one. It updates Velocity’s own files and leaves your content, theme, header, footer, the template’s files and the Premium Kit alone.