search

ccntrq / git-jira-branch

Manage branches for your Jira tickets
https://www.npmjs.com/package/git-jira-branch
MIT License
11 stars 2 forks source link

chore(deps-dev): bump the development-dependencies group across 1 directory with 5 updates #394

Closed dependabot[bot] closed 4 months ago

dependabot[bot] commented 4 months ago

Bumps the development-dependencies group with 5 updates in the / directory:

Package From To
@biomejs/biome 1.8.0 1.8.3
@effect/vitest 0.5.8 0.6.1
@types/node 20.14.2 20.14.10
rimraf 5.0.7 5.0.8
typescript 5.4.5 5.5.3

Updates @biomejs/biome from 1.8.0 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

Enhancements

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.

... (truncated)

Commits


Updates @effect/vitest from 0.5.8 to 0.6.1

Release notes

Sourced from @​effect/vitest's releases.

@​effect/vitest@​0.6.1

Patch Changes

  • Updated dependencies [a5737d6]:
    • effect@3.4.7

@​effect/vitest@​0.6.0

Minor Changes

  • #3122 489d20a Thanks @​sukovanej! - Refactor @effect/vitest package.

    • Clear separation of the public API and internals.
    • Fix type of scoped, live, scopedLive and effect objects. Make sure skip and only are available.
    • Add each method to scoped, live, scopedLive and effect objects.

    Example usage

    import { expect, it } from "@effect/vitest";
import { Effect } from "effect";

    it.scoped.skip("test skipped", () =>
Effect.acquireRelease(Effect.die("skipped anyway"), () => Effect.void),
);
    

    it.effect.each([1, 2, 3])("effect each %s", (n) =>
Effect.sync(() => expect(n).toEqual(n)),
);

Patch Changes

Changelog

Sourced from @​effect/vitest's changelog.

0.6.1

Patch Changes

  • Updated dependencies [a5737d6]:
    • effect@3.4.7

0.6.0

Minor Changes

  • #3122 489d20a Thanks @​sukovanej! - Refactor @effect/vitest package.

    • Clear separation of the public API and internals.
    • Fix type of scoped, live, scopedLive and effect objects. Make sure skip and only are available.
    • Add each method to scoped, live, scopedLive and effect objects.

    Example usage

    import { expect, it } from "@effect/vitest";
import { Effect } from "effect";

    it.scoped.skip("test skipped", () =>
Effect.acquireRelease(Effect.die("skipped anyway"), () => Effect.void),
);
    

    it.effect.each([1, 2, 3])("effect each %s", (n) =>
Effect.sync(() => expect(n).toEqual(n)),
);

Patch Changes

0.5.21

Patch Changes

  • Updated dependencies [a047af9]:
    • effect@3.4.5

0.5.20

Patch Changes

... (truncated)

Commits


Updates @types/node from 20.14.2 to 20.14.10

Commits


Updates rimraf from 5.0.7 to 5.0.8

Commits


Updates typescript from 5.4.5 to 5.5.3

Release notes

Sourced from typescript's releases.

TypeScript 5.5.3

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

TypeScript 5.5

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

TypeScript 5.5 RC

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

TypeScript 5.5 Beta

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

... (truncated)

Commits
  • f0e9921 Bump version to 5.5.3 and LKG
  • 738bd60 Cherry-pick #58966 to release-5.5 (#59002)
  • ce2e60e Update LKG
  • f3b21a2 🤖 Pick PR #58931 (Defer creation of barebonesLibSourc...) into release-5.5 (#...
  • 7b1620b 🤖 Pick PR #58811 (fix(58801): "Move to file" on globa...) into release-5.5 (#...
  • 5367ae1 Bump version to 5.5.2 and LKG
  • 02132e5 🤖 Pick PR #58895 (Fix global when typescript.js loade...) into release-5.5 (#...
  • 45b1e3c 🤖 Pick PR #58872 (Fix declaration emit crash) into release-5.5 (#58874)
  • 17933ee 🤖 Pick PR #58810 (Fixed declaration emit issue relate...) into release-5.5 (#...
  • 552b07e 🤖 Pick PR #58786 (Fixed declaration emit crash relate...) into release-5.5 (#...
  • 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 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

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