chore(deps-dev): bump @biomejs/biome from 1.8.1 to 1.8.2

[dependabot]

Bumps @biomejs/biome from 1.8.1 to 1.8.2.

Release notes

Sourced from @​biomejs/biome's releases.

CLI v1.8.2

CLI

Bug fixes

• Fix #3201 by correctly injecting the source code of the file when printing the diagnostics. Contributed by @​ematipico
• Fix #3179 where comma separators are not correctly removed after running biome migrate and thus choke the parser. Contributed by @​Sec-ant
• Fix #3232 by correctly using the colors set by the user. Contributed by @​ematipico

Enhancement

• Reword the reporter message No fixes needed to No fixes applied.

  The former message is misleading when there're still errors or warnings in the files that should be taken care of manually. For example:

  Checked 2 files in <TIME>. No fixes needed.
  Found 2 errors.
  

  The new message suits better in these cases.

  Contributed by @​Sec-ant

Configuration

Bug fixes

• Don't conceal previous overrides (#3176).

  Previously, each override inherited the unset configuration of the base configuration. This means that setting a configuration in an override can be concealed by a subsequent override that inherits of the value from the base configuration.

  For example, in the next example, noDebugger was disabled for the index.js file.

  {
    "linter": {
      "rules": {
        "suspicious": { "noDebugger": "off" }
      }
    },
    "overrides": [
      {
        "include": ["index.js"],
        "linter": {
          "rules": {
            "suspicious": { "noDebugger": "warn" }
          }
        }

... (truncated)

Changelog

Sourced from @​biomejs/biome's changelog.

v1.8.2 (2024-06-20)

CLI

Bug fixes

• Fix #3201 by correctly injecting the source code of the file when printing the diagnostics. Contributed by @​ematipico
• Fix #3179 where comma separators are not correctly removed after running biome migrate and thus choke the parser. Contributed by @​Sec-ant
• Fix #3232 by correctly using the colors set by the user. Contributed by @​ematipico

Enhancement

• Reword the reporter message No fixes needed to No fixes applied.

  The former message is misleading when there're still errors or warnings in the files that should be taken care of manually. For example:

  Checked 2 files in <TIME>. No fixes needed.
  Found 2 errors.
  

  The new message suits better in these cases.

  Contributed by @​Sec-ant

Configuration

Bug fixes

• Don't conceal previous overrides (#3176).

  Previously, each override inherited the unset configuration of the base configuration. This means that setting a configuration in an override can be concealed by a subsequent override that inherits of the value from the base configuration.

  For example, in the next example, noDebugger was disabled for the index.js file.

  {
    "linter": {
      "rules": {
        "suspicious": { "noDebugger": "off" }
      }
    },
    "overrides": [
      {
        "include": ["index.js"],
        "linter": {
          "rules": {
            "suspicious": { "noDebugger": "warn" }
          }

... (truncated)

Commits

• 54b4c9a release: v1.8.2 (#3243)
• 6f8cab7 feat(biome_css_analyzer): implement function-linear-gradient-no-nonstandard-d...
• 0d9b60a feat(lint/useValidAutocomplete): add rule (#3143)
• 9d518d8 chore(deps): update @​biomejs packages (#3145)
• 4a7baaa feat(biome_js_analyzer): noSubstr (#3125)
• 535acc7 fix(ci): rule check error messages (#3158)
• See full diff 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)

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Install scripts	npm/@biomejs/[email protected]	Install script: postinstall Source: node scripts/postinstall.js	orphan: npm/@biomejs/[email protected]	🚫
Install scripts	npm/@biomejs/[email protected]	Install script: postinstall Source: node scripts/postinstall.js	orphan: npm/@biomejs/[email protected]	🚫

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/@biomejs/[email protected]
• @SocketSecurity ignore npm/@biomejs/[email protected]