fix(deps): update all dependencies by renovate[bot] · Pull Request #178 · Enalmada/npm-module-template

renovate · 2026-03-10T09:02:37Z

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
@astrojs/check (source)	`0.9.6` → `0.9.8`
@astrojs/react (source)	`4.4.2` → `5.0.2`
@astrojs/starlight (source)	`0.37.7` → `0.38.2`
@astrojs/starlight-tailwind (source)	`4.0.2` → `5.0.0`
@biomejs/biome (source)	`2.4.6` → `2.4.10`
@scaleway/changesets-renovate (source)	`2.2.4` → `2.2.5`
@tailwindcss/postcss (source)	`4.2.1` → `4.2.2`
@tailwindcss/vite (source)	`4.2.1` → `4.2.2`
@types/node (source)	`25.3.5` → `25.5.2`
astro (source)	`5.18.0` → `6.1.3`
lefthook	`2.1.2` → `2.1.5`
tailwindcss (source)	`4.2.1` → `4.2.2`
turbo (source)	`2.8.14` → `2.9.4`
typescript (source)	`5.9.3` → `6.0.2`
vitest (source)	`4.0.18` → `4.1.2`

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/astro (@astrojs/react)

`v5.0.2`

Compare Source

Patch Changes

#15378 a8a926e Thanks @dmgawel! - Fix React hydration errors when using conditional slot rendering
#15146 f771f75 Thanks @kedarvartak! - Fixes hydration mismatch when using experimentalReactChildren
#14917 769265b Thanks @sanjaiyan-dev! - Refactors to improve the performance of rendering static HTML content in React

`v5.0.1`

Compare Source

Patch Changes

#15864 d3c7de9 Thanks @florian-lefebvre! - Removes temporary support for Node >=20.19.1 because Stackblitz now uses Node 22 by default

`v5.0.0`

Compare Source

Major Changes

#14427 e131261 Thanks @florian-lefebvre! - Increases minimum Node.js version to 22.12.0 - (v6 upgrade guidance)
#14445 ecb0b98 Thanks @florian-lefebvre! - Astro v6.0 upgrades to Vite v7.0 as the development server and production bundler - (v6 upgrade guidance)

Minor Changes

#15312 72f7960 Thanks @ocavue! - Update @vitejs/plugin-react to v5.

Patch Changes

#15187 bbb5811 Thanks @matthewp! - Update to Astro 6 beta
#15264 11efb05 Thanks @florian-lefebvre! - Lower the Node version requirement to allow running on Stackblitz until it supports v22
#15700 4e7f3e8 Thanks @ocavue! - Improves how React components are identified when setting the include and/or exclude options in projects where multiple JSX frameworks are used together
Updated dependencies [4ebc1e3, 4e7f3e8, a164c77, cf6ea6b, a18d727, 240c317, 745e632]:
- @astrojs/internal-helpers@0.8.0

withastro/starlight (@astrojs/starlight)

`v0.38.2`

Compare Source

Patch Changes

#3759 f24ce99 Thanks @MilesChou! - Fixes an issue where monolingual sites using a region-specific locale (e.g., zh-TW) as the default would incorrectly display base language translations (e.g., zh Simplified Chinese) instead of the region-specific ones (e.g., zh-TW Traditional Chinese).
#3768 a4c6c20 Thanks @delucis! - Improves performance of sidebar generation for sites with very large sidebars

`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;
}
```

withastro/starlight (@astrojs/starlight-tailwind)

`v5.0.0`

Compare Source

Major Changes

#3644 0d2e7ed Thanks @HiDeoo! - ⚠️ BREAKING CHANGE: The minimum supported version of Starlight is now 0.38.0

Please use the @astrojs/upgrade command to upgrade your project:
```
npx @&#8203;astrojs/upgrade
```

biomejs/biome (@biomejs/biome)

`v2.4.10`

Compare Source

Patch Changes

#8838 f3a6a6b Thanks @baeseokjae! - Added new lint nursery rule noImpliedEval.

The rule detects implied eval() usage through functions like setTimeout, setInterval, and setImmediate when called with string arguments.
```
// Invalid
setTimeout("alert('Hello');", 100);

// Valid
setTimeout(() => alert("Hello"), 100);
```
#9320 93c3b6c Thanks @taberoajorge! - Fixed #7664: noUnusedVariables no longer reports false positives for TypeScript namespace declarations that participate in declaration merging with an exported or used value declaration (const, function, or class) of the same name. The reverse direction is also handled: a value declaration merged with an exported namespace is no longer flagged.
#9630 1dd4a56 Thanks @raashish1601! - Fixed #9629: noNegationElse now keeps ternary branch comments attached to the correct branch when applying its fixer.
#9216 04243b0 Thanks @FrederickStempfle! - Fixed #9061: noProcessEnv now also detects process.env when process is imported from the "process" or "node:process" modules.

