Changelog

Every theme ships with a CHANGELOG.md in its root. That file is the source of truth for what changed between versions.

Per-theme changelog

Open CHANGELOG.md in your theme. It follows the Keep a Changelog convention:

CHANGELOG.md (excerpt)

# Changelog

## [1.2.0] — 2026-04-15

### Added
- ResourceHub component for non-blog resource indexes
- Forge: acid-lime accent block utility for inverted sections

### Changed
- Contact and Newsletter forms now wire to siteConfig providers automatically
- Updated all themes to Astro 5.18

### Fixed
- Gallery section was rendering placeholder backgrounds instead of images

How to get a new version

1. Re-download the latest zip from your Gumroad library at gumroad.com/library, or from the original receipt email.
2. Compare the new CHANGELOG.md against your current version. Note the additions, changes, and any “breaking” warnings.
3. Pick an upgrade strategy — see below.

Upgrade strategy A: targeted updates

Best for sites that are already in production with custom edits.

1. Unzip the new version next to your project (e.g. ~/projects/aurora-new/).
2. Use a diff tool (git diff, VS Code’s “Compare Folders” extension, Beyond Compare) to compare the new version against your edited copy.
3. Cherry-pick the changes you want — bug fixes, new sections, the new utility class — into your existing project.
4. Leave your custom edits alone.

This is the safest path. The cost is more manual work; the benefit is no risk of losing your customizations.

Upgrade strategy B: replace + reapply

Best for sites with minimal customization or sites you’re early in building.

1. Move your current src/config/site.ts, src/styles/global.css (if you edited it), src/content/blog/ (your posts), and public/ (your assets) somewhere safe.
2. Replace the whole project folder with the new version.
3. Restore your config, styles, blog posts, and public assets.
4. Run npm install && npm run dev and verify.

Faster, but only safe if you know you haven’t edited any components, layouts, or pages.

Versioning

We follow semantic versioning loosely:

• Major (1.x.x → 2.x.x) — breaking changes to the config shape, the section API, or required dependencies (e.g. Astro 5 → 6).
• Minor (1.0.x → 1.1.x) — new sections, new utilities, new features. Backwards-compatible.
• Patch (1.0.0 → 1.0.1) — bug fixes, copy edits, performance tweaks.

Breaking changes are always called out at the top of the changelog entry. We try hard to avoid them — when they happen, we include a migration note.

Bundle changelog (lifetime customers)

If you bought the lifetime bundle, you also get a separate bundle changelog that lists when new themes were added to the bundle. Check the Gumroad product page for the latest list.

When we ship a new theme:

1. It gets added to your Gumroad library automatically.
2. You receive a Gumroad “new content available” email.
3. The bundle changelog updates with the addition.

What’s next

• License — how lifetime updates are licensed.
• Support — how to ask about a specific changelog entry.