Qurno Astro Changelog

#v3.0.0 — April 18, 2026

#Astro v6 Migration

#Dependencies

• Upgraded all dependencies to latest versions
• Downgraded typescript from ^6.0.3 to ^5.8.3 for @astrojs/check compatibility
• Added overrides to pin vite to ^7 scoped to astro only (prevents breaking @tinacms/cli which requires Vite 5)

#Content Collections (Astro v5 API Migration)

• Moved src/content/config.ts → src/content.config.ts
• Replaced type: 'content' with glob() loader for blog and author collections
• Added generateId to strip file extensions, keeping IDs compatible with old slug-based URLs
• Replaced deprecated z import from astro:content with z from zod

#Routing & Pages

• Replaced all post.slug → post.id across pages and components
• Replaced all author.slug → author.id across pages and components
• Fixed post.render() → render(post) (new Astro v5 API) in blog/[...slug].astro
• Added import { render } from "astro:content" in blog/[...slug].astro
• Added null guards ?? "" on post.body and author.body usages

#Components

• BlogCard.astro — updated post.slug → post.id, added null guard on post.body
• BlogCardTwo.astro — updated post.slug → post.id, added null guard on post.body
• Search.astro — fixed alt={post.slug} → alt={post.id} (was causing ImageMissingAlt crash)
• SearchComponent.jsx — updated post.slug → post.id for image matching and href, added null guard on post.body
• AstroImage.astro — pass alt explicitly alongside spread props to satisfy Astro v6 runtime validator

#Navigation

• Header.astro — removed || i == 0 condition that was incorrectly marking the first dropdown item as always active

#v2.0.0 — August 29, 2025

• 💥 Has breaking changes
• 💯 Upgraded Astro.js to latest v5.13.4
• ✨ Upgraded Tailwind to latest v4.1.12
• 🥎 !important: there are changes in styles; removed SCSS dependency.
• 🌍 Updated other dependencies

*Please make sure you backup your files before updating to v2

#v1.0.1 — January 19, 2025

• 🐛 Fixed TOC toggle issue after page-swap

#v1.0.0 — January 12, 2025

• 🚀 Initial Release

#Update Guide

1. Always backup your current theme before updating to a new version
2. Custom modifications warning: If you’ve made custom changes to your theme files, updating will overwrite these modifications
3. Document your custom changes
4. Compare your current theme with the new version. Use one of the following methods:
   • Use version control. GitHub is recommended for this method.
   • Use a tool like Zip Compare Tool to identify changed files
5. Using GitHub for Theme Management If you’re planning to customize your theme, consider saving it to a private GitHub repository first. This might sound technical, but it’s actually quite simple and will save you hours of headaches later.