feat: enable Content Collection Caching

[Princesseuh]

Description (required)

Maybe I could've tried this before, sorry for the time loss.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
docs	✅ Ready (Inspect)	Visit Preview	Apr 18, 2024 6:19pm

1 Ignored Deployment

Name	Status	Preview	Updated (UTC)
docs-i18n	⬜️ Ignored (Inspect)		Apr 18, 2024 6:19pm

[astrobot-houston]

Lunaria Status Overview

🌕 This pull request will trigger status changes.

Learn more

By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.

You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale	File	Note
en	recipes/build-forms.mdx	Source changed, localizations will be marked as outdated.

Warnings reference

Icon	Description
🔄️	The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

[delucis]

Adding a quick note that I’m not 100% confident we can rely on Vercel to test the cache hit in this case — tried rerunning the deploy there a few times with build cache enabled, but it always logs:

Cache invalid, rebuilding from source. Reason: The cache manifest version has changed.

I think this is because Vercel only caches node_modules from main not from deploy branches so the lock file has always changed on branch deploy? Not sure, but just a heads up.

[matthewp]

@delucis that's what I was going to test today, thanks!

[matthewp]

I think in this case a code issue is causing it to continuously be invalidated. I'm working on a fix while writing tests.