fix(deps): update dependency starlight-llms-txt to ^0.11.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
starlight-llms-txt (source)	^0.10.0 → ^0.11.0

---

Release Notes

delucis/starlight-llms-txt (starlight-llms-txt)

v0.11.0

Compare Source

Minor Changes

• #​127 bf986de Thanks @​funkadelic! - Updates to support Astro 7. The astro peer dependency is now ^7.0.0 and the @astrojs/starlight peer dependency is now >=0.41.0.

  Support for Astro 6 and Starlight versions below 0.41 has been dropped. Existing projects on Astro 6 can continue using the previous release until they are ready to upgrade to Astro 7.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.92%. Comparing base (bcfff77) to head (1657b04).

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #85   +/-   ##
=======================================
  Coverage   83.92%   83.92%           
=======================================
  Files         137      137           
  Lines        2954     2954           
  Branches      549      549           
=======================================
  Hits         2479     2479           
  Misses        337      337           
  Partials      138      138           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

Scope: all 61 workspace projects
.                                        | [WARN] There are cyclic workspace dependencies: /tmp/renovate/repos/github/TrigenSoftware/nano_kit/packages/nanoviews, /tmp/renovate/repos/github/TrigenSoftware/nano_kit/packages/storybook
? Verifying lockfile against supply-chain policies (1399 entries)...
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 37, reused 0, downloaded 0, added 0
Progress: resolved 44, reused 0, downloaded 0, added 0
Progress: resolved 47, reused 0, downloaded 0, added 0
Progress: resolved 54, reused 0, downloaded 0, added 0
Progress: resolved 55, reused 0, downloaded 0, added 0
Progress: resolved 58, reused 0, downloaded 0, added 0
Progress: resolved 59, reused 0, downloaded 0, added 0
Progress: resolved 72, reused 0, downloaded 0, added 0
Progress: resolved 79, reused 0, downloaded 0, added 0
Progress: resolved 82, reused 0, downloaded 0, added 0
Progress: resolved 84, reused 0, downloaded 0, added 0
Progress: resolved 85, reused 0, downloaded 0, added 0
Progress: resolved 92, reused 0, downloaded 0, added 0
Progress: resolved 99, reused 0, downloaded 0, added 0
✗ Lockfile failed supply-chain policy check (1399 entries in 21.3s)
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification:
  @trigen/oxlint-config@10.1.2 was published at 2026-07-11T13:21:39.746Z, within the minimumReleaseAge cutoff (2026-07-11T11:56:44.957Z)

The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them.