[PR #240] [MERGED] chore(deps): Bump sass from 1.94.2 to 1.95.0 #315

New issue

Closed

opened 2026-05-06 12:16:22 +02:00 by BreizhHardware · 0 comments

BreizhHardware commented

2026-05-06 12:16:22 +02:00

Owner

📋 Pull Request Information

Original PR: https://github.com/BreizhHardware/portfolio/pull/240
Author: @dependabot[bot]
Created: 12/8/2025
Status: ✅ Merged
Merged: 12/9/2025
Merged by: @BreizhHardware

Base: dev ← Head: dependabot/npm_and_yarn/dev/sass-1.95.0

📝 Commits (1)

32c9ed6 chore(deps): Bump sass from 1.94.2 to 1.95.0

📊 Changes

2 files changed (+21 additions, -21 deletions)

View changed files

📝 package.json (+1 -1)
📝 pnpm-lock.yaml (+20 -20)

📄 Description

Bumps sass from 1.94.2 to 1.95.0.

Release notes

Sourced from sass's releases.

Dart Sass 1.95.0

To install Sass 1.95.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 the CSS-style if() function. In addition to supporting the plain CSS syntax, this also supports a sass() query that takes a Sass expression that evaluates to true or false at preprocessing time depending on whether the Sass value is truthy. If there are no plain-CSS queries, the function will return the first value whose query returns true during preprocessing. For example, if(sass(false): 1; sass(true): 2; else: 3) returns 2.

The old Sass if() syntax is now deprecated. Users are encouraged to migrate to the new CSS syntax. if($condition, $if-true, $if-false) can be changed to if(sass($condition): $if-true; else: $if-false).

See the Sass website for details.

Plain-CSS if() functions are now considered "special numbers", meaning that they can be used in place of arguments to CSS color functions.

Plain-CSS if() functions and attr() functions are now considered "special variable strings" (like var()), meaning they can now be used in place of multiple arguments or syntax fragments in various CSS functions.

See the full changelog for changes in earlier releases.

Dart Sass 1.94.3

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

Changes

Fix the span reported for standalone % expressions followed by whitespace.

See the full changelog for changes in earlier releases.

Changelog

Sourced from sass's changelog.

1.95.0

Add support for the CSS-style if() function. In addition to supporting the plain CSS syntax, this also supports a sass() query that takes a Sass expression that evaluates to true or false at preprocessing time depending on whether the Sass value is truthy. If there are no plain-CSS queries, the function will return the first value whose query returns true during preprocessing. For example, if(sass(false): 1; sass(true): 2; else: 3) returns 2.

The old Sass if() syntax is now deprecated. Users are encouraged to migrate to the new CSS syntax. if($condition, $if-true, $if-false) can be changed to if(sass($condition): $if-true; else: $if-false).

See the Sass website for details.

Plain-CSS if() functions are now considered "special numbers", meaning that they can be used in place of arguments to CSS color functions.

Plain-CSS if() functions and attr() functions are now considered "special variable strings" (like var()), meaning they can now be used in place of multiple arguments or syntax fragments in various CSS functions.

1.94.3

Fix the span reported for standalone % expressions followed by whitespace.

Commits

2abc89e Merge pull request #2693 from sass/css-if
2f7a16c Revert "Bump chokidar from 4.0.3 to 5.0.0 in /package (#2690)" (#2691)
38d4ac8 Add ArgumentList.namedSpans
6f9a593 Add support for plain-CSS if()
3b95eb7 Rename IfExpression to LegacyIfExpression
e2bf843 Make the recursive AST visitor comprehensive (#2694)
9380924 Fix the operator span when parsing a standalone % (#2667)
f8a8a51 Bump chokidar from 4.0.3 to 5.0.0 in /package (#2690)
e4837d1 Bump archive from 3.6.1 to 4.0.7 (#2688)
293200b Bump protoc_plugin from 23.0.0 to 24.0.0 (#2677)
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 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
@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)

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/BreizhHardware/portfolio/pull/240 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 12/8/2025 **Status:** ✅ Merged **Merged:** 12/9/2025 **Merged by:** [@BreizhHardware](https://github.com/BreizhHardware) **Base:** `dev` ← **Head:** `dependabot/npm_and_yarn/dev/sass-1.95.0` --- ### 📝 Commits (1) - [`32c9ed6`](https://github.com/BreizhHardware/portfolio/commit/32c9ed602765c6831662f0a76e03a98e468a1460) chore(deps): Bump sass from 1.94.2 to 1.95.0 ### 📊 Changes **2 files changed** (+21 additions, -21 deletions) <details> <summary>View changed files</summary> 📝 `package.json` (+1 -1) 📝 `pnpm-lock.yaml` (+20 -20) </details> ### 📄 Description Bumps [sass](https://github.com/sass/dart-sass) from 1.94.2 to 1.95.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.95.0</h2> <p>To install Sass 1.95.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 the <a href="https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Values/if">CSS-style <code>if()</code> function</a>. In addition to supporting the plain CSS syntax, this also supports a <code>sass()</code> query that takes a Sass expression that evaluates to <code>true</code> or <code>false</code> at preprocessing time depending on whether the Sass value is truthy. If there are no plain-CSS queries, the function will return the first value whose query returns true during preprocessing. For example, <code>if(sass(false): 1; sass(true): 2; else: 3)</code> returns <code>2</code>.</p> </li> <li> <p>The old Sass <code>if()</code> syntax is now deprecated. Users are encouraged to migrate to the new CSS syntax. <code>if($condition, $if-true, $if-false)</code> can be changed to <code>if(sass($condition): $if-true; else: $if-false)</code>.</p> <p>See <a href="https://sass-lang.com/d/css-if">the Sass website</a> for details.</p> </li> <li> <p>Plain-CSS <code>if()</code> functions are now considered "special numbers", meaning that they can be used in place of arguments to CSS color functions.</p> </li> <li> <p>Plain-CSS <code>if()</code> functions and <code>attr()</code> functions are now considered "special variable strings" (like <code>var()</code>), meaning they can now be used in place of multiple arguments or syntax fragments in various CSS functions.</p> </li> </ul> <p>See the <a href="https://github.com/sass/dart-sass/blob/master/CHANGELOG.md#1950">full changelog</a> for changes in earlier releases.</p> <h2>Dart Sass 1.94.3</h2> <p>To install Sass 1.94.3, 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>Fix the span reported for standalone <code>%</code> expressions followed by whitespace.</li> </ul> <p>See the <a href="https://github.com/sass/dart-sass/blob/master/CHANGELOG.md#1943">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.95.0</h2> <ul> <li> <p>Add support for the <a href="https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Values/if">CSS-style <code>if()</code> function</a>. In addition to supporting the plain CSS syntax, this also supports a <code>sass()</code> query that takes a Sass expression that evaluates to <code>true</code> or <code>false</code> at preprocessing time depending on whether the Sass value is truthy. If there are no plain-CSS queries, the function will return the first value whose query returns true during preprocessing. For example, <code>if(sass(false): 1; sass(true): 2; else: 3)</code> returns <code>2</code>.</p> </li> <li> <p>The old Sass <code>if()</code> syntax is now deprecated. Users are encouraged to migrate to the new CSS syntax. <code>if($condition, $if-true, $if-false)</code> can be changed to <code>if(sass($condition): $if-true; else: $if-false)</code>.</p> <p>See <a href="https://sass-lang.com/d/css-if">the Sass website</a> for details.</p> </li> <li> <p>Plain-CSS <code>if()</code> functions are now considered "special numbers", meaning that they can be used in place of arguments to CSS color functions.</p> </li> <li> <p>Plain-CSS <code>if()</code> functions and <code>attr()</code> functions are now considered "special variable strings" (like <code>var()</code>), meaning they can now be used in place of multiple arguments or syntax fragments in various CSS functions.</p> </li> </ul> <h2>1.94.3</h2> <ul> <li>Fix the span reported for standalone <code>%</code> expressions followed by whitespace.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/sass/dart-sass/commit/2abc89e9e52864065a16fa7e23c4ca55726d5b56"><code>2abc89e</code></a> Merge pull request <a href="https://redirect.github.com/sass/dart-sass/issues/2693">#2693</a> from sass/css-if</li> <li><a href="https://github.com/sass/dart-sass/commit/2f7a16c9cf2f10b82097429dbd24819eb475858b"><code>2f7a16c</code></a> Revert "Bump chokidar from 4.0.3 to 5.0.0 in /package (<a href="https://redirect.github.com/sass/dart-sass/issues/2690">#2690</a>)" (<a href="https://redirect.github.com/sass/dart-sass/issues/2691">#2691</a>)</li> <li><a href="https://github.com/sass/dart-sass/commit/38d4ac8665e1b03e41f5556e10b6e61004da6851"><code>38d4ac8</code></a> Add ArgumentList.namedSpans</li> <li><a href="https://github.com/sass/dart-sass/commit/6f9a5933db524686782c74d1339cb3e474d9b5eb"><code>6f9a593</code></a> Add support for plain-CSS if()</li> <li><a href="https://github.com/sass/dart-sass/commit/3b95eb775136a8e8dd87de4bdbd1ee1a3d05d3a0"><code>3b95eb7</code></a> Rename IfExpression to LegacyIfExpression</li> <li><a href="https://github.com/sass/dart-sass/commit/e2bf8434e5fbb6c9c5c8281a55cc3aaec90f3d5d"><code>e2bf843</code></a> Make the recursive AST visitor comprehensive (<a href="https://redirect.github.com/sass/dart-sass/issues/2694">#2694</a>)</li> <li><a href="https://github.com/sass/dart-sass/commit/9380924b8b178b6db9ac91d1a87c63414966aff7"><code>9380924</code></a> Fix the operator span when parsing a standalone <code>%</code> (<a href="https://redirect.github.com/sass/dart-sass/issues/2667">#2667</a>)</li> <li><a href="https://github.com/sass/dart-sass/commit/f8a8a51c0fb6db600b0e8cc7aaf9edb5e25a5f6e"><code>f8a8a51</code></a> Bump chokidar from 4.0.3 to 5.0.0 in /package (<a href="https://redirect.github.com/sass/dart-sass/issues/2690">#2690</a>)</li> <li><a href="https://github.com/sass/dart-sass/commit/e4837d1ae3b1850812861bcf7e4bb37bb77225c2"><code>e4837d1</code></a> Bump archive from 3.6.1 to 4.0.7 (<a href="https://redirect.github.com/sass/dart-sass/issues/2688">#2688</a>)</li> <li><a href="https://github.com/sass/dart-sass/commit/293200b1b1f895375f2c4cc6299ca531ee7c3fdc"><code>293200b</code></a> Bump protoc_plugin from 23.0.0 to 24.0.0 (<a href="https://redirect.github.com/sass/dart-sass/issues/2677">#2677</a>)</li> <li>Additional commits viewable in <a href="https://github.com/sass/dart-sass/compare/1.94.2...1.95.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.94.2&new-version=1.95.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-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 show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@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> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>