Previously, only the global process object was flagged:
```
import process from "node:process";
// This was not flagged, but now it is:
console.log(process.env.NODE_ENV);
```
#9692 61b7ec5 Thanks @mkosei! - Fixed Svelte #each destructuring parsing and formatting for nested patterns such as [key, { a, b }].
#9627 06a0f35 Thanks @ematipico! - Fixed #191: Improved the performance of how the Biome Language Server pulls code actions and diagnostics.

Before, code actions were pulled and computed all at once in one request. This approach couldn't work in big files, and caused Biome to stale and have CPU usage spikes up to 100%.

Now, code actions are pulled and computed lazily, and Biome won't choke anymore in big files.
#9643 5bfee36 Thanks @dyc3! - Fixed #9347: useVueValidVBind no longer reports valid object bindings like v-bind="props".
#9627 06a0f35 Thanks @ematipico! - Fixed assist diagnostics being invisible when using --diagnostic-level=error. Enforced assist violations (e.g. useSortedKeys) were filtered out before being promoted to errors, causing biome check to incorrectly return success.
#9695 9856a87 Thanks @dyc3! - Added the new nursery rule noUnsafePlusOperands, which reports + and += operations that use object-like, symbol, unknown, or never operands, or that mix number with bigint.
#9627 06a0f35 Thanks @ematipico! - Fixed duplicate parse errors in check and ci output. When a file had syntax errors, the same parse error was printed twice and the error count was inflated.
#9627 06a0f35 Thanks @ematipico! - Improved the performance of the commands lint and check when they are called with --write.
#9627 06a0f35 Thanks @ematipico! - Fixed --diagnostic-level not fully filtering diagnostics. Setting --diagnostic-level=error now correctly excludes warnings and infos from both the output and the summary counts.
#9623 13b3261 Thanks @ematipico! - Fixed #9258: --skip no longer causes suppressions/unused warnings for suppression comments targeting skipped rules or domains.
#9631 599dd04 Thanks @raashish1601! - Fixed #9625: experimentalEmbeddedSnippetsEnabled no longer crashes when a file mixes formatable CSS-in-JS templates with tagged templates that the embedded formatter can't currently delegate, such as a styled-components interpolation returning `css```.

`v2.4.9`

Compare Source

Patch Changes

#9315 085d324 Thanks @ematipico! - Added a new nursery CSS rule noDuplicateSelectors, that disallows duplicate selector lists within the same at-rule context.

For example, the following snippet triggers the rule because the second selector and the first selector are the same:
```
/* First selector */
.x .y .z {
}

/* Second selector */
.x {
  .y {
    .z {
    }
  }
}
```
#9567 b7ab931 Thanks @ematipico! - Fixed #7211: useOptionalChain now detects negated logical OR chains. The following code is now considered invalid:
```
!foo || !foo.bar;
```
#8670 607ebf9 Thanks @tt-a1i! - Fixed #8345: useAdjacentOverloadSignatures no longer reports false positives for static and instance methods with the same name. Static methods and instance methods are now treated as separate overload groups.
```
class Kek {
  static kek(): number {
    return 0;
  }
  another(): string {
    return "";
  }
  kek(): number {
    return 1;
  } // no longer reported as non-adjacent
}
```
#9476 97b80a8 Thanks @masterkain! - Fixed #9475: Fixed a panic when Biome analyzed ambient TypeScript modules containing class constructor, getter, or setter signatures that reference local type aliases. Biome now handles these declarations without crashing during semantic analysis.
#9553 0cd5298 Thanks @dyc3! - Fixed a bug where enabling the rules of a whole group, would enable rules that belonged to a domain under the same group.

