fix(deps): update all non-major dependencies by renovate[bot] · Pull Request #172 · florian-lefebvre/astro-integration-kit

renovate · 2026-03-23T01:54:12Z

This PR contains the following updates:

Package	Change	Age	Confidence
@astrojs/check (source)	`^0.9.6` → `^0.9.8`
@astrojs/starlight (source)	`^0.37.6` → `^0.38.1`
@biomejs/biome (source)	`2.4.6` → `2.4.8`
astro (source)	`^5.18.0` → `^5.18.1`
pnpm (source)	`10.30.3` → `10.32.1`

Release Notes

withastro/astro (@astrojs/check)

`v0.9.8`

Compare Source

Patch Changes

#15892 a2f597d Thanks @Princesseuh! - Fixes Astro not being able to find astro check sometimes
Updated dependencies [7b4b254]:
- @astrojs/language-server@2.16.5

`v0.9.7`

Compare Source

Patch Changes

#15187 bbb5811 Thanks @matthewp! - Update to Astro 6 beta
#15198 55107a1 Thanks @HiDeoo! - Updates to Astro 6 beta
Updated dependencies [bbb5811, df6d2d7]:
- @astrojs/language-server@2.16.1

withastro/starlight (@astrojs/starlight)

`v0.38.1`

Compare Source

Patch Changes

#3751 fb955ff Thanks @pyxelr! - Fixes a regression causing global tableOfContents config to be ignored

`v0.38.0`

Compare Source

Minor Changes

#3644 0d2e7ed Thanks @HiDeoo! - Adds support for Astro v6, drops support for Astro v5.

Upgrade Astro and dependencies

⚠️ BREAKING CHANGE: Astro v5 is no longer supported. Make sure you update Astro and any other official integrations at the same time as updating Starlight:

npx @&#8203;astrojs/upgrade

Community Starlight plugins and Astro integrations may also need to be manually updated to work with Astro v6. If you encounter any issues, please reach out to the plugin or integration author to see if it is a known issue or if an updated version is being worked on.

Update your collections

⚠️ BREAKING CHANGE: Drops support for content collections backwards compatibility.

In Astro 5.x, projects could delay upgrading to the new Content Layer API introduced for content collections because of some existing automatic backwards compatibility that was not previously behind a flag. This meant that it was possible to upgrade from Astro 4 to Astro 5 without updating your content collections, even if you had not enabled the legacy.collections flag. Projects would continue to build, and no errors or warnings would be displayed.

Astro v6.0 now removes this automatic legacy content collections support, along with the legacy.collections flag.

If you experience content collections errors after updating to v6, check your project for any removed legacy features that may need updating to the Content Layer API. See the Starlight v0.30.0 upgrade guide for detailed instructions on upgrading legacy collections to the new Content Layer API.

If you are unable to make any changes to your collections at this time, including Starlight's default docs and i18n collections, you can enable the legacy.collectionsBackwardsCompat flag to upgrade to v6 without updating your collections. This temporary flag preserves some legacy v4 content collections features, and will allow you to keep your collections in their current state until the legacy flag is no longer supported.

#3704 375edcc Thanks @florian-lefebvre! - Fixes autocomplete for components exported from @astrojs/starlight/components/*

⚠️ Potentially breaking change: This change moves some files used in Starlight’s component internals out of the components/ directory. Direct use of these files was not and is not officially supported. If you previously imported TableOfContents/starlight-toc.ts, TableOfContents/TableOfContentsList.astro, Icons.ts, or SidebarPersistState.ts, please review your code when updating.
#3729 3642625 Thanks @delucis! - Improves Starlight’s default body font stack to better support languages such as Chinese, Japanese, and Korean on Windows.
For most users there should be no visible change.

If you would prefer to keep the previous font stack, you can add the following custom CSS to your site:
```
:root {
  --sl-font-system: ui-sans-serif, system-ui, 'Segoe UI', Roboto,
    'Helvetica Neue', Arial, 'Noto Sans', sans-serif, 'Apple Color Emoji',
    'Segoe UI Emoji', 'Segoe UI Symbol', 'Noto Color Emoji';
}
```
#3598 fff38d5 Thanks @HiDeoo! - Makes hover styles consistent in Starlight’s navigation bar

Previously, the social icon links and language/theme switchers in Starlight’s navigation bar, dimmed on hover.
After this change, they now increase in contrast on hover instead.
This matches hover behavior elsewhere, for example in the sidebar, table of contents, or search button.

