chore(deps): update dependency sass to v1.72.0 #1938
Conversation
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
❌ @renovate[bot] the
📝 What should I do to fix it?All proposed commits should include a sign-off in their messages, ideally at the end. ❔ Why it is requiredThe Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:
Contributors sign-off that they adhere to these requirements by adding a Git even has a |
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/sass-1.x-lockfile
branch
from
53fe0fd to
c0aa956
Compare
|
❌ @renovate[bot] the
📝 What should I do to fix it?All proposed commits should include a sign-off in their messages, ideally at the end. ❔ Why it is requiredThe Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:
Contributors sign-off that they adhere to these requirements by adding a Git even has a |
2 similar comments
|
❌ @renovate[bot] the
📝 What should I do to fix it?All proposed commits should include a sign-off in their messages, ideally at the end. ❔ Why it is requiredThe Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:
Contributors sign-off that they adhere to these requirements by adding a Git even has a |
|
❌ @renovate[bot] the
📝 What should I do to fix it?All proposed commits should include a sign-off in their messages, ideally at the end. ❔ Why it is requiredThe Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:
Contributors sign-off that they adhere to these requirements by adding a Git even has a |
renovate
bot
force-pushed
the
renovate/sass-1.x-lockfile
branch
from
c0aa956 to
061fef5
Compare
|
❌ @renovate[bot] the
📝 What should I do to fix it?All proposed commits should include a sign-off in their messages, ideally at the end. ❔ Why it is requiredThe Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:
Contributors sign-off that they adhere to these requirements by adding a Git even has a |
1 similar comment
|
❌ @renovate[bot] the
📝 What should I do to fix it?All proposed commits should include a sign-off in their messages, ideally at the end. ❔ Why it is requiredThe Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:
Contributors sign-off that they adhere to these requirements by adding a Git even has a |
renovate
bot
force-pushed
the
renovate/sass-1.x-lockfile
branch
from
061fef5 to
ec4b5ab
Compare
|
❌ @renovate[bot] the
📝 What should I do to fix it?All proposed commits should include a sign-off in their messages, ideally at the end. ❔ Why it is requiredThe Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:
Contributors sign-off that they adhere to these requirements by adding a Git even has a |
renovate
bot
force-pushed
the
renovate/sass-1.x-lockfile
branch
from
ec4b5ab to
7dda550
Compare
|
❌ @renovate[bot] the
📝 What should I do to fix it?All proposed commits should include a sign-off in their messages, ideally at the end. ❔ Why it is requiredThe Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:
Contributors sign-off that they adhere to these requirements by adding a Git even has a |
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/sass-1.x-lockfile
branch
from
7dda550 to
c26c8fb
Compare
|
❌ @renovate[bot] the
📝 What should I do to fix it?All proposed commits should include a sign-off in their messages, ideally at the end. ❔ Why it is requiredThe Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:
Contributors sign-off that they adhere to these requirements by adding a Git even has a |
1 similar comment
|
❌ @renovate[bot] the
📝 What should I do to fix it?All proposed commits should include a sign-off in their messages, ideally at the end. ❔ Why it is requiredThe Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:
Contributors sign-off that they adhere to these requirements by adding a Git even has a |
renovate
bot
force-pushed
the
renovate/sass-1.x-lockfile
branch
from
c26c8fb to
0e521a7
Compare
|
❌ @renovate[bot] the
📝 What should I do to fix it?All proposed commits should include a sign-off in their messages, ideally at the end. ❔ Why it is requiredThe Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:
Contributors sign-off that they adhere to these requirements by adding a Git even has a |
1 similar comment
|
❌ @renovate[bot] the
📝 What should I do to fix it?All proposed commits should include a sign-off in their messages, ideally at the end. ❔ Why it is requiredThe Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:
Contributors sign-off that they adhere to these requirements by adding a Git even has a |
renovate
bot
force-pushed
the
renovate/sass-1.x-lockfile
branch
from
0e521a7 to
d70db21
Compare
renovate
bot
changed the title
|
❌ @renovate[bot] the
📝 What should I do to fix it?All proposed commits should include a sign-off in their messages, ideally at the end. ❔ Why it is requiredThe Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:
Contributors sign-off that they adhere to these requirements by adding a Git even has a |
1 similar comment
|
❌ @renovate[bot] the
📝 What should I do to fix it?All proposed commits should include a sign-off in their messages, ideally at the end. ❔ Why it is requiredThe Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:
Contributors sign-off that they adhere to these requirements by adding a Git even has a |
renovate
bot
force-pushed
the
renovate/sass-1.x-lockfile
branch
from
d70db21 to
235b72f
Compare
|
❌ @renovate[bot] the
📝 What should I do to fix it?All proposed commits should include a sign-off in their messages, ideally at the end. ❔ Why it is requiredThe Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:
Contributors sign-off that they adhere to these requirements by adding a Git even has a |
renovate
bot
force-pushed
the
renovate/sass-1.x-lockfile
branch
from
235b72f to
3455840
Compare
|
❌ @renovate[bot] the
📝 What should I do to fix it?All proposed commits should include a sign-off in their messages, ideally at the end. ❔ Why it is requiredThe Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:
Contributors sign-off that they adhere to these requirements by adding a Git even has a |
1 similar comment
|
❌ @renovate[bot] the
📝 What should I do to fix it?All proposed commits should include a sign-off in their messages, ideally at the end. ❔ Why it is requiredThe Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:
Contributors sign-off that they adhere to these requirements by adding a Git even has a |
renovate
bot
force-pushed
the
renovate/sass-1.x-lockfile
branch
from
3455840 to
86074c4
Compare
|
❌ @renovate[bot] the
📝 What should I do to fix it?All proposed commits should include a sign-off in their messages, ideally at the end. ❔ Why it is requiredThe Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:
Contributors sign-off that they adhere to these requirements by adding a Git even has a |
renovate
bot
force-pushed
the
renovate/sass-1.x-lockfile
branch
from
86074c4 to
b72ff43
Compare
renovate
bot
changed the title
|
❌ @renovate[bot] the
📝 What should I do to fix it?All proposed commits should include a sign-off in their messages, ideally at the end. ❔ Why it is requiredThe Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:
Contributors sign-off that they adhere to these requirements by adding a Git even has a |
1 similar comment
|
❌ @renovate[bot] the
📝 What should I do to fix it?All proposed commits should include a sign-off in their messages, ideally at the end. ❔ Why it is requiredThe Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:
Contributors sign-off that they adhere to these requirements by adding a Git even has a |
renovate
bot
force-pushed
the
renovate/sass-1.x-lockfile
branch
from
b72ff43 to
b1c13a3
Compare
|
❌ @renovate[bot] the
📝 What should I do to fix it?All proposed commits should include a sign-off in their messages, ideally at the end. ❔ Why it is requiredThe Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:
Contributors sign-off that they adhere to these requirements by adding a Git even has a |
1 similar comment
|
❌ @renovate[bot] the
📝 What should I do to fix it?All proposed commits should include a sign-off in their messages, ideally at the end. ❔ Why it is requiredThe Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:
Contributors sign-off that they adhere to these requirements by adding a Git even has a |
renovate
bot
force-pushed
the
renovate/sass-1.x-lockfile
branch
from
b1c13a3 to
a2a8981
Compare
|
❌ @renovate[bot] the
📝 What should I do to fix it?All proposed commits should include a sign-off in their messages, ideally at the end. ❔ Why it is requiredThe Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:
Contributors sign-off that they adhere to these requirements by adding a Git even has a |
This PR contains the following updates:
1.69.5->1.72.0Release Notes
sass/dart-sass (sass)
v1.72.0Compare Source
Support adjacent
/s without whitespace in between when parsing plain CSSexpressions.
Allow the Node.js
pkg:importer to load Sass stylesheets forpackage.jsonexportsfield entries without extensions.When printing suggestions for variables, use underscores in variable names
when the original usage used underscores.
JavaScript API
pkg:imports with the Node.js package importer whenarguments are passed to the JavaScript process.
v1.71.1Compare Source
Command-Line Interface
JavaScript API
Export the
NodePackageImporterclass in ESM mode.Allow
NodePackageImporterto locate a default directory even when theentrypoint is an ESM module.
Dart API
NodePackageImporter()a static error ratherthan just a runtime error.
Embedded Sass
when running on musl Linux.
v1.71.0Compare Source
For more information about
pkg:importers, see theannouncement on the Sass blog.
Command-Line Interface
--pkg-importerflag to enable built-inpkg:importers. Currentlythis only supports the Node.js package resolution algorithm, via
--pkg-importer=node. For example,@use "pkg:bootstrap"will loadnode_modules/bootstrap/scss/bootstrap.scss.JavaScript API
NodePackageImporterimporter that can be passed to theimportersoption. This loads files using the
pkg:URL scheme according to the Node.jspackage resolution algorithm. For example,
@use "pkg:bootstrap"will loadnode_modules/bootstrap/scss/bootstrap.scss. The constructor takes a singleoptional argument, which indicates the base directory to use when locating
node_modulesdirectories. It defaults topath.dirname(require.main.filename).Dart API
NodePackageImporterimporter that can be passed to theimportersoption. This loads files using the
pkg:URL scheme according to the Node.jspackage resolution algorithm. For example,
@use "pkg:bootstrap"will loadnode_modules/bootstrap/scss/bootstrap.scss. The constructor takes a singleargument, which indicates the base directory to use when locating
node_modulesdirectories.v1.70.0Compare Source
JavaScript API
Add a
sass.initCompiler()function that returns asass.Compilerobjectwhich supports
compile()andcompileString()methods with the same API asthe global Sass object. On the Node.js embedded host, each
sass.Compilerobject uses a single long-lived subprocess, making compiling multiple
stylesheets much more efficient.
Add a
sass.initAsyncCompiler()function that returns asass.AsyncCompilerobject which supports
compileAsync()andcompileStringAsync()methods withthe same API as the global Sass object. On the Node.js embedded host, each
sass.AsynCompilerobject uses a single long-lived subprocess, makingcompiling multiple stylesheets much more efficient.
Embedded Sass
Support the
CompileRequest.silentfield. This allows compilations with nologging to avoid unnecessary request/response cycles.
The Dart Sass embedded compiler now reports its name as "dart-sass" rather
than "Dart Sass", to match the JS API's
infofield.v1.69.7Compare Source
Embedded Sass
ARM64 Windows.
v1.69.6Compare Source
Produce better output for numbers with complex units in
meta.inspect()anddebugging messages.
Escape U+007F DELETE when serializing strings.
When generating CSS error messages to display in-browser, escape all code
points that aren't in the US-ASCII region. Previously only code points U+0100
LATIN CAPITAL LETTER A WITH MACRON were escaped.
Provide official releases for musl LibC and for Android.
Don't crash when running
meta.apply()in asynchronous mode.JS API
SourceSpans that didn'tfollow the documented
SourceSpanAPI.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.