chore(deps): bump astro-consent from 2.0.0 to 2.1.1

[dependabot]

Bumps astro-consent from 2.0.0 to 2.1.1.

Release notes

Sourced from astro-consent's releases.

v2.1.1

Fixed

• init, doctor, status, and remove no longer hardcode src/layouts/BaseLayout.astro. Layout file names aren't standardized across Astro projects, so previously the CLI silently failed to wire up (or even detect) the required stylesheet import on any project using a differently named layout (e.g. MainLayout.astro). All .astro files under src/layouts are now treated as candidates:
  • init automatically inserts import "../cookiebanner/styles.css"; into every layout file that's missing it
  • doctor reports per-file findings instead of a single pass/fail against one fixed filename
  • remove strips only the marker-tagged import it added, leaving unrelated imports untouched
• Without this fix, the consent banner would still render in the DOM but with no styling applied — no fixed positioning, no colors, no transitions — making it easy to miss entirely on real projects with non-standard layout names.

Changed

• README Quick Start now has an explicit, required step for importing src/cookiebanner/styles.css into your layout, instead of only mentioning it as an optional customization step

v2.1.0

Added

• Support for Astro 7 as a peer dependency, alongside the existing Astro 4, 5, and 6 support
• Unit test suite (via Vitest) covering the integration's hook wiring and the config-merge logic
• npm test script
• License section in the README

Changed

• Extracted the user-config merge logic in loadConfig.ts into a standalone, independently testable mergeUserConfig function
• Tightened the user-config input types so nested consent and categories overrides are properly optional instead of requiring every field

Changelog

Sourced from astro-consent's changelog.

[2.1.1] - 2026-08-25

Fixed

• init, doctor, status, and remove no longer hardcode src/layouts/BaseLayout.astro. Layout file names aren't standardized across Astro projects, so previously the CLI silently failed to wire up (or even detect) the required stylesheet import on any project using a differently named layout (e.g. MainLayout.astro). All .astro files under src/layouts are now treated as candidates:
  • init automatically inserts import "../cookiebanner/styles.css"; into every layout file that's missing it
  • doctor reports per-file findings instead of a single pass/fail against one fixed filename
  • remove strips only the marker-tagged import it added, leaving unrelated imports untouched
• Without this fix, the consent banner would still render in the DOM but with no styling applied — no fixed positioning, no colors, no transitions — making it easy to miss entirely on real projects with non-standard layout names.

Changed

• README Quick Start now has an explicit, required step for importing src/cookiebanner/styles.css into your layout, instead of only mentioning it as an optional customization step

[2.1.0] - 2026-08-25

Added

• Support for Astro 7 as a peer dependency, alongside the existing Astro 4, 5, and 6 support
• Unit test suite (via Vitest) covering the integration's hook wiring and the config-merge logic
• npm test script
• License section in the README

Changed

• Extracted the user-config merge logic in loadConfig.ts into a standalone, independently testable mergeUserConfig function
• Tightened the user-config input types so nested consent and categories overrides are properly optional instead of requiring every field

Commits

• 2ffaea5 fix: stop assuming a layout is named BaseLayout.astro
• 923b160 release 2.1.0: add Astro 7 support and a unit test suite
• See full diff in compare view