Bump sass from 1.89.2 to 1.93.3

[dependabot]

Bumps sass from 1.89.2 to 1.93.3.

Release notes

Sourced from sass's releases.

Dart Sass 1.93.3

To install Sass 1.93.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 that was introduced in 1.92.0.

See the full changelog for changes in earlier releases.

Dart Sass 1.93.2

To install Sass 1.93.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.

JavaScript API

• Fix another error in the release process for @sass/types.

See the full changelog for changes in earlier releases.

Dart Sass 1.93.1

To install Sass 1.93.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.

JavaScript API

• Fix an error in the release process for @sass/types.

See the full changelog for changes in earlier releases.

Dart Sass 1.93.0

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

... (truncated)

Changelog

Sourced from sass's changelog.

1.93.3

• Fix a performance regression that was introduced in 1.92.0.

1.93.2

• No user-visible changes.

JavaScript API

• Fix another error in the release process for @sass/types.

1.93.1

• No user-visible changes.

JavaScript API

• Fix an error in the release process for @sass/types.

1.93.0

• Fix a crash when a style rule contains a nested @import, and the loaded file @uses a user-defined module as well as @includes a top-level mixin which emits top-level declarations.

JavaScript API

• Release a @sass/types package which contains the type annotations used by both the sass and sass-embedded package without any additional code or dependencies.

1.92.1

• Fix a bug where variable definitions from one imported, forwarded module would not be passed as implicit configuration to a later imported, forwarded module.

1.92.0

• Breaking change: Emit declarations, childless at-rules, and comments in the order they appear in the source even when they're interleaved with nested rules. This obsoletes the mixed-decls deprecation.

• Breaking change: The function name type() is now fully reserved for the plain CSS function. This means that @function definitions with the name type will produce errors, while function calls will be parsed as special function strings.

• Configuring private variables using @use ... with, @forward ... with, and

... (truncated)

Commits

• 4e5bd25 Stop holding onto stack traces for every CSS declaration (#2666)
• 65b77ee Bump analyzer, protobuf, protoc_plugin and dartdoc (#2660)
• e61936c Bump actions/setup-node from 4 to 6 (#2661)
• b5f4c67 Bump actions/setup-node from 5 to 6 in /.github/util/initialize (#2662)
• b8b35e8 Mark @​sass/types as public (#2653)
• 0b7d6d9 Empty commit
• 4e94339 Fix the release script for @sass/types (#2651)
• 710ef80 Switch to macos-15-intel runner (#2650)
• 307226a Publish a @sass/types package with the types of the shared JS API (#2639)
• edfe90d Fix crash when @​importing a Sass file that @​uses another file (#2599)
• 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)

[shopify-shipitnext]

🔎 View this PR in Shipit Next.

ℹ️ Expand to learn how to deploy and handle emergencies using Shipit Next

Overview

Shipit Next will merge your code on your behalf because this repository uses Shipit Next and its merge queue.

To ship this PR, you can either:

• Comment /shipit to enqueue this PR for merging.
• Go to this PR in Shipit Next and click on the "Ship It" button in the top-right corner.

Comment Commands

• /shipit: Enqueue this PR into the merge queue where it will eventually be merged and deployed.
• /cancel: Eject this PR from the merge queue and rebuild PRs that were enqueued after this PR.
• /shipit --jump-queue: Enqueue this PR at the top of the merge queue where it will be included in the next deploy. Use this for non-emergency situations.
  - Emergency handling procedure for this command can be found here.
• /shipit --emergency: Merge this PR directly into main and deploy to all environments once all require_for_emergency CI checks pass. Please be aware that changes deployed with this command will not be automatically rolled back.
  • Emergency handling procedure for this command can be found here.

Commands exclusive to Deploy Before Merge

• /cancel --emergency: Eject this PR from the merge and rollback any deployments containing this PR.

---

Documentation

• ℹ️ You can read how the merge queue works in Vault here.
• ⚠️ Emergency handling documentation in the Vault describes how to handle emergencies, e.g. failed canaries, broken code in production, etc.

Questions or feedback?

• Non-urgent questions can be submitted in our Discourse.
• Feedback can be submitted in our frustrations Google form.
• If you have feature requests, you may add them or vote for them in our GitHub repository.