For example, linter.rules.correctness = "error" no longer enables React- or Qwik-specific correctness rules unless linter.domains.react, linter.domains.qwik, or an explicit rule config also enables them, or their relative dependencies are installed.
#9586 4cafb71 Thanks @dyc3! - Fixed #8828: Grit patterns using export { $foo } from $source now match named re-exports in JavaScript and TypeScript files.
#9550 d4e3d6e Thanks @dyc3! - Fixed #9548: Biome now parses conditional expressions whose consequent is an arrow function returning a parenthesized object expression.
#8696 a7c19cc Thanks @Faizanq! - Fixed #8685 where noUselessLoneBlockStatements would remove empty blocks containing comments. The rule now preserves these blocks since comments may contain important information like TODOs or commented-out code.
#9557 6671ac5 Thanks @datalek! - Fixed #9557: Biome's LSP server no longer crashes on startup when used with editors that don't send workspaceFolders during initialization. This affected any LSP client that only sends rootUri, which is valid per the LSP specification.
#9455 1710cf1 Thanks @omar-y-abdi! - Fixed #9174: useExpect now correctly rejects asymmetric matchers in Vitest or Jest like expect.stringContaining(), expect.objectContaining(), and utilities like expect.extend() that are not valid assertions. Previously these constructs caused false negatives, allowing tests without real assertions to pass the lint rule.
#9584 956e367 Thanks @ematipico! - Fixed a bug where Vue directive attribute values like v-bind:class="{'dynamic': true}" were incorrectly parsed as JavaScript statements instead of expressions. Object literals inside directive values like :class, v-if, and v-html are now correctly parsed as expressions, preventing spurious parse errors.
#9474 e168494 Thanks @ematipico! - Added the new nursery rule noUntrustedLicenses. This rule disallows dependencies that ship with invalid licenses or licenses that don't meet the criteria of your project/organisation.

The rule has the following options:
- allow: a list of licenses that can be allowed. Useful to bypass possible invalid licenses from downstream dependencies.
- deny: a list of licenses that should trigger the rule. Useful to deny licenses that don't fit your project/organisation.
  When both deny and allow are provided, deny takes precedence.
- requireOsiApproved: whether the licenses need to be approved by the Open Source Initiative.
- requireFsfLibre: whether the licenses need to be approved by the Free Software Foundation.
#9544 723798b Thanks @ViniciusDev26! - Added an unsafe fix to useConsistentMethodSignatures that automatically converts between method-style and property-style signatures.
#9555 8a3647b Thanks @ematipico! - Fixed #188: the Biome Language Server no longer panics when open files change abruptly, such as during git branch checkouts.
#9605 f65c637 Thanks @ematipico! - Fixed #9589. Now Biome correctly parses object expressions inside props and directives. The following code doesn't emit errors anymore:
```
<style is:global define:vars={{ bgLight: light }}>
<Component name={{ first, name }} />
```
#9565 ccb249e Thanks @eyupcanakman! - Fixed #9505: noUselessStringConcat no longer reports tagged template literals as useless string concatenations. Tagged templates invoke a function and can return non-string values, so combining them with + is not equivalent to a single template literal.
#9534 4d050df Thanks @Netail! - Added the nursery rule noInlineStyles. The rule disallows the use of inline style attributes in HTML and the style prop in JSX, including React.createElement calls. Inline styles make code harder to maintain and can interfere with Content Security Policy.
#9611 cddaa44 Thanks @gaauwe! - Fixed a regression where Biome LSP could misread editor settings sent through workspace/didChangeConfiguration when the payload was wrapped in a top-level biome key. This caused requireConfiguration and related settings to be ignored in some editors.

