deps: bump sass from 1.98.0 to 1.101.0 in /next #558

Open
dependabot[bot] wants to merge 1 commit from dependabot/npm_and_yarn/next/main/sass-1.101.0 into main
dependabot[bot] commented 2026-07-12 05:28:15 +00:00 (Migrated from github.com)

Bumps sass from 1.98.0 to 1.101.0.

Release notes

Sourced from sass's releases.

Dart Sass 1.101.0

To install Sass 1.101.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: The Node package importer now properly supports resolving import-only variants of Sass files declared in the exports, sass, and style fields of package.json. Previously, these files were ignored even when loaded via @import, so any code relying on loading module-system-only files this way may break.

See the full changelog for changes in earlier releases.

Dart Sass 1.100.0

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

Changes

  • Writing two compound selectors adjacent to one another without any whitespace between them, such as [class]a, is now deprecated. This was always an error in CSS and Sass only supported it by mistake.

    See the Sass website for details.

See the full changelog for changes in earlier releases.

Dart Sass 1.99.0

To install Sass 1.99.0, 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 parent selectors (&) at the root of the document. These are emitted as-is in the CSS output, where they're interpreted as the scoping root.

  • User-defined functions named calc or clamp are no longer forbidden. If such a function exists without a namespace in the current module, it will be used instead of the built-in calc() or clamp() function.

  • User-defined functions whose names begin with - and end with -expression, -url, -and, -or, or -not are no longer forbidden. These were originally intended to match vendor prefixes, but in practice no vendor prefixes for these functions ever existed in real browsers.

  • User-defined functions named EXPRESSION, URL, and ELEMENT, those that begin with - and end with -ELEMENT, as well as the same names with some lowercase letters are now deprecated, These are names conflict with plain CSS functions that have special syntax.

    See the Sass website for details.

  • In a future release, calls to functions whose names begin with - and end with -expression and -url will no longer have special parsing. For now, these calls are deprecated if their behavior will change in the future.

    See the Sass website for details.

... (truncated)

Changelog

Sourced from sass's changelog.

1.101.0

  • Potentially breaking bug fix: The Node package importer now properly supports resolving import-only variants of Sass files declared in the exports, sass, and style fields of package.json. Previously, these files were ignored even when loaded via @import, so any code relying on loading module-system-only files this way may break.

1.100.0

  • Writing two compound selectors adjacent to one another without any whitespace between them, such as [class]a, is now deprecated. This was always an error in CSS and Sass only supported it by mistake.

    See the Sass website for details.

1.99.0

  • Add support for parent selectors (&) at the root of the document. These are emitted as-is in the CSS output, where they're interpreted as the scoping root.

  • User-defined functions named calc or clamp are no longer forbidden. If such a function exists without a namespace in the current module, it will be used instead of the built-in calc() or clamp() function.

  • User-defined functions whose names begin with - and end with -expression, -url, -and, -or, or -not are no longer forbidden. These were originally intended to match vendor prefixes, but in practice no vendor prefixes for these functions ever existed in real browsers.

  • User-defined functions named EXPRESSION, URL, and ELEMENT, those that begin with - and end with -ELEMENT, as well as the same names with some lowercase letters are now deprecated, These are names conflict with plain CSS functions that have special syntax.

    See the Sass website for details.

  • In a future release, calls to functions whose names begin with - and end with -expression and -url will no longer have special parsing. For now, these calls are deprecated if their behavior will change in the future.

    See the Sass website for details.

  • Calls to functions whose names begin with - and end with -progid:... are deprecated.

... (truncated)

