fix(deps): update all dependencies#178
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
e59d82b to
bc3ecaf
Compare
a9659fe to
63796ba
Compare
bf9195f to
e59c943
Compare
auto-merge was automatically disabled
March 13, 2026 20:37
Head branch was modified
4a2c729 to
328d455
Compare
63bf377 to
de40d55
Compare
711168c to
18b91c9
Compare
1779dbf to
60477e8
Compare
feb4451 to
7fd226f
Compare
7ce7f84 to
a5ef38e
Compare
d1cc91e to
5f6469f
Compare
1facd78 to
2e7f791
Compare
d151f15 to
a463b6a
Compare
235a4a5 to
4eb3d62
Compare
7b78381 to
f163cc8
Compare
4a9b02c to
ab4b9bb
Compare
255104a to
fd93dfb
Compare
9f860c9 to
01dbdaf
Compare
74cfafb to
7f4475a
Compare
96dbc1a to
6f67839
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.9.6→0.9.94.4.2→6.0.10.37.7→0.41.20.41.34.0.2→5.0.02.4.6→2.5.22.30.0→2.31.02.2.4→3.0.34.2.1→4.3.24.2.1→4.3.225.3.5→26.1.019.2.14→19.2.17v6→v75.18.0→7.0.62.1.2→2.1.90.3.18→0.3.2119.2.4→19.2.719.2.4→19.2.70.34.5→0.35.34.2.1→4.3.22.8.14→2.10.22.10.35.9.3→6.0.35.9.3→6.0.34.0.18→4.1.9Release Notes
withastro/astro (@astrojs/check)
v0.9.9Compare Source
Patch Changes
#16471
f56bb3fThanks @delucis! - Adds support for TypeScript v6 to peer dependencies rangeUpdated dependencies [
8c62159]:v0.9.8Compare Source
Patch Changes
#15892
a2f597dThanks @Princesseuh! - Fixes Astro not being able to find astro check sometimesUpdated dependencies [
7b4b254]:v0.9.7Compare Source
Patch Changes
#15187
bbb5811Thanks @matthewp! - Update to Astro 6 beta#15198
55107a1Thanks @HiDeoo! - Updates to Astro 6 betaUpdated dependencies [
bbb5811,df6d2d7]:withastro/astro (@astrojs/react)
v6.0.1Compare Source
Patch Changes
eb6f97e]:v6.0.0Compare Source
Major Changes
cafec4eThanks @delucis! - Upgrade to Vite v8Minor Changes
#17093
4585fe5Thanks @Princesseuh! - Replaces the import entrypoint ofgetContainerRenderer()A new
container-rendererentrypoint exportinggetContainerRenderer()has been added to the following integrations: React, Preact, Svelte, SolidJS, Vue, and MDX. This prevents bundlers from trying to bundle unrelated exports from the package root when only the Container API is used.If you are using the Container API, update your import statements to use the new entrypoint. The following example updates the
getContainerRenderer()import for React:Importing
getContainerRenderer()from the package root still works, but is now deprecated and logs a warning.Patch Changes
241250bThanks @ocavue! - Triggers beta prereleases for packages that are still on alphav5.0.7Compare Source
Patch Changes
17a0fbdThanks @ocavue! - Bumpsdevaluedependency to v5.8.1v5.0.6Compare Source
Patch Changes
f732f3c]:v5.0.5Compare Source
Patch Changes
d365c97]:v5.0.4Compare Source
Patch Changes
99464ed,f3485c3]:v5.0.3Compare Source
Patch Changes
a2b9eebThanks @fkatsuhiro! - Fix React 19 "Float" mechanism injecting into Astro islands instead of the . This PR adds a filter to @astrojs/react to strip these auto-generated resource from the island's HTML output, ensuring valid HTML structure.v5.0.2Compare Source
Patch Changes
#15378
a8a926eThanks @dmgawel! - Fix React hydration errors when using conditional slot rendering#15146
f771f75Thanks @kedarvartak! - Fixes hydration mismatch when usingexperimentalReactChildren#14917
769265bThanks @sanjaiyan-dev! - Refactors to improve the performance of rendering static HTML content in Reactv5.0.1Compare Source
Patch Changes
d3c7de9Thanks @florian-lefebvre! - Removes temporary support for Node >=20.19.1 because Stackblitz now uses Node 22 by defaultv5.0.0Compare Source
Major Changes
#14427
e131261Thanks @florian-lefebvre! - Increases minimum Node.js version to 22.12.0 - (v6 upgrade guidance)#14445
ecb0b98Thanks @florian-lefebvre! - Astro v6.0 upgrades to Vite v7.0 as the development server and production bundler - (v6 upgrade guidance)Minor Changes
72f7960Thanks @ocavue! - Update@vitejs/plugin-reactto v5.Patch Changes
#15187
bbb5811Thanks @matthewp! - Update to Astro 6 beta#15264
11efb05Thanks @florian-lefebvre! - Lower the Node version requirement to allow running on Stackblitz until it supports v22#15700
4e7f3e8Thanks @ocavue! - Improves how React components are identified when setting theincludeand/orexcludeoptions in projects where multiple JSX frameworks are used togetherUpdated dependencies [
4ebc1e3,4e7f3e8,a164c77,cf6ea6b,a18d727,240c317,745e632]:withastro/starlight (@astrojs/starlight)
v0.41.2Compare Source
Patch Changes
#4008
58a3520Thanks @FrancoKaddour! - Fixes the table of contents overflowing the right edge of the viewport when a custom--sl-content-widthvalue exceeds available space#4015
bdbfffcThanks @delucis! - Fixes an issue where aside icons were rendered incorrectly in projects where Astro’s MDX integration had optimization disabledv0.41.1Compare Source
Patch Changes
#3967
72e63dcThanks @HiDeoo! - Adds 2 new icons:linkandlink-alt.#3988
ac55cfaThanks @delucis! - Fixes a dependency resolution issue introduced in Starlight v0.41#3967
72e63dcThanks @HiDeoo! - Optimizes the icons of Markdown asides.v0.41.0Compare Source
Minor Changes
1202dd4Thanks @HiDeoo! - Adds support for Astro v7, drops support for Astro v6.Upgrade Astro and dependencies
Community Starlight plugins and Astro integrations may also need to be manually updated to work with Astro v7. 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.
Patch Changes
a935d33Thanks @HiDeoo! - Fixes Starlight Markdown processing being potentially applied to files that should not be processed.v0.40.0Compare Source
Minor Changes
#3923
edf2e6bThanks @Princesseuh! - Adds support for Astro 6.4 and the new Sätteri Markdown processor.It is now possible to opt into using Astro's 6.4 Sätteri Markdown processor by installing the
@astrojs/markdown-satteripackage and configuring it in yourastro.config.mjsfile:Please update Starlight and Astro together:
Community Starlight plugins and Astro integrations may also need to be manually updated to work with Sätteri. 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.
Patch Changes
edf2e6bThanks @Princesseuh! - Updates Expressive Code to version 0.43.1.v0.39.3Compare Source
Patch Changes
#3910
dddf405Thanks @andreialba! - Improves Romanian UI translations#3924
02f2ce1Thanks @BouRock! - Improves Turkish UI translations#3928
11a7ed2Thanks @delucis! - Updates Pagefind to v1.5 and adds support for Pagefind’s newdiacriticSimilarityandmetaWeightsadvanced ranking options#3927
e944870Thanks @HiDeoo! - Refactors internal file path handling for Starlight content collections.v0.39.2Compare Source
Patch Changes
2d05e18Thanks @tats-u! - Fixes CSS selector fortext-autospacestyles in Chromium browsersv0.39.1Compare Source
Patch Changes
#3885
010eed1Thanks @ArmandPhilippot! - Fixes the version mentioned in an error message related to autogenerated sidebar groups support.#3887
b3c6990Thanks @delucis! - Adds 13 new icons:clock,desktop,mobile-android,window,database,server,code-branch,notes,question,question-circle,analytics,padlock, andsolidjs.v0.39.0Compare Source
Minor Changes
#3618⚠️ BREAKING CHANGE: This release changes how autogenerated links work in Starlight’s sidebar configuration.
dcf6d09Thanks @HiDeoo! -If you have sidebar groups using the
autogeneratekey, you must now wrap that configuration in anitemsarray:{ label: 'My group', - autogenerate: { directory: 'some-dir' }, + items: [{ autogenerate: { directory: 'some-dir' } }], }This change unlocks the possibility to mix autogenerated links and other links in a single group, for example:
This release also updates the shape of autogenerated sidebar entries in route data. Autogenerated links and groups in
Astro.locals.starlightRoute.sidebarnow include anautogenerateobject with the configureddirectoryvalue:#3618⚠️ BREAKING CHANGE: This release changes the default collapsed state of autogenerated sidebar subgroups.
dcf6d09Thanks @HiDeoo! -Autogenerated subgroups no longer inherit the
collapsedvalue from their parent group. They are now expanded by default unless explicitly configured withautogenerate.collapsed.If your sidebar configuration relies on a collapsed parent group to also collapse its autogenerated subgroups, update your configuration to set
autogenerate.collapsedtotrue:{ label: 'Reference', collapsed: true, items: [ - { autogenerate: { directory: 'reference' } }, + { autogenerate: { directory: 'reference', collapsed: true } }, ], }#3845
4d755f5Thanks @delucis! - Adds a<link rel="alternate" hreflang="x-default" href="...">tag pointing to the default locale in multilingual sites. Thex-defaultalternate is used as a signal of which language to fall back to if no other is available. Learn more in Google’s SEO localization docs.#3862
ec70630Thanks @itrew! - Makes spacing of items in nested lists more consistent#3872
417a66cThanks @tats-u! - Enables the CSS propertytext-autospacein Chinese and Japanese documents.If you would prefer to disable autospacing in Chinese and Japanese pages, you can add the following custom CSS to your site:
#3797
9764ebdThanks @delucis! - Avoids the risk of layout shift when users expand and collapse sidebar groupsThis release can introduce additional padding to the site sidebar on certain devices to reserve space for scrollbars. You may wish to inspect your site sidebar visually when upgrading.
If you would prefer to keep the previous styling, you can add the following custom CSS to your site:
#3858
6672c35Thanks @delucis! - Updatesi18next, used for Starlight’s localization APIs, from v23 to v26There should not be any user-facing changes from this update
v0.38.5Compare Source
Patch Changes
ccf6000, #387747451bcThanks @delucis! - Updates internal dependenciesv0.38.4Compare Source
Patch Changes
#3828
342038bThanks @MangelMaxime! - Fixes aside styling when used without any content#3853
563e11bThanks @delucis! - Fixes a type-checking issue for users on newer versions of TypeScriptv0.38.3Compare Source
Patch Changes
#3799
313611bThanks @JosefJezek! - Improves Czech UI translations#3770
6e7bed1Thanks @gameroman! - Adds examples to the inline documentation fortitlein the Starlight configuration object#3801
fedd48bThanks @delucis! - Fixes missing draft content warning in dev on pages using the hero layoutv0.38.2Compare Source
Patch Changes
#3759
f24ce99Thanks @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.,zhSimplified Chinese) instead of the region-specific ones (e.g.,zh-TWTraditional Chinese).#3768
a4c6c20Thanks @delucis! - Improves performance of sidebar generation for sites with very large sidebarsv0.38.1Compare Source
Patch Changes
fb955ffThanks @pyxelr! - Fixes a regression causing globaltableOfContentsconfig to be ignoredv0.38.0Compare Source
Minor Changes
0d2e7edThanks @HiDeoo! - Adds support for Astro v6, drops support for Astro v5.Upgrade Astro and dependencies
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
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.collectionsflag. 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.collectionsflag.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
docsandi18ncollections, you can enable thelegacy.collectionsBackwardsCompatflag 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
375edccThanks @florian-lefebvre! - Fixes autocomplete for components exported from@astrojs/starlight/components/*components/directory. Direct use of these files was not and is not officially supported. If you previously importedTableOfContents/starlight-toc.ts,TableOfContents/TableOfContentsList.astro,Icons.ts, orSidebarPersistState.ts, please review your code when updating.#3729
3642625Thanks @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:
#3598
fff38d5Thanks @HiDeoo! - Makes hover styles consistent in Starlight’s navigation barPreviously, 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.
If you want to preserve the previous styling, you can add the following custom CSS to your site:
withastro/starlight (@astrojs/starlight-tailwind)
v5.0.0Compare Source
Major Changes
#3644⚠️ BREAKING CHANGE: The minimum supported version of Starlight is now 0.38.0
0d2e7edThanks @HiDeoo! -Please use the
@astrojs/upgradecommand to upgrade your project:biomejs/biome (@biomejs/biome)
v2.5.2Compare Source
Patch Changes
#10595
f458028Thanks @pkallos! - Added the optionignoreBooleanCoercionto useNullishCoalescing. When enabled, Biome ignores||and||=used inside aBoolean()call, where coalescing on falsy values is intentional.#10798
4a32b63Thanks @pkallos! - Added the optionignorePrimitivesto useNullishCoalescing. When enabled, Biome ignores||,||=, and ternary expressions whose non-nullish operands are all primitives the option opts out of. Usetrueto ignore all primitives, or an object selectingstring,number,boolean, orbigint.#10545
f3d4c00Thanks @Mokto! - Added the new nursery rulenoSvelteUnnecessaryStateWrap, which reports unnecessary$state()wrapping of classes fromsvelte/reactivitythat are already reactive.#10752
f62fb8bThanks @ematipico! - Fixed #10739. Now the ruleuseValidAutocompletecorrectly flags theautoCompleteattribute.#10796
f1b3ab2Thanks @ematipico! - Fixed #10768. Improved the performance of the Biome Language Server by cancelling certain in-flight operations when there are fast updates.#10719
aa649b5Thanks @minseong0324! - FixednoMisleadingReturnTypefalse positive on returns that use a widening type assertion:"a" as stringis no longer reported as misleading. The rule now also reports a literal-pinning assertion such asfalse as false, matching the existingas constbehavior.#10678
8f073a7Thanks @PranavAchar01! - Fixed #7718: Biome now correctly parses CSS nesting selectors when&appears as a trailing sub-selector after a type selector, e.g.h1& { color: red; }.#10756
5ec965aThanks @denbezrukov! - Fixed CSS formatter output for selector lists withallowWrongLineCommentsand//comments after a selector comma. Biome now keeps the selector before the line comment inline instead of breaking it across descendant combinators.#10757
6232fcdThanks @PranavAchar01! - Fixed #8269: the CSS parser now accepts Tailwind@variantand@utilitynames that start with a digit, such as the2xlbreakpoint.#10777
575ced6Thanks @WaterWhisperer! - Fixed an issue reported in #10708: the GitLab reporter now handles--verbosediagnostics filtering correctly.#10281
0efe244Thanks @Zelys-DFKH! - Fixed a bug where GritQL patterns rejected positional (unkeyed) arguments.#10758
e36fd8aThanks @henrybrewer00-dotcom! - Fixed #10697: The formatter no longer removes the parentheses around anawaitoryieldexpression used as the target of a TypeScript instantiation expression. For example,(await makeFactory)<Value>is no longer reformatted toawait makeFactory<Value>, which would change the meaning of the code.#10586
3617094Thanks @IxxyDev! - Fixed #9568:noFloatingPromisesno longer reports a false positive when calling an overloaded function and the selected overload does not return a promise.fConfiguration
📅 Schedule: (UTC)
* 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.
This PR was generated by Mend Renovate. View the repository job log.