⚠️ Potentially breaking change: this is a subtle change to the hover style colors.
If you want to preserve the previous styling, you can add the following custom CSS to your site:
```
starlight-theme-select label,
starlight-lang-select label {
  color: var(--sl-color-gray-1);

  &:hover {
    color: var(--sl-color-white);
  }
}

.social-icons a:hover {
  color: var(--sl-color-text-accent);
  opacity: 0.66;
}
```

`v0.37.7`

Compare Source

Patch Changes

#3726 8a09b60 Thanks @delucis! - Fixes an issue using components containing scripts inside Starlight’s steps component in versions of Astro >= 5.16.9

biomejs/biome (@biomejs/biome)

`v2.4.8`

Compare Source

Patch Changes

#9488 bc709f6 Thanks @mvanhorn! - Fixed #9463: the "Biome found a configuration file outside of the current working directory" diagnostic now includes the configuration file path and the working directory, giving users actionable information to debug the issue.
#9527 2f8bf80 Thanks @mdm317! - Fixed #8959: Fixed TypeScript arrow function formatting when a comment appears after =>.
#9525 e7b3b10 Thanks @ViniciusDev26! - Added the rule noDrizzleUpdateWithoutWhere to prevent accidental full-table updates when using Drizzle ORM without a .where() clause.
#9531 1302740 Thanks @ematipico! - Fixed #9187: Astro frontmatter containing regex literals with quotes (/'/, /"/) or dashes (/---/) no longer causes parse errors.
#9535 b630d93 Thanks @leno23! - Fixed #9524: remove extra space before > when bracketSameLine is true and the self-closing slash is absent in HTML formatter.
#9537 81e6306 Thanks @ematipico! - Fixed #9238: The HTML parser no longer incorrectly reports --- inside element content (e.g. <td>---</td>) as an "Unexpected value or character" error.
#9532 4b64145 Thanks @ematipico! - Fixed #9117: biome check --write no longer falsely reports Svelte and Vue files as changed when html.formatter.indentScriptAndStyle is enabled and the files are already correctly formatted.
#9528 61451ef Thanks @ematipico! - Fixed #9341: Fixed an LSP crash that could corrupt file content when saving with format-on-save enabled.
#9538 794f79c Thanks @ematipico! - Fixed #9279: The rule noSubstr now detects .substr() and .substring() calls in all expression contexts, including variable declarations, function arguments, return statements, and arrow function bodies.
#9462 c23272c Thanks @ematipico! - Fixed #9370: The resolver now correctly prioritizes more specific exports patterns over less specific ones. Previously, a pattern like "./*" could match before "./features/*", causing resolution failures for packages with overlapping subpath patterns.
#9515 f85c069 Thanks @shivamtiwari3! - Fixed #9506 and #9479: Biome no longer reports false parse errors on <script type="speculationrules"> and <script type="application/ld+json"> tags. These script types contain non-JavaScript content and are now correctly skipped by the embedded language detector.
#9514 7fe43c8 Thanks @ematipico! - Fixed #6964: Biome now correctly resolves the .gitignore file relative to vcs.root when configured. Previously, the vcs.root setting was ignored and Biome always looked for the ignore file in the workspace directory.
#9521 af39936 Thanks @ematipico! - Fixed #9483. Now the rule noRedeclare doesn't panic when it encounters constructor overloads.
#9490 60cf024 Thanks @willfarrell! - Added support for modern CSS properties, pseudo-classes, and pseudo-elements.

New known properties: dynamic-range-limit, overlay, reading-flow, reading-order, scroll-marker-group, scroll-target-group.

New pseudo-elements: ::checkmark, ::column, ::picker, ::picker-icon, ::scroll-button, ::scroll-marker, ::scroll-marker-group.

New pseudo-classes: :active-view-transition-type, :has-slotted, :target-after, :target-before, :target-current.
#9526 4d42823 Thanks @ematipico! - Fixed #9358 and #9375. Now attributes that have text expressions such as class={buttonClass()} are correctly tracked in Svelte files.
#9520 61f53ee Thanks @ematipico! - Fixed #9519. Now noUnusedVariables doesn't flag variables that are used as typeof type.
#9487 331dc0d Thanks @mvanhorn! - Fixed #9477: source.fixAll.biome no longer sorts imports when source.organizeImports.biome is disabled in editor settings. The organize imports action is now excluded from the fix-all pass unless explicitly requested.
#9525 e7b3b10 Thanks @ViniciusDev26! - Added the rule noDrizzleDeleteWithoutWhere to prevent accidental full-table deletes when using Drizzle ORM without a .where() clause.

`v2.4.7`

Compare Source

Patch Changes

#9318 3ac98eb Thanks @ematipico! - Added new nursery lint rule useBaseline for CSS. The rule reports when CSS properties, property values, at-rules, media conditions, functions, or pseudo-selectors are not part of the configured Baseline tier.

