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 7 updates #487

Closed dependabot[bot] closed 1 month ago

dependabot[bot] commented 1 month ago

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

Package From To
@biomejs/biome 1.8.3 1.9.2
@effect/vitest 0.9.2 0.10.5
@types/node 22.5.4 22.7.4
@vitest/coverage-v8 2.0.5 2.1.1
@vitest/ui 2.0.5 2.1.1
lefthook 1.7.15 1.7.18
vitest 2.0.5 2.1.1

Updates @biomejs/biome from 1.8.3 to 1.9.2

Release notes

Sourced from @​biomejs/biome's releases.

CLI v1.9.2

CLI

New features

Bug fixes

  • Fix #3917, where the fixed files were incorrectly computed. Contributed by @​ematipico
  • Fixed an issue that caused GritQL contains queries to report false positives when the matched node appeared inside a sibling node. Contributed by @​arendjr

Editors

Bug fixes

  • Fix #3923. Now the .editorconfig is correctly parsed by the LSP, and the options are correctly applied to files when formatting is triggered. Plus, the Biome LSP now watches for any change to the .editorconfig, and updates the formatting settings.

  • Reduced the number of log files generated by the LSP server. Now the maximum number of logs saved on disk is seven. Contributed by @​ematipico

  • Fix the code actions capabilities available in the LSP Biome server. Before, the LSP was using the default capabilities, which resulted in pulling code actions even when they were disabled by the editor.

    This means that the code actions are pulled by the client only when the editor enables quickfix.biome, source.organizeImports.biome and source.fixAll.biome.

    Now, if you enable organizeImports.enabled: true in the biome.json, and then you configure your editor with the following code action source.organizeImports.biome: false, the editor won't sort the imports.

    Contributed by @​ematipico

Linter

New features

Bug fixes

... (truncated)

Changelog

Sourced from @​biomejs/biome's changelog.

v1.9.2 (2024-09-19)

CLI

New features

Bug fixes

  • Fix #3917, where the fixed files were incorrectly computed. Contributed by @​ematipico
  • Fixed an issue that caused GritQL contains queries to report false positives when the matched node appeared inside a sibling node. Contributed by @​arendjr

Editors

Bug fixes

  • Fix #3923. Now the .editorconfig is correctly parsed by the LSP, and the options are correctly applied to files when formatting is triggered. Plus, the Biome LSP now watches for any change to the .editorconfig, and updates the formatting settings.

  • Reduced the number of log files generated by the LSP server. Now the maximum number of logs saved on disk is seven. Contributed by @​ematipico

  • Fix the code actions capabilities available in the LSP Biome server. Before, the LSP was using the default capabilities, which resulted in pulling code actions even when they were disabled by the editor.

    This means that the code actions are pulled by the client only when the editor enables quickfix.biome, source.organizeImports.biome and source.fixAll.biome.

    Now, if you enable organizeImports.enabled: true in the biome.json, and then you configure your editor with the following code action source.organizeImports.biome: false, the editor won't sort the imports.

    Contributed by @​ematipico

Linter

New features

Bug fixes

... (truncated)

Commits


Updates @effect/vitest from 0.9.2 to 0.10.5

Release notes

Sourced from @​effect/vitest's releases.

@​effect/vitest@​0.10.5

Patch Changes

  • #3689 4d91f41 Thanks @​tim-smart! - add layer api to @effect/vitest

    This allows you to share a Layer between multiple tests, optionally wrapping the tests in a describe block.

    import { expect, layer } from "@effect/vitest"
import { Context, Effect, Layer } from "effect"

    class Foo extends Context.Tag("Foo")<Foo, "foo">() {
static Live = Layer.succeed(Foo, "foo")
}
    

    class Bar extends Context.Tag("Bar")<Bar, "bar">() {
static Live = Layer.effect(
Bar,
Effect.map(Foo, () => "bar" as const)
)
}
    

    layer(Foo.Live)("layer", (it) => {
it.effect("adds context", () =>
Effect.gen(function* () {
const foo = yield* Foo
expect(foo).toEqual("foo")
})
)
    

    it.layer(Bar.Live)("nested", (it) => {
it.effect("adds context", () =>
Effect.gen(function* () {
const foo = yield* Foo
const bar = yield* Bar
expect(foo).toEqual("foo")
expect(bar).toEqual("bar")
})
)
})
})

@​effect/vitest@​0.10.4

Patch Changes

  • Updated dependencies [4509656]:
    • effect@3.8.4
Changelog

Sourced from @​effect/vitest's changelog.

0.10.5

Patch Changes

  • #3689 4d91f41 Thanks @​tim-smart! - add layer api to @effect/vitest

    This allows you to share a Layer between multiple tests, optionally wrapping the tests in a describe block.

    import { expect, layer } from "@effect/vitest"
