Bump sass from 1.79.5 to 1.81.1 in /frontend

[dependabot]

Bumps sass from 1.79.5 to 1.81.1.

Release notes

Sourced from sass's releases.

Dart Sass 1.81.1

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

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

Changes

• Fix a few cases where deprecation warnings weren't being emitted for global built-in functions whose names overlap with CSS calculations.

• Add support for the CSS round() calculation with a single argument, as long as that argument might be a unitless number.

See the full changelog for changes in earlier releases.

Dart Sass 1.80.7

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

Changes

Embedded Host

• Don't treat 0 as undefined for the green and blue channels in the LegacyColor constructor.

See the full changelog for changes in earlier releases.

Dart Sass 1.80.6

To install Sass 1.80.6, 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

... (truncated)

Changelog

Sourced from sass's changelog.

1.81.1

• No user-visible changes.

1.81.0

• Fix a few cases where deprecation warnings weren't being emitted for global built-in functions whose names overlap with CSS calculations.

• Add support for the CSS round() calculation with a single argument, as long as that argument might be a unitless number.

1.80.7

Embedded Host

• Don't treat 0 as undefined for the green and blue channels in the LegacyColor constructor.

1.80.6

Command-Line Interface

• Make @parcel/watcher an optional dependency so this can still be installed on operating systems where it's unavailable.

1.80.5

Embedded Host

• Don't produce phantom @import deprecations when using an importer with the legacy API.

1.80.4

• No user-visible changes.

1.80.3

• Fix a bug where @import url("...") would crash in plain CSS files.

• Improve consistency of how warnings are emitted by different parts of the compiler. This should result in minimal user-visible changes, but different types of warnings should now respond more reliably to flags like --quiet, --verbose, and --silence-deprecation.

1.80.2

• Fix a bug where deprecation warnings were incorrectly emitted for the plain-CSS invert() function.

... (truncated)

Commits

• 5163644 Expose NodePackageImporter in sass_api (#2452)
• 02fff80 Merge pull request #2439 from sass/function
• 6939faa Bump typedoc from 0.26.11 to 0.27.2 in /pkg/sass-parser (#2451)
• 9abdfaa Bump lints from 4.0.0 to 5.0.0 (#2441)
• 1e07de7 Bump pub_api_client from 2.7.1 to 3.0.0 (#2442)
• b10ca79 Add sass-parser support for @function
• ea47287 Update some configuration names to avoid unnecessary namespacing
• 30fc4db Bump bufbuild/buf-setup-action in /.github/util/initialize (#2438)
• 2c5c7d4 Enable tests now that ForwardRule exists (#2437)
• 57a6853 Add support for CSS round() with one unitless argument (#2436)
• 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)

Summary by Sourcery

Build:

• Update the 'sass' dependency from version 1.79.5 to 1.81.1 in the frontend package.json.

[dependabot]

Dependabot tried to add @drosetti as a reviewer to this PR, but received the following error from GitHub:

POST https://api.github.com/repos/khulnasoft/ThreatMatrix/pulls/185/requested_reviewers: 422 - Reviews may only be requested from collaborators. One or more of the users or teams you specified is not a collaborator of the khulnasoft/ThreatMatrix repository. // See: https://docs.github.com/rest/pulls/review-requests#request-reviewers-for-a-pull-request

[sourcery-ai]

Reviewer's Guide by Sourcery

This PR updates the sass dependency in the frontend from version 1.79.5 to 1.81.1. The update includes minor bug fixes, improvements to deprecation warnings, and adds support for CSS round() calculation with single unitless arguments.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Update sass dependency version	Bump version from 1.79.5 to 1.81.1 Add support for CSS round() calculation with single unitless arguments Fix deprecation warnings for global built-in functions overlapping with CSS calculations Fix handling of green and blue channels in LegacyColor constructor	frontend/package.json frontend/package-lock.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[sourcery-ai]

We have skipped reviewing this pull request. It seems to have been created by a bot (hey, dependabot[bot]!). We assume it knows what it's doing!

[deepsource-io]

Here's the code health analysis summary for commits 90eee48..ca9f6bf. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
Python	✅ Success		View Check ↗
Docker	✅ Success		View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[codiumai-pr-agent-free]

CI Failure Feedback 🧐

Action: backend-tests

Failed stage: Docker debug [❌]

Failure summary: The action failed because the Docker command docker logs threatmatrix_uwsgi attempted to access a container named threatmatrix_uwsgi, which does not exist. This resulted in an error response from the Docker daemon indicating "No such container: threatmatrix_uwsgi".

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 170: inflating: test_files/urls2.xls 171: ##[group]Run docker ps -a 172: �[36;1mdocker ps -a�[0m 173: �[36;1mdocker logs threatmatrix_uwsgi�[0m 174: �[36;1mdocker logs threatmatrix_daphne�[0m 175: shell: /usr/bin/bash -e {0} 176: ##[endgroup] 177: CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 178: Error response from daemon: No such container: threatmatrix_uwsgi 179: ##[error]Process completed with exit code 1.

---

✨ CI feedback usage guide:

---

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

• Failed stage
• Failed test name
• Failure summary
• Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

• enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
• excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
• enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
• persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
• final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.

[dependabot]

Superseded by #186.