For example, at the time of writing, the rule will trigger for the use of accent-color because it has limited availability:
```
a {
  accent-color: bar;
}
```
#9272 2de8362 Thanks @terror! - Added the nursery rule useImportsFirst that enforces all import statements appear before any non-import statements in a module. Inspired by the eslint-plugin-import import/first rule.
```
// Invalid
import { foo } from "foo";
const bar = 1;
import { baz } from "baz"; // ← flagged

// Valid
import { foo } from "foo";
import { baz } from "baz";
const bar = 1;
```
#9285 93ea495 Thanks @dyc3! - Fixed noUndeclaredVariables from erroneously flagging props only used in the template section in Vue SFCs
#9435 6c5a8f2 Thanks @siketyan! - Fixed #9432: Values referenced as a JSX element in Astro/Vue/Svelte templates are now correctly detected; noUnusedImports and useImportType rules no longer reports these values as false positives.
#9362 fc9ca4c Thanks @Netail! - Extra rule source references. biome migrate eslint should do a bit better detecting rules in your eslint configurations.
#9392 b881fea Thanks @g-ortuno! - Fixed biomejs/biome-vscode#959: LSP now correctly resolves project directory when configurationPath points to a configuration file outside the workspace.
#9420 a1c46af Thanks @ematipico! - Fixed #9385: noUselessEscapeInString no longer incorrectly flags valid CSS hex escapes (e.g. \e7bb) as useless. The rule now recognizes all hex digits (0-9, a-f, A-F) as valid escape characters in CSS strings.
#9416 f2581b8 Thanks @ematipico! - Fixed #9131, #9112, #9166: the formatter no longer crashes or produces corrupt output when a JS file with experimentalEmbeddedSnippetsEnabled contains non-embedded template literals alongside embedded ones (e.g. console.log(\test`)next tographql(`...`)`).
#9344 cb4d7d7 Thanks @ematipico! - Fixed #6921: noShadow no longer incorrectly flags destructured variable bindings in sibling scopes as shadowing. Object destructuring, array destructuring, nested patterns, and rest elements are now properly recognized as declarations.
#9360 bc5dd99 Thanks @ematipico! - Fixed #7125: The rule noShadow no longer incorrectly flags parameters in TypeScript constructor and method overload signatures.
#9371 29cac17 Thanks @ematipico! - Fixed #5279: Tabs in diagnostic diff output are now rendered at a consistent width across context and changed lines, fixing visual misalignment when source files use tab indentation.
#9043 61e2a02 Thanks @dyc3! - Fixed #8897: Biome now parses @utility names containing / when Tailwind directives are enabled.

#9354 930c858 Thanks @denbezrukov! - Improved CSS parser recovery for invalid unicode-range values that mix wildcard ranges with range intervals. For example, Biome now reports clearer diagnostics for invalid syntax like:

unicode-range: U+11???-2??;
unicode-range: U+11???-;

with diagnostics such as:

× Wildcard ranges cannot be combined with a range interval.
  > unicode-range: U+11???-2??;
                            ^

× Expected a codepoint but instead found ';'.
  > unicode-range: U+11???-;
                             ^

