Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump sass from 1.57.0 to 1.59.3 #356

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 20, 2023

Bumps sass from 1.57.0 to 1.59.3.

Release notes

Sourced from sass's releases.

Dart Sass 1.59.3

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

Changes

  • Fix a performance regression introduced in 1.59.0.

  • The NPM release of 1.59.0 dropped support for Node 12 without actually indicating so in its pubspec. This release temporarily adds back support so that the latest Sass version that declares it supports Node 12 actually does so. However, Node 12 is now end-of-life, so we will drop support for it properly in an upcoming release.

See the full changelog for changes in earlier releases.

Dart Sass 1.59.2

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

Changes

  • No user-visible changes.

See the full changelog for changes in earlier releases.

Dart Sass 1.59.1

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

Changes

  • No user-visible changes.

See the full changelog for changes in earlier releases.

Dart Sass 1.59.0

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

Changes

Command Line Interface

  • Added a new --fatal-deprecation flag that lets you treat a deprecation warning as an error. You can pass an individual deprecation ID (e.g. slash-div) or you can pass a Dart Sass version to treat all deprecations initially emitted in that version or earlier as errors.

... (truncated)

Changelog

Sourced from sass's changelog.

1.59.3

  • Fix a performance regression introduced in 1.59.0.

  • The NPM release of 1.59.0 dropped support for Node 12 without actually indicating so in its pubspec. This release temporarily adds back support so that the latest Sass version that declares it supports Node 12 actually does so. However, Node 12 is now end-of-life, so we will drop support for it properly in an upcoming release.

1.59.2

  • No user-visible changes.

1.59.1

  • No user-visible changes.

1.59.0

Command Line Interface

  • Added a new --fatal-deprecation flag that lets you treat a deprecation warning as an error. You can pass an individual deprecation ID (e.g. slash-div) or you can pass a Dart Sass version to treat all deprecations initially emitted in that version or earlier as errors.

  • New --future-deprecation flag that lets you opt into warning for use of certain features that will be deprecated in the future. At the moment, the only option is --future-deprecation=import, which will emit warnings for Sass @import rules, which are not yet deprecated, but will be in the future.

Dart API

  • New Deprecation enum, which contains the different current and future deprecations used by the new CLI flags.

  • The compile methods now take in fatalDeprecations and futureDeprecations parameters, which work similarly to the CLI flags.

1.58.4

  • Pull @font-face to the root rather than bubbling the style rule selector inwards.

  • Improve error messages for invalid CSS values passed to plain CSS functions.

  • Improve error messages involving selectors.

Embedded Sass

... (truncated)

Commits

Dependabot compatibility score

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 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)

Bumps [sass](https://github.com/sass/dart-sass) from 1.57.0 to 1.59.3.
- [Release notes](https://github.com/sass/dart-sass/releases)
- [Changelog](https://github.com/sass/dart-sass/blob/main/CHANGELOG.md)
- [Commits](sass/dart-sass@1.57.0...1.59.3)

---
updated-dependencies:
- dependency-name: sass
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Mar 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants