Bump sass from 1.54.9 to 1.55.0 #585

Merged

dependabot[bot] merged 1 commit from dependabot/npm_and_yarn/develop/sass-1.55.0 into develop

2022-09-22 06:08:55 +02:00

dependabot[bot] commented

2022-09-22 06:06:26 +02:00

(Migrated from github.com)

Bumps sass from 1.54.9 to 1.55.0.

Release notes

Sourced from sass's releases.

Dart Sass 1.55.0

To install Sass 1.55.0, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.

Changes

Potentially breaking bug fix: Sass numbers are now universally stored as 64-bit floating-point numbers, rather than sometimes being stored as integers. This will generally make arithmetic with very large numbers more reliable and more consistent across platforms, but it does mean that numbers between nine quadrillion and nine quintillion will no longer be represented with full accuracy when compiling Sass on the Dart VM.

Potentially breaking bug fix: Sass equality is now properly transitive. Two numbers are now considered equal (after doing unit conversions) if they round to the same 1e-11th. Previously, numbers were considered equal if they were within 1e-11 of one another, which led to some circumstances where $a == $b and $b == $c but $a != $b.

Potentially breaking bug fix: Various functions in sass:math no longer treat floating-point numbers that are very close (but not identical) to integers as integers. Instead, these functions now follow the floating-point specification exactly. For example, math.pow(0.000000000001, -1) now returns 1000000000000 instead of Infinity.

Emit a deprecation warning for $a -$b and $a +$b, since these look like they could be unary operations but they're actually parsed as binary operations. Either explicitly write $a - $b or $a (-$b). See https://sass-lang.com/d/strict-unary for more details.

Dart API

Add an optional argumentName parameter to SassScriptException() to make it easier to throw exceptions associated with particular argument names.

Most APIs that previously returned num now return double. All APIs continue to accept num, although in Dart 2.0.0 these APIs will be changed to accept only double.

JS API

Fix a bug in which certain warning spans would not have their properties accessible by the JS API.

See the full changelog for changes in earlier releases.

Changelog

Sourced from sass's changelog.

1.55.0

Potentially breaking bug fix: Sass numbers are now universally stored as 64-bit floating-point numbers, rather than sometimes being stored as integers. This will generally make arithmetic with very large numbers more reliable and more consistent across platforms, but it does mean that numbers between nine quadrillion and nine quintillion will no longer be represented with full accuracy when compiling Sass on the Dart VM.

Potentially breaking bug fix: Sass equality is now properly transitive. Two numbers are now considered equal (after doing unit conversions) if they round to the same 1e-11th. Previously, numbers were considered equal if they were within 1e-11 of one another, which led to some circumstances where $a == $b and $b == $c but $a != $b.

Potentially breaking bug fix: Various functions in sass:math no longer treat floating-point numbers that are very close (but not identical) to integers as integers. Instead, these functions now follow the floating-point specification exactly. For example, math.pow(0.000000000001, -1) now returns 1000000000000 instead of Infinity.

Emit a deprecation warning for $a -$b and $a +$b, since these look like they could be unary operations but they're actually parsed as binary operations. Either explicitly write $a - $b or $a (-$b). See https://sass-lang.com/d/strict-unary for more details.

Dart API

Add an optional argumentName parameter to SassScriptException() to make it easier to throw exceptions associated with particular argument names.

Most APIs that previously returned num now return double. All APIs continue to accept num, although in Dart 2.0.0 these APIs will be changed to accept only double.

JS API

Fix a bug in which certain warning spans would not have their properties accessible by the JS API.

Commits

