Repository navigation
chore(deps): update non-major (automerge) - #17
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
Contributor
🧪 Runtime gate❌ Runtime crawl did not produce a reportThe app may not have started. See the run log. ⏭️ AI explorer skippedNo Screenshots, diffs and the app log: runtime-gate artifact. |
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:
^10.6.1→^10.6.2^30.1.2→^30.1.3^1.105.1→^1.107.0^8.3.4→^8.3.5^5.0.3→^5.0.5Release Notes
postcss/autoprefixer (autoprefixer)
v10.6.2Compare Source
/* autoprefixer: ignore next warning */(by @dualfroz).-webkit-cross-fade()for images with numbers (by @mkantautas).jsdom/jsdom (jsdom)
v30.1.3Compare Source
getComputedStyle()and computed CSS property reads, including with stylesheets containing attribute selectors. (@scttcper, @asamuzaK)XMLHttpRequestreusing credentials supplied toxhr.open()after cross-origin redirects, including in response to authentication challenges from the destination.XMLHttpRequestincorrectly sending and accepting cookies after cross-origin redirects back to the document's origin whenxhr.withCredentialsis false.calc(0px - @submenu_space), while parsing documents, stylesheets, and style declarations. (@rnavarro)getComputedStyle()ignoring style rules nested inside multiple@mediarules.getComputedStyle()returning unresolved or inconsistent shorthand values, including for 'background', 'border', 'flex', 'font', 'margin', and 'padding', and incorrect shorthand defaults and inheritance.color-mix()results, which regressed in v29.0.2.currentcolorborder colors incorrectly becoming transparent when 'color' useslight-dark()or relative color syntax.[data-a|=""]failing to match empty values and values beginning with-. (@asamuzaK)sass/dart-sass (sass)
v1.107.0Compare Source
Command-Line Interface
The
--fatal-deprecationflag can now exclude deprecations that wouldotherwise be included by passing a version number. To exclude a deprecation,
add
-before its name. For example,--fatal-deprecation=1.107.0,-importincludes all deprecations that were present in Dart Sass 1.107.0 except for
the
@importdeprecation.The
--fatal-deprecationflag now takes the special valuedart-sass-2,which treats as fatal all deprecations that will become fatal in Dart Sass
2.0.0.
JavaScript API
Options.fatalDeprecationscan now take aDeprecationSelectorDifferenceobject of the form
{include: ..., except: ...}, where theincludefieldlists deprecations to mark fatal (which can be version numbers) and the
exceptfield lists deprecations not to mark fatal. Theexceptfieldtakes precedence over
include.Add a (non-enumerable)
sass.deprecations.dartSass2property which can bepassed to
Options.fatalDeprecationsto mark as fatal exactly thedeprecations that will become fatal in Dart Sass 2.0.0. This can be combined
with other deprecations or used in a
DeprecationSelectorDifferenceto modifyexactly which deprecations it covers.
Passing a version number beyond the current Dart Sass version to
Options.fatalDeprecationsis now deprecated. See the Sasswebsite for details.
Dart API
Add a
Deprecation.dartSass2property which returns exactly the set ofdeprecations that will become fatal in Dart Sass 2.0.0.
Passing a version number beyond the current Dart Sass version to
Deprecation.forVersionis now deprecated.Embedded Protocol
CompileRequest.fatal_deprecation_exceptfield which excludesdeprecations from being considered fatal if they would have been enabled by
CompileRequest.fatal_deprecation.v1.106.1Compare Source
Fix a bug where an attribute selector with an empty value (such as
[class=""]) would crash when serializing.Don't crash when serializing a number with an empty unit. This is only
possible through the JavaScript and Dart APIs or the embedded protocol.
Embedded Dart Sass
PARAMSerrors.v1.106.0Compare Source
Don't normalize CSS escapes in statement contexts that can contain
interpolation. For example,
@f\6Fois now emitted as written rather thannormalized to
@foo.Fix a bug where quotes would be removed from attribute selector values that
contained backslashes.
Fix invalid source spans that could cause crashes when encountering a syntax
error in selectors or media queries that also contain escape sequences.
Fix a bug where the indented syntax parser would crash when parsing a file
where the first statement was indented and appeared after the first line.
Fix a bug that could cause crashes when encountering errors or warnings in
interpolations that contain patterns like
// */.Potentially breaking compatibility fix: CSS escape codes whose values are
0, for Unicode surrogates, or greater than the maximum allowed code point are
now consistently normalized to U+FFFD REPLACEMENT CHARACTER in expression
contexts. Previously, in some cases these were instead normalized to the
normalized form of the original escape sequence, which violates the principle
that all escape sequences for identical values should be normalized the same
way. In other cases, these would simply throw errors.
As a special case,
\0on its own will continue to be normalized to\0tosupport historical CSS hacks.
Potentially breaking bug fix: Throw an error for mixins and functions that
have rest parameters which are the same as normal parameters. Previously, the
positional parameters wouldn't be accessible and calling such a mixin or
function with a named argument would crash the compiler.
Potentially breaking bug fix: Fix various cases where using a CSS escape
code at the beginning of an identifier would change parsing behavior versus
using the character directly.
Potentially breaking bug fix: When a number's unit is ambiguous with a
numeric exponent, the unit is now serialized as an escape code rather than a
literal
eto avoid being interpreted as an exponent by CSS.Potentially breaking bug fix: Don't parse a CSS escape code for U+45 LATIN
CAPITAL LETTER E or U+65 LATIN LOWERCASE LETTER E as an exponent in
@keyframespercentage selectors.Potentially breaking bug fix: Properly normalize underscores written as
CSS escape codes in variable, mixin, and function names.
v1.105.2Compare Source
Node.js Embedded Host
vitejs/vite (vite)
v8.3.5Compare Source
Bug Fixes
server.originto asset URLs (#23683) (52ba877)import.meta.env.*defines in theimport.meta.envobject (#23713) (6019aa7)%inurl()(#23676) (50b382d)oxc.jsxInjectimports (#23758) (38f3cb4)#(#23631) (0d86b34)Performance Improvements
Miscellaneous Chores
Code Refactoring
@vercel/detect-agentwithstd-env(#23744) (ce4293f)vitest-dev/vitest (vitest)
v5.0.5Compare Source
🐞 Bug Fixes
fs.denywith api token file - by @hi-ogawa, Hiroshi Ogawa and Claude Opus 5.5 in #11578 (28dc1)--changed- by @sheremet-va in #11583 (14921)datato theimport.meta.hotstub - by @sheremet-va in #11590 (3a828)skipinskipIf, ignoreundefinedoptions - by @sheremet-va in #11591 (d523a)&#​39;failed&#​39;on worker crash - by @AriPerkkio in #11568 (6ae8e)View changes on GitHub
v5.0.4Compare Source
🚀 Features
test.ui.themeoption - by @sheremet-va in #11499 (1da66)--changed- by @sheremet-va in #11424 (a2336)🐞 Bug Fixes
:in project and change the shape ofresultscache - by @sheremet-va in #11453 (9673c)$string values whentaskTitleValueFormatTruncateis 0 - by @hi-ogawa, Hiroshi Ogawa and Claude Opus 5.5 in #11485 (4f7e1)maxWorkerssetting. Previously, it was applied incorrectly and could lead to Vitest using too many resources. For example, a lower number would still open too many browsers. Fixing it means Vitest opens less instances by default now.allowExternalfails to include uncovered files - by @AriPerkkio in #11513 (4ef00)MapandSetdeep equality in some assertions - by @hi-ogawa, Hiroshi Ogawa and Claude Opus 5.5 in #11402 (b4e79)thistomodule.exports- by @sheremet-va in #11504 (b618a)🏎 Performance
View changes on GitHub
Configuration
📅 Schedule: (in timezone Europe/London)
* * 1-3 * *)🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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.