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.

Sign up for GitHub

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

Jump to bottom

[Snyk] Upgrade: , , vitest #9

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

[Snyk] Upgrade: , , vitest #9

wants to merge 1 commit into from

Conversation

Ramyromel
Copy link
Owner

snyk-top-banner

Snyk has created this PR to upgrade multiple dependencies.

👯 The following dependencies are linked and will therefore be updated together.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

⚠️ Warning: This PR contains major version upgrade(s), and may be a breaking change.

Name Versions Released on

@biomejs/biome
from 1.5.3 to 1.8.3 | 18 versions ahead of your current version | 3 months ago
on 2024-06-27
@total-typescript/ts-reset
from 0.5.1 to 0.6.0 | 1 version ahead of your current version | 22 days ago
on 2024-08-24
vitest
from 1.6.0 to 2.0.5 | 18 versions ahead of your current version
⚠️ This is a major version upgrade, and may be a breaking change | a month ago
on 2024-07-31

Release notes
Package name: @biomejs/biome
  • 1.8.3 - 2024-06-27

    CLI

    Bug fixes

    • Fix #3104 by suppressing node warnings when using biome migrate. Contributed by @ SuperchupuDev

    • Force colors to be off when using the GitHub reporter to properly create annotations in GitHub actions (#3148). Contributed by @ Sec-ant

    Parser

    Bug fixes

    Formatter

    Bug fixes

    Linter

    New features

    Bug fixes

    • useConsistentArrayType and useShorthandArrayType now ignore Array in the extends and implements clauses. Fix #3247. Contributed by @ Conaclos
    • Fixes #3066 by taking into account the dependencies declared in the package.json. Contributed by @ ematipico
    • The code action of the useArrowFunction rule now preserves a trailing comma when there is only a single type parameter in the arrow function and JSX is enabled. Fixes #3292. Contributed by @ Sec-ant

    Enhancements

    • Enhance tailwind sorting lint rule #1274 with variant support.

      Every preconfigured variant is assigned a weight that concurs on establishing the output sorting order.
      Since nesting variants on the same utility class is possible, the resulting weight is the Bitwise XOR of all the variants weight for that class.
      Dynamic variants (e.g. has-[.custom-class], group-[:checked]) are also supported and they take the weight of their base variant name the custom value attached (e.g. has-[.custom-class] takes has weight).
      Arbitrary variants (e.g. [&nth-child(2)]) don't have a weight assigned and they are placed after every known variant.
      Classes with the same amount of arbitrary variants follow lexicographical order. The class that has the highest number of nested arbitrary variants is placed last.
      Screen variants (e.g. sm:, max-md:, min-lg:) are not supported yet.

      Contributed by @ lutaok

    What's Changed

    Other changes

    • feat(workspace): adds GraphQL parsing capabilities via feature by @ ematipico in #3238
    • feat(editorconfig): expand unknown globs into known globs by @ dyc3 in #3218
    • chore(core): implement pull_diagnostics for graphql by @ ematipico in #3248
    • chore(linter): add a rule source of noUnknownProperty by @ togami2864 in #3252
    • feat: tailwind variant sorting by @ lutaok in #3208
    • test(parse/json): add test for bug where overrides erroneously override special parsing options by @ dyc3 in #3260
    • docs(analyzer): improve contributing guide for rules with multiple signals by @ minht11 in #3245
    • chore(lint): initialise biome_graphql_analyze by @ ematipico in #3276
    • chore(deps): update @ biomejs packages by @ renovate in #3266
    • docs(useNamingConvention): add examples and improve explanations by @ Conaclos in #3277
    • refactor(parse/json): change fields in JsonParserSettings to Option by @ dyc3 in #3272
    • feat(search-output-formatter): initialize search output formatter by @ BackupMiles in #3258
    • chore(grit): implement node-like compilers + fixes by @ arendjr in #3253
    • feat: enable linting for graphql by @ ematipico in #3295
    • refactor(parse/css): change fields in CssParserSettings to Option by @ dyc3 in #3273
    • refactor: add variables to format strings directly by @ hamirmahal in #3299
    • chore: update codegen to include GraphQL by @ ematipico in #3301

    New Contributors

    Full Changelog: cli/v1.8.2...cli/v1.8.3

  • 1.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" }
        }
      }
    }, {
      "include": ["index.js"],
      "linter": {
        "rules": {
          "suspicious": { "noDoubleEquals": "off" }
        }
      }
    }
  ]
}

      The rule is now correctly enabled for the index.js file.

      Contributed by @ Conaclos

    Formatter

    Bug fixes

    • Fix #3103 by correctly resolving CSS formatter options. Contributed by @ ah-yu
    • Fix #3192 don't add an extra whitespace within :has. Contributed by @ denbezrukov

    JavaScript APIs

    Bug fixes

    • Fix a regression introduced by the release of v1.8.0

    Linter

    New features

    Bug fixes

    • Add nursery/noShorthandPropertyOverrides. #2958 Contributed by @ neokidev

    • Fix [#3084] false positive by correctly recognize parenthesized return statement. Contributed by @ unvalley

    • useImportExtensions now suggests a correct fix for import '.' and import './.'. Contributed by @ minht11

    • Fix useDateNow false positive when new Date object has arguments new Date(0).getTime(). Contributed by @ minht11.

    • The noUnmatchableAnbSelector rule is now able to catch unmatchable an+b selectors like 0n+0 or -0n+0. Contributed by @ Sec-ant.

    • The useHookAtTopLevel rule now recognizes properties named as hooks like foo.useFoo(). Contributed by @ ksnyder9801

    • Fix #3092, prevent warning for Custom properties (--*). Contributed by @ chansuke

    • Fix a false positive in the useLiteralKeys rule. (#3160)

      This rule now ignores the following kind of computed member name:

      const a = {
  [`line1
  line2`]: true,
};

      Contributed by @ Sec-ant

    • The noUnknownProperty rule now ignores the composes property often used in css modules. #3000 Contributed by @ chansuke

    • Fix false positives of the useExhaustiveDependencies rule.

      The component itself is considered stable when it is used recursively inside a hook closure defined inside of it:

      import { useMemo } from "react";

      function MyRecursiveComponent() {
      // MyRecursiveComponent is stable, we don't need to add it to the dependencies list.
      const children = useMemo(() => <MyRecursiveComponent />, []);
      return <div>{children}</div>;
      }

      Also, export default function and export default class are considered stable now because they can only appear at the top level of a module.

      Contributed by @ Sec-ant

    • Fix missing withDefaults macro in vue files for globals variables. Contributed by @ Shyam-Chen

    Parser

    Bug fixes

    What's Changed

    Other changes

    New Contributors

    Full Changelog: cli/v1.8.1...cli/v1.8.2

  • 1.8.1 - 2024-06-10
  • 1.8.0 - 2024-06-04
  • 1.7.4-nightly.125f34b - 2024-05-23
  • 1.7.3 - 2024-05-06
  • 1.7.3-nightly.d74b584 - 2024-05-09
  • 1.7.3-nightly.af70ac2 - 2024-05-23
  • 1.7.2 - 2024-04-30
  • 1.7.1 - 2024-04-22
  • 1.7.0 - 2024-04-15
  • 1.6.4 - 2024-04-03
  • 1.6.4-nightly.abab451 - 2024-04-10
  • 1.6.4-nightly.a995ada - 2024-04-06
  • 1.6.3 - 2024-03-25
  • 1.6.2 - 2024-03-22
  • 1.6.1 - 2024-03-12
  • 1.6.0 - 2024-03-08
  • 1.5.3 - 2024-01-22
from @biomejs/biome GitHub release notes
Package name: @total-typescript/ts-reset
  • 0.6.0 - 2024-08-24
  • 0.5.1 - 2023-08-17
from @total-typescript/ts-reset GitHub release notes
Package name: vitest

@snyk-bot
feat: upgrade multiple dependencies with Snyk
604ff0b 
Snyk has created this PR to upgrade:
  - @biomejs/biome from 1.5.3 to 1.8.3.
    See this package in npm: https://www.npmjs.com/package/@biomejs/biome
  - @total-typescript/ts-reset from 0.5.1 to 0.6.0.
    See this package in npm: https://www.npmjs.com/package/@total-typescript/ts-reset
  - vitest from 1.6.0 to 2.0.5.
    See this package in npm: https://www.npmjs.com/package/vitest

See this project in Snyk:
https://app.snyk.io/org/ramyromel/project/ad6f6f75-d99c-4c4c-a0db-59f98f4a302b?utm_source=github&utm_medium=referral&page=upgrade-pr
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
2 participants
@Ramyromel @snyk-bot