Updating packages

[aaronpowell]

Pull Request Checklist

• I have read and followed the CONTRIBUTING.md guidelines.
• I have read and followed the Guidance for submissions involving paid services.
• My contribution adds a new instruction, prompt, agent, skill, or workflow file in the correct directory.
• The file follows the required naming convention.
• The content is clearly structured and follows the example format.
• I have tested my instructions, prompt, agent, skill, or workflow with GitHub Copilot.
• I have run npm start and verified that README.md is up to date.
• I am targeting the staged branch for this pull request.

---

Description

---

Type of Contribution

• New instruction file.
• New prompt file.
• New agent file.
• New plugin.
• New skill file.
• New agentic workflow.
• Update to existing instruction, prompt, agent, plugin, skill, or workflow.
• Other (please specify):

---

Additional Notes

---

By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.

[Copilot]

Pull request overview

Updates the website’s npm dependencies to newer versions (notably Astro, Starlight, Marked, and Shiki) and refreshes the lockfile accordingly.

Changes:

• Bump astro, @astrojs/starlight, @astrojs/sitemap, marked, and shiki versions in website/package.json.
• Regenerate website/package-lock.json to capture updated transitive dependencies and engine constraints.

Show a summary per file

File	Description
website/package.json	Updates direct website dependencies to newer versions.
website/package-lock.json	Updates resolved dependency graph, including new Node engine requirements introduced by upgrades.

Copilot's findings

• Files reviewed: 1/2 changed files
• Comments generated: 2

[Copilot]

Upgrading to Astro 6.x raises the minimum supported Node.js version (the lockfile shows astro@6.1.9 requires node >=22.12.0). Our CI workflows for the website currently use Node 20 (e.g., .github/workflows/build-website.yml and deploy-website.yml), so builds/installations will fail unless the repo’s Node version is bumped accordingly (and ideally reflected via an engines.node field). If the repo must stay on Node 20, astro should remain on a compatible major version instead.

[Copilot]

The updated lockfile records astro@6.1.9 with engines.node >=22.12.0. This will conflict with the repo’s current GitHub Actions website workflows that install/build with Node 20, causing CI failures unless the workflows (and any documented/tooling Node version) are updated to >=22.12.0.