Skip to content

Update sass from 1.32.12 to 1.49.9

Takuya Noguchi requested to merge tnir-sass-1.49.9 into master

What does this MR do and why?

Update sass from 1.32.12 to 1.49.9.

Previous update: !60609 (merged)

Follows gitlab-ui!2726 (merged)

Potential breaking changes from the full changelog:

1.48.0

JS API

Potentially breaking bug fix: Match the specification of the new JS API by setting LegacyResult.map to undefined rather than null.

1.46.0

JS API

Potentially breaking bug fix: Match the specification of the new JS API by passing undefined rather than null to Logger.warn() for an unset span.

1.45.2

JS API

Potentially breaking bug fix: Change the default value of the separator parameter for new SassArgumentList() to ',' rather than null. This matches the API specification.

1.45.1

Potentially breaking bug fix: Properly parse custom properties in @supports conditions. Note that this means that SassScript expressions on the right-hand side of custom property @supports queries now need to be interpolated, as per https://sass-lang.com/d/css-vars.

Potentially breaking bug fix: Fix a bug where inspect() was not properly printing nested, empty, bracketed lists.

1.37.0

Dart API

Potentially breaking bug fix: SassNumber.asSlash, SassNumber.withSlash(), and SassNumber.withoutSlash() have been marked as @internal. They were never intended to be used outside the sass package.

Potentially breaking bug fix: SassException has been marked as @sealed to formally indicate that it's not intended to be extended outside of the sass package.

1.35.2

Potentially breaking bug fix: Properly throw an error for Unicode ranges that have too many ?s after hexadecimal digits, such as U+12345??.

Potentially breaking bug fix: Fixed a bug where certain local variable declarations nested within multiple @if statements would incorrectly override a global variable. It's unlikely that any real stylesheets were relying on this bug, but if so they can simply add !global to the variable declaration to preserve the old behavior.

Potentially breaking bug fix: Fix a bug where imports of root-relative URLs (those that begin with /) in @import rules would be passed to both Dart and JS importers as file: URLs.

1.33.0

Deprecate the use of / for division. The new math.div() function should be used instead. See this page for details.

Add a list.slash() function that returns a slash-separated list.

Potentially breaking bug fix: The heuristics around when potentially slash-separated numbers are converted to slash-free numbers—for example, when 1/2 will be printed as 0.5 rather than 1/2—have been slightly expanded. Previously, a number would be made slash-free if it was passed as an argument to a user-defined function, but not to a built-in function. Now it will be made slash-free in both cases. This is a behavioral change, but it's unlikely to affect any real-world stylesheets.

1.32.13

Potentially breaking bug fix: Null values in @use and @forward configurations no longer override the !default variable, matching the behavior of the equivalent code using @import.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Takuya Noguchi

Merge request reports