Skip to content

Upgrade: Beta to v1.0.0 Stable

This guide walks you through upgrading Velocity from any beta release (v0.1.0-beta through v0.5.0-beta) to the v1.0.0 stable release.

Beta (latest)v1.0.0 Stable
Astro6.0.0-beta.206.0.0
@astrojs/mdx5.0.0-beta.125.0.0
@astrojs/react5.0.0-beta.45.0.0
@astrojs/check0.9.7-beta.10.9.7
@astrojs/sitemap^3.7.0^3.7.1

If you have create-velocity-astro installed:

  1. Update the CLI

    Terminal window
    npm install -g create-velocity-astro@latest
  2. Run the upgrade

    Terminal window
    pnpm create velocity-astro upgrade

    The CLI will:

    • Download the latest template
    • Show what files will change
    • Update safe files (components, layouts, lib, styles)
    • Bump package.json dependencies to stable versions
    • Update your .velocity.json version marker
    • Show migration notes relevant to your current version
  3. Install and verify

    Terminal window
    pnpm install && pnpm build
  1. Update package.json dependencies

    "astro": "6.0.0-beta.20",
    "astro": "6.0.0",
    "@astrojs/mdx": "5.0.0-beta.12",
    "@astrojs/mdx": "5.0.0",
    "@astrojs/react": "5.0.0-beta.4",
    "@astrojs/react": "5.0.0",
    "@astrojs/check": "0.9.7-beta.1",
    "@astrojs/check": "0.9.7",
    "@astrojs/sitemap": "^3.7.0",
    "@astrojs/sitemap": "^3.7.1",
  2. Install and build

    Terminal window
    pnpm install && pnpm build
  3. Update .velocity.json

    "version": "0.5.0-beta"
    "version": "1.0.0"

If you’re upgrading from a version earlier than v0.5.0-beta, review these additional guides first:

  • Vitest 2 → 3 migration: Astro 6 bundles Vite 7, which requires Vitest 3.2+. If you have a custom vitest.config.ts, review the Vitest 3 migration guide.
  • Image defaults changed: Cropping is now enabled by default and images are never upscaled. If images appear cropped unexpectedly, add fit: 'contain' to your Image components.
  • Heading ID changes: The heading ID generation algorithm changed. Verify any internal anchor links (#my-heading) still resolve correctly.

Follow the existing upgrade guides in order:

  1. v0.1.0-beta to v0.2.0-beta
  2. v0.2.0-beta to v0.3.0-beta
  3. v0.3.x-beta to v0.4.0-beta

Then apply the steps in this guide.

Run the full verification suite:

Terminal window
pnpm lint && pnpm check && pnpm build

All three commands should complete with zero errors. The stable releases are fully compatible with the existing beta.20 codebase.