[Snyk] Upgrade sass from 1.26.3 to 1.55.0

[mongoloidkhulmikuki366385]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to upgrade sass from 1.26.3 to 1.55.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 97 versions ahead of your current version.
• The recommended version was released a month ago, on 2022-09-21.

Release notes

Package name: sass

• 1.55.0 - 2022-09-21
  

  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.

• 1.54.9 - 2022-09-07
  

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

  Changes

  • Fix an incorrect span in certain @ media query deprecation warnings.

  See the full changelog for changes in earlier releases.

• 1.54.8 - 2022-08-31
  

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

  Changes

  • No user-visible changes.

  See the full changelog for changes in earlier releases.

• 1.54.7 - 2022-08-31
  

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

  Changes

  • Add support for 32-bit ARM releases on Linux.

  See the full changelog for changes in earlier releases.

• 1.54.6 - 2022-08-29
  

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

  Changes

  • Fix a bug where a @ media query could be incorrectly omitted from a stylesheet if it had multiple levels of nested @ media queries within it and the inner queries were mergeable but the outer query was not.

  See the full changelog for changes in earlier releases.

• 1.54.5 - 2022-08-19
• 1.54.4 - 2022-08-10
• 1.54.3 - 2022-08-04
• 1.54.2 - 2022-08-03
• 1.54.1 - 2022-08-02
• 1.54.0 - 2022-07-22
• 1.53.0 - 2022-06-22
• 1.52.3 - 2022-06-08
• 1.52.2 - 2022-06-03
• 1.52.1 - 2022-05-20
• 1.52.0 - 2022-05-20
• 1.51.0 - 2022-04-26
• 1.50.1 - 2022-04-19
• 1.50.0 - 2022-04-07
• 1.49.11 - 2022-04-01
• 1.49.10 - 2022-03-30
• 1.49.9 - 2022-02-24
• 1.49.8 - 2022-02-17
• 1.49.7 - 2022-02-01
• 1.49.6 - 2022-02-01
• 1.49.5 - 2022-02-01
• 1.49.4 - 2022-02-01
• 1.49.3 - 2022-02-01
• 1.49.2 - 2022-02-01
• 1.49.1 - 2022-01-31
• 1.49.0 - 2022-01-18
• 1.48.0 - 2022-01-13
• 1.47.0 - 2022-01-07
• 1.46.0 - 2022-01-06
• 1.45.2 - 2021-12-31
• 1.45.1 - 2021-12-21
• 1.45.0 - 2021-12-10
• 1.45.0-rc.2 - 2021-12-02
• 1.45.0-rc.1 - 2021-11-30
• 1.44.0 - 2021-11-30
• 1.43.5 - 2021-11-24
• 1.43.4 - 2021-10-26
• 1.43.3 - 2021-10-21
• 1.43.2 - 2021-10-13
• 1.42.1 - 2021-09-22
• 1.42.0 - 2021-09-21
• 1.41.1 - 2021-09-16
• 1.41.0 - 2021-09-14
• 1.40.1 - 2021-09-14
• 1.40.0 - 2021-09-13
• 1.39.2 - 2021-09-10
• 1.39.1 - 2021-09-09
• 1.39.0 - 2021-09-02
• 1.38.2 - 2021-08-28
• 1.38.1 - 2021-08-23
• 1.38.0 - 2021-08-17
• 1.37.5 - 2021-08-04
• 1.37.4 - 2021-08-03
• 1.37.3 - 2021-08-03
• 1.37.2 - 2021-08-03
• 1.37.1 - 2021-08-02
• 1.37.0 - 2021-07-30
• 1.36.0 - 2021-07-23
• 1.35.2 - 2021-07-07
• 1.35.1 - 2021-06-15
• 1.35.0 - 2021-06-15
• 1.34.1 - 2021-06-02
• 1.34.0 - 2021-05-22
• 1.33.0 - 2021-05-21
• 1.32.13 - 2021-05-12
• 1.32.12 - 2021-04-28
• 1.32.11 - 2021-04-19
• 1.32.10 - 2021-04-16
• 1.32.9 - 2021-04-16
• 1.32.8 - 2021-02-18
• 1.32.7 - 2021-02-10
• 1.32.6 - 2021-02-01
• 1.32.5 - 2021-01-20
• 1.32.4 - 2021-01-12
• 1.32.3 - 2021-01-12
• 1.32.2 - 2021-01-07
• 1.32.1 - 2021-01-06
• 1.32.0 - 2020-12-30
• 1.30.0 - 2020-12-04
• 1.29.0 - 2020-11-05
• 1.28.0 - 2020-10-29
• 1.27.2 - 2020-10-29
• 1.27.1 - 2020-10-28
• 1.27.0 - 2020-10-08
• 1.26.12 - 2020-10-06
• 1.26.11 - 2020-09-18
• 1.26.10 - 2020-07-06
• 1.26.9 - 2020-06-22
• 1.26.8 - 2020-06-05
• 1.26.7 - 2020-05-29
• 1.26.6 - 2020-05-28
• 1.26.5 - 2020-04-24
• 1.26.3 - 2020-03-11

from sass GitHub release notes

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[performance-testing-bot]

Unable to locate .performanceTestingBot config file

[pull-request-quantifier-deprecated]

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 2

Change summary by file extension:
.json : +1 -1

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detected.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.