import { Context, Effect, Layer } from "effect"

    class Foo extends Context.Tag("Foo")<Foo, "foo">() {
static Live = Layer.succeed(Foo, "foo")
}
    

    class Bar extends Context.Tag("Bar")<Bar, "bar">() {
static Live = Layer.effect(
Bar,
Effect.map(Foo, () => "bar" as const)
)
}
    

    layer(Foo.Live)("layer", (it) => {
it.effect("adds context", () =>
Effect.gen(function* () {
const foo = yield* Foo
expect(foo).toEqual("foo")
})
)
    

    it.layer(Bar.Live)("nested", (it) => {
it.effect("adds context", () =>
Effect.gen(function* () {
const foo = yield* Foo
const bar = yield* Bar
expect(foo).toEqual("foo")
expect(bar).toEqual("bar")
})
)
})
})

0.10.4

Patch Changes

... (truncated)

Commits


Updates @types/node from 22.5.4 to 22.7.4

Commits


Updates @vitest/coverage-v8 from 2.0.5 to 2.1.1

Release notes

Sourced from @​vitest/coverage-v8's releases.

v2.1.1

   🐞 Bug Fixes

    View changes on GitHub

v2.1.0

This release makes another big change to the Browser Mode by introducing locators API:

test('renders blog posts', async () => {
  const screen = page.render(<Blog />)

await expect.element(screen.getByRole('heading', { name: 'Blog' })).toBeInTheDocument()


const [firstPost] = screen.getByRole('listitem').all()


await firstPost.getByRole('button', { name: 'Delete' }).click()


expect(screen.getByRole('listitem').all()).toHaveLength(3)
})

You can use either vitest-browser-vue, vitest-browser-svelte or vitest-browser-react to render components and make assertions using locators. Locators are also available on the page object from @vitest/browser/context.

Potential Breaking Change

  • workspace:
    • Correctly resolve workspace globs and file paths  -  by @​sheremet-va in vitest-dev/vitest#6316 (afdcb)
    • This changes how the custom glob pattern in the workspace config is treated. Any file matching the glob is considered a Vitest config file. Any folder matching the glob pattern is treated as a workspace project and is subject to the regular config resolution (single vitest.config.ts or vite.config.ts inside the folder)
    • For example, projects/* will match anything inside the projects folder. If it's a folder, we try to find the config inside that folder (if there is none, it is still treated as a project with the default config). If it's a file, it will be treated as a Vitest config. projects/**/* previously would assume that you only wanted to have folders as projects, but now it will match every single file insideprojects.
    • This change doesn't affect non-glob usage.

   🚀 Features

... (truncated)