#9355 78e74a2 Thanks @SchahinRohani! - Fixed #9349: Biome now correctly handles Vue dynamic :alt and v-bind:alt bindings in useAltText, preventing false positives in .vue files.
#9369 b309dde Thanks @costajohnt! - Fixed #9210: useAnchorContent no longer reports an accessibility error for Astro Image components inside links when they provide non-empty alt text.
#9345 70c2d4e Thanks @ematipico! - Fixed #7214: useOptionalChain now detects optional chain patterns that don't start at the beginning of a logical AND expression. For example, bar && foo && foo.length is now correctly flagged and fixed to bar && foo?.length.
#9311 78c4e9b Thanks @ruidosujeira! - Fixed #9245: the useSemanticElements rule no longer suggests <output> for role="status" and role="alert". The <output> element is only a relatedConcept of these roles, not a direct semantic equivalent. These roles are now excluded from suggestions, aligning with the intended behavior of the upstream prefer-tag-over-role rule.
#9363 b2ffb4a Thanks @ematipico! - Fixed #5212: useSemanticElements no longer reports a diagnostic when a semantic element already has its corresponding role attribute (e.g. <nav role="navigation">, <footer role="contentinfo">). These cases are now correctly left to noRedundantRoles.
#9364 1bb9edc Thanks @xvchris! - Fixed #9357. Improved the information emitted by some diagnostics.
#9434 bf12092 Thanks @siketyan! - Fixed #9433: noBlankTarget now correctly handles dynamic href attributes, such as <a href={company?.website} target="_blank">.
#9351 5046d2b Thanks @Netail! - Expanded the noNegationElse rule to cover the inequality & strict inequality operator.
#9353 2a29e0d Thanks @Conaclos! - Fixed #7583:
organizeImports now
sorts named specifiers inside bare exports and merges bare exports.
```
- export { b, a };
- export { c };
+ export { a, b, c };
```
Also, organizeImports now correctly adds a blank line between an import chunk
and an export chunk.
```
  import { A } from "package";
+
  export { A };
```
#8658 bdcc934 Thanks @rksvc! - When the domains field is set in the configuration file, domains is now automatically enabled when Biome detects certain dependencies in package.json.
#9383 f5c8bf0 Thanks @ematipico! - Fixed #6606: The type inference engine now resolves Record<K, V> types, synthesizing them as object types with index signatures. This improves accuracy for type-aware lint rules such as noFloatingPromises, noMisusedPromises, useAwaitThenable, and useArraySortCompare when operating on Record-typed values.
#9359 701ddd3 Thanks @ematipico! - Fixed #7516: noUnusedImports no longer reports a false positive when a local variable shadows an imported type namespace that is still used in a type annotation.
#9473 50e93bd Thanks @ematipico! - Improved the detection of variables inside Astro files. Now the rule noUnusedVariables and others will trigger fewer false positives.
#9459 171b2ee Thanks @ematipico! - Fixed #9314. Now Biome doesn't panic when useAriaPropsForRole is configured using an object.
#9465 c8918d6 Thanks @Netail! - Fixed #9464: Temporal is now correctly detected as a global.
#9367 722f0da Thanks @Netail! - Added the nursery rule noTopLevelLiterals. It requires the root-level value to be an array or object.

Invalid:
```
"just a string"
```
#9333 a294b89 Thanks @terror! - Fixed #9310. Now the HTML formatter doesn't mangle elements that are followed by self-closing elements such as <br> or <img>.
#9391 4bffb66 Thanks @ematipico! - Slightly increased the performance of the CLI in projects that have more than ~2K files.
#9365 776cb64 Thanks @Netail! - Added the nursery rule noEmptyObjectKeys, which disallows the use of empty keys in JSON objects.

Invalid:
```
{
  "": "value"
}
```

withastro/astro (astro)

`v5.18.1`

Compare Source

Patch Changes

Updated dependencies [c2cd371]:
- @astrojs/internal-helpers@0.7.6
- @astrojs/markdown-remark@6.3.11

pnpm/pnpm (pnpm)

`v10.32.1`: pnpm 10.32.1

Compare Source

Patch Changes

Fix a regression where pnpm-workspace.yaml without a packages field caused all directories to be treated as workspace projects. This broke projects that use pnpm-workspace.yaml only for settings (e.g. minimumReleaseAge) without defining workspace packages #10909.

Platinum Sponsors

Gold Sponsors

`v10.32.0`: pnpm 10.32

Compare Source

Minor Changes

Added --all flag to pnpm approve-builds that approves all pending builds without interactive prompts #10136.

Patch Changes

Reverted change related to setting explicitly the npm config file path, which caused regressions.
Reverted fix related to lockfile-include-tarball-url. Fixes #10915.

Platinum Sponsors

Gold Sponsors

`v10.31.0`

Compare Source

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

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

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

netlify · 2026-03-23T01:54:26Z

❌ Deploy Preview for astro-integration-kit failed.

Name	Link
🔨 Latest commit	`c2d2ed8`
🔍 Latest deploy log	https://app.netlify.com/projects/astro-integration-kit/deploys/69c09d4885fe45000802ca4a

fix(deps): update all non-major dependencies

c2d2ed8

florian-lefebvre closed this Mar 23, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(deps): update all non-major dependencies#172

fix(deps): update all non-major dependencies#172
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all-minor-patch

renovate Bot commented Mar 23, 2026

Uh oh!

netlify Bot commented Mar 23, 2026 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

renovate Bot commented Mar 23, 2026

Release Notes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Upgrade Astro and dependencies

Update your collections

Patch Changes

Patch Changes

Patch Changes

Patch Changes

v10.32.1: pnpm 10.32.1

Patch Changes

Platinum Sponsors

Gold Sponsors

v10.32.0: pnpm 10.32

Minor Changes

Patch Changes

Platinum Sponsors

Gold Sponsors

Configuration

Uh oh!

netlify Bot commented Mar 23, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

❌ Deploy Preview for astro-integration-kit failed.

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

`v10.32.1`: pnpm 10.32.1

`v10.32.0`: pnpm 10.32

netlify Bot commented Mar 23, 2026 •

edited

Loading