Aver Astro Changelog

#v2.0.0 — Apr 19, 2026

#Astro v6 Migration

#Packages

• Upgraded astro to ^6.1.8
• Upgraded @astrojs/mdx to ^5.0.3
• Upgraded @astrojs/react to ^5.0.3
• Upgraded @astrojs/markdown-remark to ^7.1.0
• Upgraded typescript to ^6.0.3
• Upgraded react / react-dom to ^19.2.5
• Upgraded marked to ^18.0.2
• Upgraded swiper to ^12.1.3

#Content Collections

• Moved content config from src/content/config.ts → src/content.config.ts (required by Astro v6)
• Replaced type: 'content' with loader: glob(...) for blog and project collections

#Breaking Change Fixes

• Replaced entry.render() → render(entry) (imported from astro:content) in blog and project slug pages
• Replaced entry.slug → entry.id across all collection pages (v6 glob loader uses id)
• Strip file extension from entry.id when used as URL slug (e.g. curoloy.mdx → curoloy)

#Utilities

• Added entrySlug(id: string) helper to src/lib/utils/textConverter.ts to strip file extensions from collection entry IDs
• Replaced all inline .replace(/\.[^.]+$/, '') calls with entrySlug() across 7 pages

#v1.1.1 — Aug 19, 2025

• Updated Product view layout in mobile, for better mobile experience
• Upgraded Astro.js to latest + updated dependencies

#v1.0.1 — Aug 14, 2025

• 🐛 Fixed banner overflow issue on mobile

#v1.0.0 — July 21, 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.