Update minimum supported Astro version to 5.1

[delucis]

Description

• Updates our development versions of Astro to 5.1.1
• Updates the minimum supported of Astro to 5.1.0
• This bump is needed for both Fixes code example colour contrast #2708 and feat: Adds print styles for Starlight docs pages #157

[changeset-bot]

🦋 Changeset detected

Latest commit: 6b54a4a

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@astrojs/starlight	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[netlify]

✅ Deploy Preview for astro-starlight ready!

Name	Link
🔨 Latest commit	6b54a4a
🔍 Latest deploy log	https://app.netlify.com/sites/astro-starlight/deploys/67818ff337bfa90008511997
😎 Deploy Preview	https://deploy-preview-2736--astro-starlight.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 100 (no change from production) Accessibility: 100 (no change from production) Best Practices: 100 (no change from production) SEO: 100 (no change from production) PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[astrobot-houston]

size-limit report 📦

Path	Size
/index.html	6.89 KB (-1.54% 🔽)
/_astro/*.js	21.19 KB (0%)
/_astro/*.css	13.75 KB (0%)

[HiDeoo]

Small note that the dev version can not be updated until withastro/astro#12652 is fixed.

[delucis]

Small note that the dev version can not be updated until withastro/astro#12652 is fixed.

Ohhhh, you even said that already in #2612 (comment)

Damn, that makes this really tricky. We can’t really have a dev version lower than our minimum supported version I don’t think?

[lilnasy]

Small note that the dev version can not be updated until withastro/astro#12652 is fixed.

It can if you manually set process.env.NODE_ENV to development before running the failing test. It corrects astro's wrong guess that the environment is production, and it correctly looks for the development data store instead of the production one.

[ascorbic]

This is what we do in the Astro tests:

https://github.com/withastro/astro/blob/ce842c9b7e27b8ab1c5d43bafd1a64a7bfa29194/packages/astro/test/test-utils.js#L180

[lilnasy]

This is what we do in the Astro tests:

The default of data store retrieval is to assume production, so wouldn't implementing the linked workaround this arrive at the same failure?

I imagine the variable would need to be definitely set to development, not just deleted, which is what worked for me.

[delucis]

I imagine the variable would need to be definitely set to development, not just deleted, which is what worked for me.

Not sure exactly why, but it does look like deleting it fixes our E2E tests in this context.

[lilnasy]

Right, of course, vite sets it to development if its not already defined, same as it does normally when invoked rom the cli.

[ascorbic]

I have a PR which should fix this. It's doing a preview build if you'd like to check.

[ascorbic]

Install astro@experimental--data-store-location

[delucis]

Thanks @ascorbic! The experimental release does seem to fix things. You can see end-to-end tests running successfully in a branch off this PR here: #2776