Qurno Astro Changelog

#v4.0.0 — July 2, 2026

#Astro v7 Migration

#Packages

• Upgraded astro to ^7.0.5
• Upgraded @astrojs/mdx to ^7.0.1, @astrojs/react to ^6.0.0
• Upgraded @astrojs/markdown-remark to ^7.2.0, @astrojs/rss to ^4.0.19, @astrojs/sitemap to ^3.7.3
• Upgraded tailwindcss and @tailwindcss/vite to ^4.3.2, @tailwindcss/typography to ^0.5.20
• Upgraded tinacms to ^3.9.4, @tinacms/cli to ^2.5.2
• Upgraded typescript to ^6.0.3 (tsconfig already sets ignoreDeprecations: "6.0" from the v3.0.0 migration, so this bump is warning-free)
• Upgraded astro-expressive-code to ^0.44.0, sharp to ^0.35.3, shiki to ^4.3.0, marked to ^18.0.5, @astrojs/check to ^0.9.9
• Removed the overrides.vite: ^7 pin — @tinacms/cli@2.5.2 now supports Vite 7 natively, no override needed
• Removed .nvmrc / Node engine pin added during the v3.0.0 cycle

#Fonts — moved off astro-font to Astro's native Fonts API

• Removed the astro-font dependency
• astro.config.mjs now declares Crete Round / Work Sans via a fonts: [...] array using fontProviders.google()
• Layout.astro renders <Font cssVariable="--font-primary" preload /> / <Font cssVariable="--font-secondary" preload /> (from astro:assets) instead of <AstroFont config={...} />
• styles.css moved --font-primary / --font-secondary into a separate @theme inline block so Tailwind consumes the values Astro's <Font> component sets on :root instead of redeclaring them

#Embeds — replaced astro-auto-import + astro-embed with local shortcodes

• astro-embed is unmaintained for Astro 7 (its peer range caps at astro ^6), so its fetch/parse logic is vendored locally instead of pulled in as a dependency
• Added src/libs/embed.ts — OpenGraph parsing (parse5 / @parse5/tools) plus YouTube/Vimeo ID extraction
• Added src/components/shortcodes/YouTube.astro (click-to-load, built on lite-youtube-embed), Vimeo.astro + Vimeo.css (click-to-load lite-vimeo web component), and LinkPreview.astro (OpenGraph link card)
• Removed the AutoImport integration from astro.config.mjs — Callout, AstroImage, LinkPreview, YouTube, and Vimeo are no longer globally auto-imported into every .mdx file
• Breaking for content authors: each .mdx post that uses these components must now import them explicitly at the top of the file, e.g.:
  
  

  import AstroImage from "@components/helpers/AstroImage.astro";
  import Callout from "@components/shortcodes/Callout.astro";
  import LinkPreview from "@components/shortcodes/LinkPreview.astro";
  import YouTube from "@components/shortcodes/YouTube.astro";
  import Vimeo from "@components/shortcodes/Vimeo.astro";
  

• Breaking prop change: YouTube / Vimeo now take a single id prop instead of videoid (the width / height / params props from astro-embed are gone) — e.g. <YouTube id="dsTXcSeAZq8" />, <Vimeo id="341490793" />

#Tailwind v4.3 syntax modernization (visual output unchanged)

• Important modifier: !text-3xl → text-3xl! (postfix !)
• Renamed utilities: flex-shrink-0 → shrink-0, flex-grow → grow, bg-gradient-to-r → bg-linear-to-r
• Arbitrary pixel values converted to Tailwind's fixed spacing scale where an exact match exists, e.g. h-[200px] → h-50, -mb-[95px] → -mb-23.75, py-[5px] → py-1.25
• Selector variants simplified: [&:is(.active)]: → [.active]:, [&:not(:first-child)]: → not-first:
• brightness-[115%] → brightness-115

#Fixes

• ThemeScript.astro — re-enabled OS dark/light preference detection (prefers-color-scheme), which had been left disabled
• Minor spacing consistency fixes: added ml-2 gap on category/tag count badges, header nav-toggle button padding aligned to the spacing scale (p-[6px] → p-1.5)

#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.