feat: update flag naming

[ematipico]

Description (required)

This PR updates experimentalStaticHeaders to staticHeaders.

The docs already use a very broad explanation, so it's there's no need to update their explanation.

For Astro version: 6.0. See astro PR #15258.

[netlify]

✅ Deploy Preview for astro-docs-2 ready!

Name	Link
🔨 Latest commit	bcb0296
🔍 Latest deploy log	https://app.netlify.com/projects/astro-docs-2/deploys/6983688b4e0b370008e23a6b
😎 Deploy Preview	https://deploy-preview-13159--astro-docs-2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

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

[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

File	Note
en/guides/integrations-guide/netlify.mdx	Source changed, localizations will be marked as outdated.
en/guides/integrations-guide/node.mdx	Source changed, localizations will be marked as outdated.
en/guides/integrations-guide/vercel.mdx	Source changed, localizations will be marked as outdated.
en/reference/adapter-reference.mdx	Source changed, localizations will be marked as outdated.
en/reference/integrations-reference.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.

[sarah11918]

@ematipico - If you look at the bottom of the "Files changed" view, you can see that there are two pages with an anchor link to a section heading you've changed. This is why the link check has failed.

(If you look at the results of the link check, it will tell you there are 11 problems, but 10 of them are caused because they are creating pages using the content of the English page with the broken link; the Korean page is the only one that separately needs manually updating)

Can you please update those anchor links to match the new heading, and then I think all the tests should pass!

[ArmandPhilippot]

the Korean page is the only one that separately needs manually updating

👀
This means that some replacements are missing for adapter-reference. The Korean version isn't the only one to include experimentalStaticHeaders. There's also at least the French version 😄 and the Chinese version.

The failing links come from SSRManifest.csp.cspDestination (and the translations)

[ematipico]

@sarah11918 @ArmandPhilippot Should I just revert the changes and limit myself to the english version?

[ArmandPhilippot]

If you don't want to waste time struggling with links, this is probably easier, yes. 😄

In any case, the Adapter and Integrations references will require an update to the translations. So, I don't think it's an issue to keep experimentalStaticHeaders in the meantime!

[ematipico]

@sarah11918 @ArmandPhilippot Discovered more changes, and addressed the link failures

[ArmandPhilippot]

Thanks, Ema! Unfortunately with the new changes you discovered, we'll need more changes. 😅 I think it's fine if you only apply that to the English version:

• on @astrojs/netlify, because staticHeaders is no longer experimental, I think we can remove the "Experimental features" section and move staticHeaders in "Usage".
• same for @astrojs/vercel
• on @astrojs/node, this is rather a nit, I guess we should keep the experimental flags grouped, so we might want to move staticHeaders above experimentalDisableStreaming.

I also suggested to bump the version in each <Since /> component. I'm not sure we have something about that in AD², but we usually use the stable version rather than the experimental one.

[ematipico]

Ok, let me revert the changes to only target english. Then I will apply your suggestions

[ematipico]

@ArmandPhilippot I force pushed, now the changes only affect the english version. So, here's the thing though: for vercel and netlify, there aren't experimental features anymore. Should I remove the paragraph?

[ArmandPhilippot]

@ematipico Yes, I think it would make sense because these sections are now empty!

[sarah11918]

Just comments re: whether we still need the experimental section and to check carefully version numbers!

[ematipico]

@ArmandPhilippot and @sarah11918 please review again

[ArmandPhilippot]

Thanks for the update Ema!
I think we're almost there! There is an issue with a code snippet in @astrojs/node and, in @astrojs/vercel, the section should be moved under "Configuration". After that, this looks pretty good to me!

[sarah11918]

As far as I can tell, Armand caught everything! Should be the only changes still needed!

[yanthomasdev]

LGTM!

[ematipico]

Let me know when this PR is ready for merging, so I can merge the code feature

[ArmandPhilippot]

LGTM, thanks Ema! And sorry my suggestion wasted time...

[ematipico]

Thank you. I just merged the code pr

[sarah11918]

Great! This PR is ready to merge when the feature is released! 🎉