search

SchizzY / next-month-web

https://next-month-web.vercel.app
2 stars 0 forks source link

npm: bump the dev-deps group with 3 updates #59

Closed dependabot[bot] closed 4 months ago

dependabot[bot] commented 4 months ago

Bumps the dev-deps group with 3 updates: @biomejs/biome, @types/node and postcss.

Updates @biomejs/biome from 1.8.2 to 1.8.3

Release notes

Sourced from @​biomejs/biome's releases.

CLI v1.8.3

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

... (truncated)

Changelog

Sourced from @​biomejs/biome's changelog.

v1.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

Commits


Updates @types/node from 20.14.8 to 20.14.9

Commits


Updates postcss from 8.4.38 to 8.4.39

Release notes

Sourced from postcss's releases.

8.4.39

Changelog

Sourced from postcss's changelog.

8.4.39

Commits


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 ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions
dependabot[bot] commented 4 months ago

Dependabot tried to add @octocat, @christoff-linde, @SchizzY and @seanloock as reviewers to this PR, but received the following error from GitHub:

POST https://api.github.com/repos/SchizzY/next-month-web/pulls/59/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 SchizzY/next-month-web repository. // See: https://docs.github.com/rest/pulls/review-requests#request-reviewers-for-a-pull-request
vercel[bot] commented 4 months ago

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

Name Status Preview Comments Updated (UTC)
next-month-web ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 1, 2024 5:35am
dependabot[bot] commented 4 months ago

Looks like these dependencies are updatable in another way, so this is no longer needed.