[mcgroarty]

The astro group is meant to keep Astro and its first-party @astrojs/* packages upgrading together, but listing it first wasn't enough. Dependabot still put some of them in the catch-all groups:

• chore(deps): bump astro from 7.3.2 to 7.4.1 in the astro group #79 bumped astro in the astro group (as intended)
• chore(deps): bump @astrojs/starlight from 0.42.0 to 0.42.6 in the production-dependencies group #80 bumped @astrojs/starlight in production-dependencies
• chore(deps-dev): bump @astrojs/check from 0.9.10 to 0.9.11 in the dev-dependencies group #81 bumped @astrojs/check in dev-dependencies

This adds exclude-patterns for astro and @astrojs/* to the production-dependencies and dev-dependencies groups, so those packages can only land in the astro group.

After merging, Dependabot should close #80 and #81 and fold those bumps into the astro group PR on its next run.

[Copilot]

🟢 Approval recommended

The exclusions match the existing Astro group patterns and leave other update policies unchanged.

No open issues 🎉

What changed in this PR

This PR makes Dependabot’s catch-all groups exclude Astro packages, keeping updates for the documentation site’s Astro stack in the dedicated astro group.

Changes:

• Excludes astro and @astrojs/* from both production and development dependency groups.
• Adds a comment explaining the exclusions and referencing the previously split update PRs.

File	Description
.github/​dependabot.yml	Adds matching Astro exclusions to both catch-all dependency groups.

_{Review effort: Balanced}