chore: remove npm override for @ascorbic/loader-utils when upstream adds astro 7+ support #26

Summary

PR #24 added an npm overrides block in package.json to resolve a transitive peer dependency conflict:

"overrides": {
  "@ascorbic/loader-utils": {
    "astro": "$astro"
  }
}

starlight-changelogs@0.5.0 depends on @ascorbic/loader-utils@^1.0.2, which declares peerDependencies: { astro: "^4.14.0 || ^5.0.0-beta.0" } — it does not support astro 6 or 7. The override forces the transitive dependency to use the workspace's own astro version.

Current Status (2026-07-05)

The project migrated from Astro 6 to Astro 7 in PR #205. The override remains necessary:

• @ascorbic/loader-utils@1.0.2 (latest) still declares peerDependencies: { astro: "^4.14.0 || ^5.0.0-beta.0" }
• starlight-changelogs@0.5.0 still depends on @ascorbic/loader-utils
• The $astro override pattern forces it to accept astro 7.0.6 — the build succeeds

Acceptance Criteria

• When @ascorbic/loader-utils updates its peerDependencies to include astro@7 (or starlight-changelogs drops the dependency), remove the overrides block from package.json
• Verify npm ci && npm run build still succeeds without the override

How to Check

Periodically run npm info @ascorbic/loader-utils peerDependencies and check if the astro range includes ^7.0.0, or watch for a new release of starlight-changelogs that resolves the conflict.