[sbb-angular-renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
sass	1.105.2 → 1.107.0

---

Release Notes

sass/dart-sass (sass)

v1.107.0

Compare Source

Command-Line Interface

• The --fatal-deprecation flag can now exclude deprecations that would
  otherwise be included by passing a version number. To exclude a deprecation,
  add - before its name. For example, --fatal-deprecation=1.107.0,-import
  includes all deprecations that were present in Dart Sass 1.107.0 except for
  the @import deprecation.

• The --fatal-deprecation flag now takes the special value dart-sass-2,
  which treats as fatal all deprecations that will become fatal in Dart Sass
  2.0.0.

JavaScript API

• Options.fatalDeprecations can now take a DeprecationSelectorDifference
  object of the form {include: ..., except: ...}, where the include field
  lists deprecations to mark fatal (which can be version numbers) and the
  except field lists deprecations not to mark fatal. The except field
  takes precedence over include.

• Add a (non-enumerable) sass.deprecations.dartSass2 property which can be
  passed to Options.fatalDeprecations to mark as fatal exactly the
  deprecations that will become fatal in Dart Sass 2.0.0. This can be combined
  with other deprecations or used in a DeprecationSelectorDifference to modify
  exactly which deprecations it covers.

• Passing a version number beyond the current Dart Sass version to
  Options.fatalDeprecations is now deprecated. See the Sass
  website for details.

Dart API

• Add a Deprecation.dartSass2 property which returns exactly the set of
  deprecations that will become fatal in Dart Sass 2.0.0.

• Passing a version number beyond the current Dart Sass version to
  Deprecation.forVersion is now deprecated.

Embedded Protocol

• Add a CompileRequest.fatal_deprecation_except field which excludes
  deprecations from being considered fatal if they would have been enabled by
  CompileRequest.fatal_deprecation.

v1.106.1

Compare 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

• More robustly convert invalid value errors into PARAMS errors.

v1.106.0

Compare Source

• Don't normalize CSS escapes in statement contexts that can contain
  interpolation. For example, @f\6Fo is now emitted as written rather than
  normalized 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, \0 on its own will continue to be normalized to \0 to
  support 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 e to 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
  @keyframes percentage selectors.

• Potentially breaking bug fix: Properly normalize underscores written as
  CSS escape codes in variable, mixin, and function names.

---

Configuration

📅 Schedule: (in timezone Europe/Zurich)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate.

[sbb-angular-renovate]

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.

---

• Branch has one or more failed status checks