Commits
  • 699055e chore: release v2.1.1
  • 9f1fd18 chore: release v2.1.0
  • b2be23e chore: release v2.1.0-beta.7
  • 8ac7011 chore: release v2.1.0-beta.6
  • da52d23 fix(coverage): use project specific vitenode for uncovered files (#6044)
  • 5932a7f feat(coverage): add --exclude-after-remap (#6309)
  • 34199bd feat(browser): support v8 coverage (#6273)
  • 72056b5 chore: release v2.1.0-beta.5
  • 91dea8c fix(coverage): v8 to warn instead of crash when conversion fails (#6318)
  • 1f6cb59 fix(coverage): v8 to support source maps with multiple sources (#6120)
  • Additional commits viewable in compare view


Updates @vitest/ui from 2.0.5 to 2.1.1

Release notes

Sourced from @​vitest/ui's releases.

v2.1.1

   🐞 Bug Fixes

    View changes on GitHub

v2.1.0

This release makes another big change to the Browser Mode by introducing locators API:

test('renders blog posts', async () => {
  const screen = page.render(<Blog />)

await expect.element(screen.getByRole('heading', { name: 'Blog' })).toBeInTheDocument()


const [firstPost] = screen.getByRole('listitem').all()


await firstPost.getByRole('button', { name: 'Delete' }).click()


expect(screen.getByRole('listitem').all()).toHaveLength(3)
})

You can use either vitest-browser-vue, vitest-browser-svelte or vitest-browser-react to render components and make assertions using locators. Locators are also available on the page object from @vitest/browser/context.

Potential Breaking Change

  • workspace:
    • Correctly resolve workspace globs and file paths  -  by @​sheremet-va in vitest-dev/vitest#6316 (afdcb)
    • This changes how the custom glob pattern in the workspace config is treated. Any file matching the glob is considered a Vitest config file. Any folder matching the glob pattern is treated as a workspace project and is subject to the regular config resolution (single vitest.config.ts or vite.config.ts inside the folder)
    • For example, projects/* will match anything inside the projects folder. If it's a folder, we try to find the config inside that folder (if there is none, it is still treated as a project with the default config). If it's a file, it will be treated as a Vitest config. projects/**/* previously would assume that you only wanted to have folders as projects, but now it will match every single file insideprojects.
    • This change doesn't affect non-glob usage.

   🚀 Features

... (truncated)

Commits
  • 699055e chore: release v2.1.1
  • 9f1fd18 chore: release v2.1.0
  • 94a186e fix(ui): render project name consistently (#6329)
  • b2be23e chore: release v2.1.0-beta.7
  • 0223bb7 fix(ui): remove "filters" flickering (#6463)
  • 97773e2 chore: fix edge case in license files bundling (#6460)
  • b78fa88 chore(deps): update dependency @​faker-js/faker to v9 (#6461)
  • c321a3f chore: replace fast-glob with tinyglobby (#6274)
  • b992b34 fix: print unexpected error message if peer dependencies have a different ver...
  • c853126 fix(browser): correctly run in-source tests in the browser (#6440)
  • Additional commits viewable in compare view


Updates lefthook from 1.7.15 to 1.7.18

Release notes

Sourced from lefthook's releases.

v1.7.18

Changelog

  • 2eb8d43fcdfc47f647727becd7c130e13b80bfea deps: September 2024 (#829)
  • 9be9ab0e7499dde6b38e008d2078a3eb291f707a fix: force remote name origin when using remotes (#830)

v1.7.17

Changelog

  • 6383ff38f936d08a70769d0fab73c6ef3eca45eb feat: skip LFS hooks when pre-push hook is skipped (#818)

v1.7.16

Changelog

  • eb24c87bc72f72a2dd1b614a5685094bd1d63d20 chore: enhance some code parts (#824)
  • 3daab42c2fd0334e3134672d741c63068cc122dd fix: quote script path (#823)
Changelog

Sourced from lefthook's changelog.

1.7.18 (2024-09-30)

1.7.17 (2024-09-26)

1.7.16 (2024-09-23)

Commits
  • 3291e7d 1.7.18: set origin when cloning remotes and ignore defaultRemoteName setting
  • 9be9ab0 fix: force remote name origin when using remotes (#830)
  • 2eb8d43 deps: September 2024 (#829)
  • e4d5cd2 1.7.17: skip LFS hooks when hook is skipped by config
  • 6383ff3 feat: skip LFS hooks when pre-push hook is skipped (#818)
  • 6858ccb 1.7.16: allow spaces in project name when using scripts
  • eb24c87 chore: enhance some code parts (#824)
  • 3daab42 fix: quote script path (#823)
  • 76cf1a0 docs: fix typo for command names in configuration.md (#814)
  • See full diff in compare view


Updates vitest from 2.0.5 to 2.1.1

Release notes

Sourced from vitest's releases.

v2.1.1

   🐞 Bug Fixes

    View changes on GitHub

v2.1.0

This release makes another big change to the Browser Mode by introducing locators API:

test('renders blog posts', async () => {
  const screen = page.render(<Blog />)

await expect.element(screen.getByRole('heading', { name: 'Blog' })).toBeInTheDocument()


const [firstPost] = screen.getByRole('listitem').all()


await firstPost.getByRole('button', { name: 'Delete' }).click()


expect(screen.getByRole('listitem').all()).toHaveLength(3)
})

You can use either vitest-browser-vue, vitest-browser-svelte or vitest-browser-react to render components and make assertions using locators. Locators are also available on the page object from @vitest/browser/context.

Potential Breaking Change

  • workspace:
    • Correctly resolve workspace globs and file paths  -  by @​sheremet-va in vitest-dev/vitest#6316 (afdcb)
    • This changes how the custom glob pattern in the workspace config is treated. Any file matching the glob is considered a Vitest config file. Any folder matching the glob pattern is treated as a workspace project and is subject to the regular config resolution (single vitest.config.ts or vite.config.ts inside the folder)
    • For example, projects/* will match anything inside the projects folder. If it's a folder, we try to find the config inside that folder (if there is none, it is still treated as a project with the default config). If it's a file, it will be treated as a Vitest config. projects/**/* previously would assume that you only wanted to have folders as projects, but now it will match every single file insideprojects.
    • This change doesn't affect non-glob usage.

   🚀 Features

... (truncated)

Commits
  • 699055e chore: release v2.1.1
  • 36b5ace fix(workspace): resolve glob pattern once to avoid name collision (#6489)
  • 16aa76c fix(browser): make example test callbacks async (#6484)
  • 9f1fd18 chore: release v2.1.0
  • 94a186e fix(ui): render project name consistently (#6329)
  • ac698b1 fix: expect.getState().testPath always returns correct path (#6472)
  • b2be23e chore: release v2.1.0-beta.7
  • 0b44722 fix: ignore importer when resolving Vitest (#6469)
  • 97773e2 chore: fix edge case in license files bundling (#6460)
  • 7ab0f4a feat(browser): support --inspect-brk (#6434)
  • 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 1 month ago

Superseded by #488.