a65e504 Release 1.55.0 (#1806)
103cb19 Consistently use floating-point numbers everywhere (#1802)
90b6190 Add a deprecation warning for strict unary operations (#1800)
db1e126 Fix bug in JS MultiSpan (#1801)
5466dd7 Give SassScriptException a name parameter (#1798)
e2f9705 Merge pull request #1795 from stof/upgrade_dependencies
ba2971c Disable the prefer_interpolation_to_compose_strings rule
19ef66f Remove useless ignore rules
8480259 Avoid using private types in public APIs
a705445 Avoid null check on potentially nullable type parameter
Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot will merge this PR once CI passes on it, as requested by @Serraniel.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [sass](https://github.com/sass/dart-sass) from 1.54.9 to 1.55.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/sass/dart-sass/releases">sass's releases</a>.</em></p> <blockquote> <h2>Dart Sass 1.55.0</h2> <p>To install Sass 1.55.0, download one of the packages below and <a href="https://katiek2.github.io/path-doc/">add it to your PATH</a>, or see <a href="https://sass-lang.com/install">the Sass website</a> for full installation instructions.</p> <h1>Changes</h1> <ul> <li> <p><strong>Potentially breaking bug fix:</strong> Sass numbers are now universally stored as 64-bit floating-point numbers, rather than sometimes being stored as integers. This will generally make arithmetic with very large numbers more reliable and more consistent across platforms, but it does mean that numbers between nine quadrillion and nine quintillion will no longer be represented with full accuracy when compiling Sass on the Dart VM.</p> </li> <li> <p><strong>Potentially breaking bug fix:</strong> Sass equality is now properly <a href="https://en.wikipedia.org/wiki/Transitive_property">transitive</a>. Two numbers are now considered equal (after doing unit conversions) if they round to the same <code>1e-11</code>th. Previously, numbers were considered equal if they were within <code>1e-11</code> of one another, which led to some circumstances where <code>$a == $b</code> and <code>$b == $c</code> but <code>$a != $b</code>.</p> </li> </ul> <ul> <li> <p><strong>Potentially breaking bug fix:</strong> Various functions in <code>sass:math</code> no longer treat floating-point numbers that are very close (but not identical) to integers as integers. Instead, these functions now follow the floating-point specification exactly. For example, <code>math.pow(0.000000000001, -1)</code> now returns <code>1000000000000</code> instead of <code>Infinity</code>.</p> </li> <li> <p>Emit a deprecation warning for <code>$a -$b</code> and <code>$a +$b</code>, since these look like they could be unary operations but they're actually parsed as binary operations. Either explicitly write <code>$a - $b</code> or <code>$a (-$b)</code>. See <a href="https://sass-lang.com/d/strict-unary">https://sass-lang.com/d/strict-unary</a> for more details.</p> </li> </ul> <h3>Dart API</h3> <ul> <li> <p>Add an optional <code>argumentName</code> parameter to <code>SassScriptException()</code> to make it easier to throw exceptions associated with particular argument names.</p> </li> <li> <p>Most APIs that previously returned <code>num</code> now return <code>double</code>. All APIs continue to <em>accept</em> <code>num</code>, although in Dart 2.0.0 these APIs will be changed to accept only <code>double</code>.</p> </li> </ul> <h3>JS API</h3> <ul> <li>Fix a bug in which certain warning spans would not have their properties accessible by the JS API.</li> </ul> <p>See the <a href="https://github.com/sass/dart-sass/blob/master/CHANGELOG.md#1550">full changelog</a> for changes in earlier releases.</p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/sass/dart-sass/blob/main/CHANGELOG.md">sass's changelog</a>.</em></p> <blockquote> <h2>1.55.0</h2> <ul> <li> <p><strong>Potentially breaking bug fix:</strong> Sass numbers are now universally stored as 64-bit floating-point numbers, rather than sometimes being stored as integers. This will generally make arithmetic with very large numbers more reliable and more consistent across platforms, but it does mean that numbers between nine quadrillion and nine quintillion will no longer be represented with full accuracy when compiling Sass on the Dart VM.</p> </li> <li> <p><strong>Potentially breaking bug fix:</strong> Sass equality is now properly <a href="https://en.wikipedia.org/wiki/Transitive_property">transitive</a>. Two numbers are now considered equal (after doing unit conversions) if they round to the same <code>1e-11</code>th. Previously, numbers were considered equal if they were within <code>1e-11</code> of one another, which led to some circumstances where <code>$a == $b</code> and <code>$b == $c</code> but <code>$a != $b</code>.</p> </li> </ul> <ul> <li> <p><strong>Potentially breaking bug fix:</strong> Various functions in <code>sass:math</code> no longer treat floating-point numbers that are very close (but not identical) to integers as integers. Instead, these functions now follow the floating-point specification exactly. For example, <code>math.pow(0.000000000001, -1)</code> now returns <code>1000000000000</code> instead of <code>Infinity</code>.</p> </li> <li> <p>Emit a deprecation warning for <code>$a -$b</code> and <code>$a +$b</code>, since these look like they could be unary operations but they're actually parsed as binary operations. Either explicitly write <code>$a - $b</code> or <code>$a (-$b)</code>. See <a href="https://sass-lang.com/d/strict-unary">https://sass-lang.com/d/strict-unary</a> for more details.</p> </li> </ul> <h3>Dart API</h3> <ul> <li> <p>Add an optional <code>argumentName</code> parameter to <code>SassScriptException()</code> to make it easier to throw exceptions associated with particular argument names.</p> </li> <li> <p>Most APIs that previously returned <code>num</code> now return <code>double</code>. All APIs continue to <em>accept</em> <code>num</code>, although in Dart 2.0.0 these APIs will be changed to accept only <code>double</code>.</p> </li> </ul> <h3>JS API</h3> <ul> <li>Fix a bug in which certain warning spans would not have their properties accessible by the JS API.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/sass/dart-sass/commit/a65e504b484eeacfff5219a24ad4b89e5ee1f87f"><code>a65e504</code></a> Release 1.55.0 (<a href="https://github-redirect.dependabot.com/sass/dart-sass/issues/1806">#1806</a>)</li> <li><a href="https://github.com/sass/dart-sass/commit/103cb19b41a44d9df9d100d920376cb633e962bb"><code>103cb19</code></a> Consistently use floating-point numbers everywhere (<a href="https://github-redirect.dependabot.com/sass/dart-sass/issues/1802">#1802</a>)</li> <li><a href="https://github.com/sass/dart-sass/commit/90b6190027088dc58c9413cf1ed25550a268b1fe"><code>90b6190</code></a> Add a deprecation warning for strict unary operations (<a href="https://github-redirect.dependabot.com/sass/dart-sass/issues/1800">#1800</a>)</li> <li><a href="https://github.com/sass/dart-sass/commit/db1e1261bd183ec74ee4352083724c597670b658"><code>db1e126</code></a> Fix bug in JS MultiSpan (<a href="https://github-redirect.dependabot.com/sass/dart-sass/issues/1801">#1801</a>)</li> <li><a href="https://github.com/sass/dart-sass/commit/5466dd76a2ac2a68034de20386807ab1f60b0ecb"><code>5466dd7</code></a> Give SassScriptException a name parameter (<a href="https://github-redirect.dependabot.com/sass/dart-sass/issues/1798">#1798</a>)</li> <li><a href="https://github.com/sass/dart-sass/commit/e2f97055db1ca938d335f990337408a7796c48da"><code>e2f9705</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/sass/dart-sass/issues/1795">#1795</a> from stof/upgrade_dependencies</li> <li><a href="https://github.com/sass/dart-sass/commit/ba2971c61aed524e2982d89c50a74495cf229b1f"><code>ba2971c</code></a> Disable the prefer_interpolation_to_compose_strings rule</li> <li><a href="https://github.com/sass/dart-sass/commit/19ef66f510b3b006eb233b5dd1782f720a97a182"><code>19ef66f</code></a> Remove useless ignore rules</li> <li><a href="https://github.com/sass/dart-sass/commit/8480259d6ca29bcea85b0c04eb14af274c6bc66b"><code>8480259</code></a> Avoid using private types in public APIs</li> <li><a href="https://github.com/sass/dart-sass/commit/a705445f0d84871e175a5f0b617bd5f9aedb941e"><code>a705445</code></a> Avoid null check on potentially nullable type parameter</li> <li>Additional commits viewable in <a href="https://github.com/sass/dart-sass/compare/1.54.9...1.55.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=sass&package-manager=npm_and_yarn&previous-version=1.54.9&new-version=1.55.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) Dependabot will merge this PR once CI passes on it, as requested by @Serraniel. [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details>

Serraniel (Migrated from github.com) approved these changes 2022-09-22 06:06:47 +02:00