search

dgiot / iotStudio

dgiot平台行业应用扩展插件 dgiot for application plugin
https://dgiot-dashboard.vercel.app/
Mozilla Public License 2.0
283 stars 102 forks source link

chore(deps-dev): bump sass from 1.32.13 to 1.56.1 #623

Closed dependabot[bot] closed 2 years ago

dependabot[bot] commented 2 years ago

Bumps sass from 1.32.13 to 1.56.1.

Release notes

Sourced from sass's releases.

Dart Sass 1.56.1

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

Changes

Embedded Sass

  • Importer results now validate that contents is actually a string and whether sourceMapUrl is an absolute URL.

See the full changelog for changes in earlier releases.

Dart Sass 1.56.0

To install Sass 1.56.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 change: To match the CSS spec, SassScript expressions beginning with not or ( are no longer supported at the beginning of parenthesized sections of media queries. For example,

    @media (width >= 500px) and (not (grid))

    will now be emitted unchanged, instead of producing

    @media (width >= 500px) and (false)

    See the Sass website for details.

  • Potentially breaking bug fix: Angle units like rad or turn are now properly converted to equivalent deg values for hsl(), hsla(), adjust-hue(), color.adjust(), and color.change().

    See the Sass website for details.

  • Fix indentation for selectors that span multiple lines in a @media query.

  • Emit a deprecation warning when passing $alpha values with units to color.adjust() or color.change(). This will be an error in Dart Sass 2.0.0.

    See the Sass website for details.

  • Emit a deprecation warning when passing a $weight value with no units or with units other than % to color.mix(). This will be an error in Dart Sass 2.0.0.

    See the Sass website for details.

... (truncated)

Changelog

Sourced from sass's changelog.

1.56.1

Embedded Sass

  • Importer results now validate that contents is actually a string and whether sourceMapUrl is an absolute URL.

1.56.0

  • Potentially breaking change: To match the CSS spec, SassScript expressions beginning with not or ( are no longer supported at the beginning of parenthesized sections of media queries. For example,

    @media (width >= 500px) and (not (grid))

    will now be emitted unchanged, instead of producing

    @media (width >= 500px) and (false)

    See the Sass website for details.

  • Potentially breaking bug fix: Angle units like rad or turn are now properly converted to equivalent deg values for hsl(), hsla(), adjust-hue(), color.adjust(), and color.change().

    See the Sass website for details.

  • Fix indentation for selectors that span multiple lines in a @media query.

  • Emit a deprecation warning when passing $alpha values with units to color.adjust() or color.change(). This will be an error in Dart Sass 2.0.0.

    See the Sass website for details.

  • Emit a deprecation warning when passing a $weight value with no units or with units other than % to color.mix(). This will be an error in Dart Sass 2.0.0.

    See the Sass website for details.

  • Emit a deprecation warning when passing $n values with units to list.nth() or list.set-nth(). This will be an error in Dart Sass 2.0.0.

... (truncated)

Commits
  • 790eb8a Update CHANGELOG for embedded-host-node fixes (#1828)
  • f3293db JS API: Validate that importer result 'contents' is a string and improve Ar...
  • 00c3517 Make `cloneCss() clone modules that transitively contain CSS (#1824)
  • 44d6bb6 Add full support for Media Queries 4 (#1822)
  • 558640b Support all angle units in color functions (#1818)
  • dd9e3cc Implement deprecations for strict function units (#1817)
  • 655b55c Indent comma-separated multiline selectors inside @​media queries (#1814)
  • 6e670ef Insert explicit type arguments where types could not be inferred. (#1813)
  • a65e504 Release 1.55.0 (#1806)
  • 103cb19 Consistently use floating-point numbers everywhere (#1802)
  • Additional commits viewable in compare view


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)
pull-checklist[bot] commented 2 years ago

Example Check Group #2 (Click here to edit)

vercel[bot] commented 2 years ago

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated
dgiot-dashboard ❌ Failed (Inspect) Nov 10, 2022 at 5:28AM (UTC)
pull-request-quantifier-deprecated[bot] commented 2 years ago

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

Quantification details

``` Label : Extra Small Size : +1 -1 Percentile : 0.8% Total files changed: 1 Change summary by file extension: .json : +1 -1 ``` > Change counts above are quantified counts, based on the [PullRequestQuantifier customizations](https://github.com/microsoft/PullRequestQuantifier/blob/main/docs/prquantifier-yaml.md).

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a balance between between PR complexity and PR review overhead. PRs within the optimal size (typical small, or medium sized PRs) mean: - Fast and predictable releases to production: - Optimal size changes are more likely to be reviewed faster with fewer iterations. - Similarity in low PR complexity drives similar review times. - Review quality is likely higher as complexity is lower: - Bugs are more likely to be detected. - Code inconsistencies are more likely to be detected. - Knowledge sharing is improved within the participants: - Small portions can be assimilated better. - Better engineering practices are exercised: - Solving big problems by dividing them in well contained, smaller problems. - Exercising separation of concerns within the code changes. #### What can I do to optimize my changes - Use the PullRequestQuantifier to quantify your PR accurately - Create a context profile for your repo using the [context generator](https://github.com/microsoft/PullRequestQuantifier/releases) - Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the `Excluded` section from your `prquantifier.yaml` context profile. - Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your `prquantifier.yaml` context profile. - Only use the labels that matter to you, [see context specification](./docs/prquantifier-yaml.md) to customize your `prquantifier.yaml` context profile. - Change your engineering behaviors - For PRs that fall outside of the desired spectrum, review the details and check if: - Your PR could be split in smaller, self-contained PRs instead - Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR). #### How to interpret the change counts in git diff output - One line was added: `+1 -0` - One line was deleted: `+0 -1` - One line was modified: `+1 -1` (git diff doesn't know about modified, it will interpret that line like one addition plus one deletion) - Change percentiles: Change characteristics (addition, deletion, modification) of this PR in relation to all other PRs within the repository.

Was this comment helpful? :thumbsup:  :ok_hand:  :thumbsdown: (Email) Customize PullRequestQuantifier for this repository.

dependabot[bot] commented 2 years ago

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.