Astro upgrade: from Astro 5 or 6 to the current major line.
An Astro upgrade runs in a separate branch with a preview environment, so your live site stays online. We tell you first when the jump is the wrong budget for your site.
Two majors in one year
Astro 6 went stable in March 2026, Astro 7 in June 2026. Planning yearly puts you out of step.
One major of safety net
Security fixes cover exactly one previous major version. Astro 5 sits outside that window.
No feature freeze required
Campaign pages, blog posts and corrections keep going live while the upgrade branch is rebased.
See what we build.
Mini Marvin is our own progressive web app, designed, built and running live in the browser.
Swipe baby names instead of scrolling
Mini Marvin is our progressive web app for finding baby names: swipe through 10,000+ first names right in the browser, no app store needed.
What a major upgrade actually touches.
-
Framework and configuration
Renamed options, changed defaults, moved responsibilities. We work through the upgrade notes in order.
More on this
With several majors skipped we jump one major at a time, and the project has to build between the steps. That keeps every change traceable to the jump that caused it. Everything without a breaking change happens first on main, so the branch holds only the forced changes.
-
Integrations can block the jump
React, Preact, Svelte, Vue, SolidJS and Alpine.js run side by side as islands, each on its own release cycle.
More on this
If one of those integrations does not reach the target major, the whole upgrade waits on it. That check therefore comes first. Three routes open up: replace it, rebuild the island, or take over its maintenance. The decision happens before the jump, never halfway through.
-
Content model, adapter and SDKs
Content collections, the Zod schema, queries through getCollection(), plus adapter, runtime and CMS SDKs.
More on this
The Zod schema validates every entry during the build, so anything that no longer fits breaks the build rather than the live page. Where routes render on demand, the adapter is lifted together with the framework and tested on the target platform, never only locally. On the model see Astro CMS; a chat agent like our WhatsApp AI agent writes into that same schema.
-
Acceptance against a route inventory
Before the jump we build a list of every route. Afterwards both versions are built and compared.
More on this
We check completeness, titles, meta tags, canonical URLs, hreflang, structured data, redirects, image dimensions and how the islands hydrate. Because static HTML is what ships by default, this is a comparison of two build outputs. Then we measure in the field against the baseline, see performance optimisation.
Which Astro version are you on?
Send us the URL and, if possible, a look into the repository. You get a written version verdict.
Your version and what it means.
| Where you are | What that means | What we recommend |
|---|---|---|
| Astro 7 | The current major line, inside the support window. Minor and patch updates are routine care. | Apply updates continuously and schedule the next major cycle. |
| Astro 6 | One major behind, and the version that still receives security fixes. | Plan now. Once the next major ships, this line falls out of the window. |
| Astro 5 | Two majors behind, outside the window for security fixes. | Schedule the upgrade. Two jumps in sequence, with a build between the steps. |
| Astro 4 or older | Several majors behind. Integrations, adapter and runtime are usually dated as well. | Audit first, decision second. Upgrade and rebuild are costed against each other. |
| Version unknown | The most common case. Without a number, neither risk nor effort can be quantified. | A version verdict: two minutes in package.json, or a short look from us. |
How an Astro upgrade runs.
Version verdict
Astro version, rendering mode, adapter, integrations, collections, state of the pipeline. In writing.
Route inventory
Every route from sitemap, build output and analytics becomes the later acceptance list.
Groundwork on main
Minor updates, tidied dependencies, a reproducible build, type checking with astro check.
The jump in its own branch
One major at a time, a build in between. The branch is rebased regularly.
Switch over and measure
Regression check against the inventory, switch through the pipeline, field data against the baseline.
Common questions about the Astro upgrade.
How do we find out which Astro version we run?
A package.json sits in the root of your repository. Under the dependencies there is an astro entry, and its first number is the major version. The lock file confirms what was last installed. If nobody can reach the repository, that is the real finding.
What is the current Astro version and how long do security updates last?
The current major line is Astro 7, released in June 2026; Astro 6 went stable in March 2026. Astro follows semantic versioning and provides extended maintenance with security fixes for exactly one previous major version.
Is there a feature freeze during the upgrade?
Usually none. The upgrade runs in its own branch, your site stays online unchanged until the switch, and content and landing pages keep shipping. If you want to rework the content model in the same period, we agree an order. That costs days, never quarters.
What does an Astro upgrade cost and how long does it take?
A maintained static project one major behind takes a few days. Two majors with several integrations and a CMS connection lands at two to four weeks, three or more at four to eight. We quote after the verdict, see Astro development cost.
Will an Astro 7 migration cost us rankings?
A major upgrade is no migration: URLs, content and structure stay, the substructure changes. We still compare titles, meta tags, canonical URLs, hreflang and redirects between both builds, and watch Search Console afterwards.
Can we upgrade the Astro version ourselves and have you review it?
Yes. We supply the version verdict, the route inventory and the acceptance list, your team performs the jump, and we go through the pull request and the build comparison. Where a project has outgrown a website, we talk about custom software development.
More from the Astro cluster.
Services, migrations, comparisons and fundamentals:
The verdict first, the decision second.
Tell us where your Astro site stands: URL, hosting, repository. Answer usually within 24 hours.
Request an Astro upgrade.
Briefly describe the situation: known version, unknown version, or a project somebody else built.
We usually reply within 24 hours.
Remote and on site in Germany, Austria and Switzerland. International projects on request.
Related pages.
Astro Support & Maintenance
The retainer that prevents the catch-up: continuous updates in a fixed window.
Learn moreIT Project Management
When hosting, CMS and agency sit in different houses and somebody has to coordinate.
Learn moreWebflow Agency
The sister service, when a visual platform fits better than a repository.
Learn more