`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 Tha

Configuration

📅 Schedule: (UTC)

Branch creation
- At any time (no schedule defined)
Automerge
- Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)

🚦 Automerge: Enabled.

♻ 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.

vercel · 2026-03-10T09:02:39Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
npm-module-template	Error		Apr 9, 2026 11:03am

changeset-bot · 2026-03-10T09:02:49Z

🦋 Changeset detected

Latest commit: 1ec2c05

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

renovate bot enabled auto-merge (squash) March 10, 2026 09:02

vercel bot deployed to Preview March 10, 2026 09:03 View deployment

renovate bot force-pushed the renovate/all branch from e59d82b to bc3ecaf Compare March 12, 2026 22:12

renovate bot changed the title ~~chore(deps): update dependency lefthook to v2.1.3~~ chore(deps): update all dependencies Mar 12, 2026

vercel bot deployed to Preview March 12, 2026 22:13 View deployment

renovate bot force-pushed the renovate/all branch from a9659fe to 63796ba Compare March 13, 2026 15:46

renovate bot changed the title ~~chore(deps): update all dependencies~~ fix(deps): update all dependencies Mar 13, 2026

vercel bot had a problem deploying to Preview March 13, 2026 15:47 Failure

renovate bot force-pushed the renovate/all branch from bf9195f to e59c943 Compare March 13, 2026 20:36

vercel bot had a problem deploying to Preview March 13, 2026 20:36 Failure

auto-merge was automatically disabled March 13, 2026 20:37
Head branch was modified

vercel bot had a problem deploying to Preview March 13, 2026 20:37 Failure

renovate bot enabled auto-merge (squash) March 14, 2026 05:03

renovate bot force-pushed the renovate/all branch from 4a2c729 to 328d455 Compare March 14, 2026 05:03

vercel bot had a problem deploying to Preview March 14, 2026 05:04 Failure

renovate bot force-pushed the renovate/all branch from 63bf377 to de40d55 Compare March 15, 2026 01:02

vercel bot had a problem deploying to Preview March 15, 2026 01:02 Failure

renovate bot force-pushed the renovate/all branch from 711168c to 18b91c9 Compare March 15, 2026 09:35

vercel bot had a problem deploying to Preview March 15, 2026 09:35 Failure

renovate bot force-pushed the renovate/all branch from 1779dbf to 60477e8 Compare March 15, 2026 17:19

vercel bot had a problem deploying to Preview March 15, 2026 17:20 Failure

renovate bot force-pushed the renovate/all branch from feb4451 to 7fd226f Compare March 16, 2026 18:47

vercel bot had a problem deploying to Preview March 16, 2026 18:47 Failure

vercel bot had a problem deploying to Preview March 16, 2026 18:48 Failure

renovate bot force-pushed the renovate/all branch from 7ce7f84 to a5ef38e Compare March 23, 2026 18:36

vercel bot had a problem deploying to Preview March 23, 2026 18:37 Failure

renovate bot force-pushed the renovate/all branch from d1cc91e to 5f6469f Compare March 26, 2026 17:56

vercel bot had a problem deploying to Preview March 26, 2026 17:57 Failure

renovate bot force-pushed the renovate/all branch from 1facd78 to 2e7f791 Compare March 28, 2026 13:16

vercel bot had a problem deploying to Preview March 28, 2026 13:17 Failure

renovate bot force-pushed the renovate/all branch from d151f15 to a463b6a Compare March 29, 2026 16:59

vercel bot had a problem deploying to Preview March 29, 2026 16:59 Failure

renovate bot force-pushed the renovate/all branch from 235a4a5 to 4eb3d62 Compare March 29, 2026 20:47

vercel bot had a problem deploying to Preview March 29, 2026 20:47 Failure

vercel bot had a problem deploying to Preview March 29, 2026 20:48 Failure

renovate bot force-pushed the renovate/all branch from 7b78381 to f163cc8 Compare March 31, 2026 13:35

vercel bot had a problem deploying to Preview March 31, 2026 13:36 Failure

renovate bot force-pushed the renovate/all branch from 4a9b02c to ab4b9bb Compare April 2, 2026 18:16

vercel bot had a problem deploying to Preview April 2, 2026 18:16 Failure

renovate bot force-pushed the renovate/all branch from 255104a to fd93dfb Compare April 2, 2026 21:49

vercel bot had a problem deploying to Preview April 2, 2026 21:50 Failure

renovate bot force-pushed the renovate/all branch from 9f860c9 to 01dbdaf Compare April 3, 2026 21:27

vercel bot had a problem deploying to Preview April 3, 2026 21:27 Failure

vercel bot had a problem deploying to Preview April 3, 2026 21:28 Failure

renovate bot force-pushed the renovate/all branch from 74cfafb to 7f4475a Compare April 4, 2026 01:16

vercel bot had a problem deploying to Preview April 4, 2026 01:16 Failure

vercel bot had a problem deploying to Preview April 4, 2026 01:17 Failure

renovate bot force-pushed the renovate/all branch from 96dbc1a to 6f67839 Compare April 4, 2026 21:44

renovate bot added 2 commits April 9, 2026 11:02

fix(deps): update all dependencies

c3ecb87

chore: add .changeset/renovate-c3ecb87.md

1ec2c05

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix(deps): update all dependencies#178

fix(deps): update all dependencies#178
renovate[bot] wants to merge 2 commits intomainfrom
renovate/all

renovate bot commented Mar 10, 2026 •

edited

Loading

Uh oh!

vercel bot commented Mar 10, 2026 •

edited

Loading

Uh oh!

changeset-bot bot commented Mar 10, 2026 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

renovate bot commented Mar 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Major Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Upgrade Astro and dependencies

Update your collections

Major Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Configuration

Uh oh!

vercel bot commented Mar 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

changeset-bot bot commented Mar 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🦋 Changeset detected

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

renovate bot commented Mar 10, 2026 •

edited

Loading

vercel bot commented Mar 10, 2026 •

edited

Loading

changeset-bot bot commented Mar 10, 2026 •

edited

Loading