44d4821a8d
Bumps [sass](https://github.com/sass/dart-sass) from 1.72.0 to 1.74.1. <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.74.1</h2> <p>To install Sass 1.74.1, 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>No user-visible changes.</li> </ul> <p>See the <a href="https://github.com/sass/dart-sass/blob/master/CHANGELOG.md#1741">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.74.1</h2> <ul> <li>No user-visible changes.</li> </ul> <h2>1.74.0</h2> <h3>JS API</h3> <ul> <li> <p>Add a new top-level <code>deprecations</code> object, which contains various <code>Deprecation</code> objects that define the different types of deprecation used by the Sass compiler and can be passed to the options below.</p> </li> <li> <p>Add a new <code>fatalDeprecations</code> compiler option that causes the compiler to error if any deprecation warnings of the provided types are encountered. You can also pass in a <code>Version</code> object to treat all deprecations that were active in that Dart Sass version as fatal.</p> </li> <li> <p>Add a new <code>futureDeprecations</code> compiler option that allows you to opt-in to certain deprecations early (currently just <code>import</code>).</p> </li> <li> <p>Add a new <code>silenceDeprecations</code> compiler option to ignore any deprecation warnings of the provided types.</p> </li> </ul> <h3>Command-Line Interface</h3> <ul> <li> <p>Add a new <code>--silence-deprecation</code> flag, which causes the compiler to ignore any deprecation warnings of the provided types.</p> </li> <li> <p>Previously, if a future deprecation was passed to <code>--fatal-deprecation</code> but not <code>--future-deprecation</code>, it would be treated as fatal despite not being enabled. Both flags are now required to treat a future deprecation as fatal with a warning emitted if <code>--fatal-deprecation</code> is passed without <code>--future-deprecation</code>, matching the JS API's behavior.</p> </li> </ul> <h3>Dart API</h3> <ul> <li> <p>The <code>compile</code> methods now take in a <code>silenceDeprecations</code> parameter, which causes the compiler to ignore any deprecation warnings of the provided types.</p> </li> <li> <p>Add <code>Deprecation.obsoleteIn</code> to match the JS API. This is currently null for all deprecations, but will be used once some deprecations become obsolete in Dart Sass 2.0.0.</p> </li> <li> <p><strong>Potentially breaking bug fix:</strong> Fix a bug where <code>compileStringToResultAsync</code> ignored <code>fatalDeprecations</code> and <code>futureDeprecations</code>.</p> </li> <li> <p>The behavior around making future deprecations fatal mentioned in the CLI section above has also been changed in the Dart API.</p> </li> </ul> <h2>1.73.0</h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="1137797f17"><code>1137797</code></a> Fix bulma and release 1.74.1 (<a href="https://redirect.github.com/sass/dart-sass/issues/2210">#2210</a>)</li> <li><a href="d9220d9c37"><code>d9220d9</code></a> Complete implementation the deprecations API (<a href="https://redirect.github.com/sass/dart-sass/issues/2207">#2207</a>)</li> <li><a href="783c248d2f"><code>783c248</code></a> Fix typo in function documentation (<a href="https://redirect.github.com/sass/dart-sass/issues/2205">#2205</a>)</li> <li><a href="c8d064368c"><code>c8d0643</code></a> Better handle filesystem importers when load paths aren't necessary (<a href="https://redirect.github.com/sass/dart-sass/issues/2203">#2203</a>)</li> <li><a href="9302b3519c"><code>9302b35</code></a> Add support for nesting in plain CSS (<a href="https://redirect.github.com/sass/dart-sass/issues/2198">#2198</a>)</li> <li><a href="772280a7ff"><code>772280a</code></a> Support linux-riscv64 and windows-arm64 (<a href="https://redirect.github.com/sass/dart-sass/issues/2201">#2201</a>)</li> <li>See full diff in <a href="https://github.com/sass/dart-sass/compare/1.72.0...1.74.1">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) You can trigger a rebase of this PR 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>
Corso
Corso is the first open-source tool that aims to assist IT admins with the critical task of protecting their Microsoft 365 data. It provides a reliable, secure, and efficient data protection engine. Admins decide where to store the backup data and have the flexibility to perform backups of their desired service through an intuitive interface. As Corso evolves, it can become a great building block for more complex data protection workflows.
Corso is currently in Beta.
Corso supports M365 Exchange and OneDrive with SharePoint and Teams support in active development. Coverage for more services, possibly beyond M365, will expand based on the interest and needs of the community.
Getting Started
See the Corso Quickstart on our docs page.
Building Corso
To learn more about working with the project source core and building Corso, see the Developer section of the Corso Documentation.
Roadmap
You can learn more about the Corso roadmap and how to interpret it here.
If you have feature requests, please file a GitHub issue
and attach the enhancement label to the issue.
Contribution Guidelines
Code of Conduct
It's important that our community is inclusive and respectful of everyone. We ask that all Corso users and contributors take a few minutes to review our Code of Conduct.
License
Corso is licensed under the Apache License, Version 2.0. See LICENSE for the full license text.