Commits
  • 63b9922 Load import-only files through package.json exports (#2772)
  • c7e9947 Migrate from bufbuild/buf-setup-action to bufbuild/buf-action (#2773)
  • 7674a4c Bump postcss from 8.5.13 to 8.5.15 in /pkg/sass-parser (#2774)
  • 5fd18c7 Bump node engine requirement to >=20.19.0 and chokidar requirement to ^5.0.0 ...
  • 8c1d984 Deprecate adjacent compound selectors (#2765)
  • 8e5f718 Bump postcss from 8.5.12 to 8.5.13 in /pkg/sass-parser (#2767)
  • 1447f9b Bump postcss from 8.5.8 to 8.5.12 in /pkg/sass-parser (#2766)
  • 83c39fe Support the top-level parent selector (#2758)
  • ec85871 Bump EndBug/add-and-commit from 9 to 10 (#2756)
  • a604acd [Function Name] Implement changes (#2731)
  • See full diff in compare view

Bumps [sass](https://github.com/sass/dart-sass) from 1.98.0 to 1.101.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.101.0</h2> <p>To install Sass 1.101.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><strong>Potentially breaking bug fix:</strong> The Node package importer now properly supports resolving import-only variants of Sass files declared in the <code>exports</code>, <code>sass</code>, and <code>style</code> fields of <code>package.json</code>. Previously, these files were ignored even when loaded via <code>@import</code>, so any code relying on loading module-system-only files this way may break.</li> </ul> <p>See the <a href="https://github.com/sass/dart-sass/blob/master/CHANGELOG.md#11010">full changelog</a> for changes in earlier releases.</p> <h2>Dart Sass 1.100.0</h2> <p>To install Sass 1.100.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>Writing two compound selectors adjacent to one another without any whitespace between them, such as <code>[class]a</code>, is now deprecated. This was always an error in CSS and Sass only supported it by mistake.</p> <p>See <a href="https://sass-lang.com/d/adjacent-compounds">the Sass website</a> for details.</p> </li> </ul> <p>See the <a href="https://github.com/sass/dart-sass/blob/master/CHANGELOG.md#11000">full changelog</a> for changes in earlier releases.</p> <h2>Dart Sass 1.99.0</h2> <p>To install Sass 1.99.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>Add support for parent selectors (<code>&amp;</code>) at the root of the document. These are emitted as-is in the CSS output, where they're interpreted as <a href="https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Selectors/Nesting_selector#using_outside_nested_rule">the scoping root</a>.</p> </li> <li> <p>User-defined functions named <code>calc</code> or <code>clamp</code> are no longer forbidden. If such a function exists without a namespace in the current module, it will be used instead of the built-in <code>calc()</code> or <code>clamp()</code> function.</p> </li> <li> <p>User-defined functions whose names begin with <code>-</code> and end with <code>-expression</code>, <code>-url</code>, <code>-and</code>, <code>-or</code>, or <code>-not</code> are no longer forbidden. These were originally intended to match vendor prefixes, but in practice no vendor prefixes for these functions ever existed in real browsers.</p> </li> <li> <p>User-defined functions named <code>EXPRESSION</code>, <code>URL</code>, and <code>ELEMENT</code>, those that begin with <code>-</code> and end with <code>-ELEMENT</code>, as well as the same names with some lowercase letters are now deprecated, These are names conflict with plain CSS functions that have special syntax.</p> <p>See <a href="https://sass-lang.com/d/function-name">the Sass website</a> for details.</p> </li> <li> <p>In a future release, calls to functions whose names begin with <code>-</code> and end with <code>-expression</code> and <code>-url</code> will no longer have special parsing. For now, these calls are deprecated if their behavior will change in the future.</p> <p>See <a href="https://sass-lang.com/d/function-name">the Sass website</a> for details.</p> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </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.101.0</h2> <ul> <li><strong>Potentially breaking bug fix:</strong> The Node package importer now properly supports resolving import-only variants of Sass files declared in the <code>exports</code>, <code>sass</code>, and <code>style</code> fields of <code>package.json</code>. Previously, these files were ignored even when loaded via <code>@import</code>, so any code relying on loading module-system-only files this way may break.</li> </ul> <h2>1.100.0</h2> <ul> <li> <p>Writing two compound selectors adjacent to one another without any whitespace between them, such as <code>[class]a</code>, is now deprecated. This was always an error in CSS and Sass only supported it by mistake.</p> <p>See <a href="https://sass-lang.com/d/adjacent-compounds">the Sass website</a> for details.</p> </li> </ul> <h2>1.99.0</h2> <ul> <li> <p>Add support for parent selectors (<code>&amp;</code>) at the root of the document. These are emitted as-is in the CSS output, where they're interpreted as <a href="https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Selectors/Nesting_selector#using_outside_nested_rule">the scoping root</a>.</p> </li> <li> <p>User-defined functions named <code>calc</code> or <code>clamp</code> are no longer forbidden. If such a function exists without a namespace in the current module, it will be used instead of the built-in <code>calc()</code> or <code>clamp()</code> function.</p> </li> <li> <p>User-defined functions whose names begin with <code>-</code> and end with <code>-expression</code>, <code>-url</code>, <code>-and</code>, <code>-or</code>, or <code>-not</code> are no longer forbidden. These were originally intended to match vendor prefixes, but in practice no vendor prefixes for these functions ever existed in real browsers.</p> </li> <li> <p>User-defined functions named <code>EXPRESSION</code>, <code>URL</code>, and <code>ELEMENT</code>, those that begin with <code>-</code> and end with <code>-ELEMENT</code>, as well as the same names with some lowercase letters are now deprecated, These are names conflict with plain CSS functions that have special syntax.</p> <p>See <a href="https://sass-lang.com/d/function-name">the Sass website</a> for details.</p> </li> <li> <p>In a future release, calls to functions whose names begin with <code>-</code> and end with <code>-expression</code> and <code>-url</code> will no longer have special parsing. For now, these calls are deprecated if their behavior will change in the future.</p> <p>See <a href="https://sass-lang.com/d/function-name">the Sass website</a> for details.</p> </li> <li> <p>Calls to functions whose names begin with <code>-</code> and end with <code>-progid:...</code> are deprecated.</p> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/sass/dart-sass/commit/63b9922f5ddbf34bc742b50949e0ee5c47f4686d"><code>63b9922</code></a> Load import-only files through package.json <code>exports</code> (<a href="https://redirect.github.com/sass/dart-sass/issues/2772">#2772</a>)</li> <li><a href="https://github.com/sass/dart-sass/commit/c7e9947100e8ffdabfe314a4e342595f2bccff35"><code>c7e9947</code></a> Migrate from bufbuild/buf-setup-action to bufbuild/buf-action (<a href="https://redirect.github.com/sass/dart-sass/issues/2773">#2773</a>)</li> <li><a href="https://github.com/sass/dart-sass/commit/7674a4c29d05c844dcffd40a91e7cf2ac216d524"><code>7674a4c</code></a> Bump postcss from 8.5.13 to 8.5.15 in /pkg/sass-parser (<a href="https://redirect.github.com/sass/dart-sass/issues/2774">#2774</a>)</li> <li><a href="https://github.com/sass/dart-sass/commit/5fd18c75e31a855476059fb6fb0c6aa829292739"><code>5fd18c7</code></a> Bump node engine requirement to &gt;=20.19.0 and chokidar requirement to ^5.0.0 ...</li> <li><a href="https://github.com/sass/dart-sass/commit/8c1d984e420d891c9c92ba1afc8b28e70a2afb78"><code>8c1d984</code></a> Deprecate adjacent compound selectors (<a href="https://redirect.github.com/sass/dart-sass/issues/2765">#2765</a>)</li> <li><a href="https://github.com/sass/dart-sass/commit/8e5f7180b4f3de4281d3454090548c03e9db8135"><code>8e5f718</code></a> Bump postcss from 8.5.12 to 8.5.13 in /pkg/sass-parser (<a href="https://redirect.github.com/sass/dart-sass/issues/2767">#2767</a>)</li> <li><a href="https://github.com/sass/dart-sass/commit/1447f9b42e89d693ce308bad9cbf8ec3e1db78c4"><code>1447f9b</code></a> Bump postcss from 8.5.8 to 8.5.12 in /pkg/sass-parser (<a href="https://redirect.github.com/sass/dart-sass/issues/2766">#2766</a>)</li> <li><a href="https://github.com/sass/dart-sass/commit/83c39fec93ab0dc183a46cff2bc468999ce53e20"><code>83c39fe</code></a> Support the top-level parent selector (<a href="https://redirect.github.com/sass/dart-sass/issues/2758">#2758</a>)</li> <li><a href="https://github.com/sass/dart-sass/commit/ec85871864ca16f8045e66ad329bd462e791bfa1"><code>ec85871</code></a> Bump EndBug/add-and-commit from 9 to 10 (<a href="https://redirect.github.com/sass/dart-sass/issues/2756">#2756</a>)</li> <li><a href="https://github.com/sass/dart-sass/commit/a604acd19ad2ce31ef2efe9aa5950b0c5fcc74a9"><code>a604acd</code></a> [Function Name] Implement changes (<a href="https://redirect.github.com/sass/dart-sass/issues/2731">#2731</a>)</li> <li>See full diff in <a href="https://github.com/sass/dart-sass/compare/1.98.0...1.101.0">compare view</a></li> </ul> </details> <br />
This pull request has changes conflicting with the target branch.
  • next/package-lock.json
View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin dependabot/npm_and_yarn/next/main/sass-1.101.0:dependabot/npm_and_yarn/next/main/sass-1.101.0
git switch dependabot/npm_and_yarn/next/main/sass-1.101.0

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff dependabot/npm_and_yarn/next/main/sass-1.101.0
git switch dependabot/npm_and_yarn/next/main/sass-1.101.0
git rebase main
git switch main
git merge --ff-only dependabot/npm_and_yarn/next/main/sass-1.101.0
git switch dependabot/npm_and_yarn/next/main/sass-1.101.0
git rebase main
git switch main
git merge --no-ff dependabot/npm_and_yarn/next/main/sass-1.101.0
git switch main
git merge --squash dependabot/npm_and_yarn/next/main/sass-1.101.0
git switch main
git merge --ff-only dependabot/npm_and_yarn/next/main/sass-1.101.0
git switch main
git merge dependabot/npm_and_yarn/next/main/sass-1.101.0
git push origin main
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
SSE/WebsiteTheSSEquel!558
No description provided.