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

Bump the minor group across 1 directory with 15 updates #1384

Closed
wants to merge 1 commit into from
Closed

Bump the minor group across 1 directory with 15 updates #1384

wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Sep 1, 2024 •
edited
Loading

Bumps the minor group with 15 updates in the / directory:

Package From To
@zip.js/zip.js 2.7.45 2.7.52
@codspeed/vitest-plugin 3.1.0 3.1.1
@playwright/test 1.44.1 1.46.1
@types/chrome 0.0.268 0.0.270
@types/firefox-webext-browser 120.0.3 120.0.4
ajv 8.14.0 8.17.1
esbuild 0.21.4 0.23.1
eslint-plugin-vitest 0.3.22 0.5.4
html-validate 8.19.1 8.21.0
husky 9.0.11 9.1.5
lint-staged 15.2.5 15.2.9
prettier 3.2.5 3.3.3
stylelint 16.6.1 16.9.0
stylelint-config-recommended 14.0.0 14.0.1
typescript 5.4.5 5.5.4

Updates @zip.js/zip.js from 2.7.45 to 2.7.52

Release notes

Sourced from @​zip.js/zip.js's releases.

v2.7.52

  • Added option compressionMethod in ZipWriter for handling custom compression methods (e.g. zstd) when setting the option passThrough to true
  • Fixed issue with Uint8Array size in ZipReader when setting passThrough to true and using a Uint8Writer class to get the uncompressed data
  • Fixed optional checkPasswordOnly property in the type definitions (index.d.ts)

v2.7.51

  • Fixed issue when passing passThrough: true option in the import* methods of the FS API with AES-encrypted files where the encryption strength is not set to the default value (i.e. 3)

v2.7.50

  • Added the new option passThrough in ZipReader, ZipWriter, and ZipDirectoryEntry#import methods. This allows reading/writing directly the raw data of zip entries without processing it (i.e. compressing or/and encrypting data)
  • Added the new option offset in ZipWriter. This allows setting the offset of the first entry in the file to a value > 0. This can be useful when creating zip files with prepended data
  • Completed the implementation of the bitFlag property in ZipWriter. It will now take into account the level of compression and update the bit flag value accordingly.
  • Updated dev dependencies

v2.7.48

What's Changed

New Contributors

Full Changelog: gildas-lormeau/zip.js@v2.7.47...v2.7.48

v2.7.47

Fixed regression introduced in the previous version (see #520)

v2.7.46

Added the export ./data-uri in order to support Web Workers loaded with a data URI instead of a Blob URI (see #519)

Commits

Updates @codspeed/vitest-plugin from 3.1.0 to 3.1.1

Release notes

Sourced from @​codspeed/vitest-plugin's releases.

v3.1.1

What's Changed

Full Changelog: CodSpeedHQ/codspeed-node@v3.1.0...v3.1.1

Commits

Updates @playwright/test from 1.44.1 to 1.46.1

Release notes

Sourced from @​playwright/test's releases.

v1.46.1

Highlights

microsoft/playwright#32004 - [REGRESSION]: Client Certificates don't work with Microsoft IIS microsoft/playwright#32004 - [REGRESSION]: Websites stall on TLS handshake errors when using Client Certificates microsoft/playwright#32146 - [BUG]: Credential scanners warn about internal socks-proxy TLS certificates microsoft/playwright#32056 - [REGRESSION]: 1.46.0 (TypeScript) - custom fixtures extend no longer chainable microsoft/playwright#32070 - [Bug]: --only-changed flag and project dependencies microsoft/playwright#32188 - [Bug]: --only-changed with shallow clone throws "unknown revision" error

Browser Versions

  • Chromium 128.0.6613.18
  • Mozilla Firefox 128.0
  • WebKit 18.0

This version was also tested against the following stable channels:

  • Google Chrome 127
  • Microsoft Edge 127

v1.46.0

TLS Client Certificates

Playwright now allows to supply client-side certificates, so that server can verify them, as specified by TLS Client Authentication.

When client certificates are specified, all browser traffic is routed through a proxy that establishes the secure TLS connection, provides client certificates to the server and validates server certificates.

The following snippet sets up a client certificate for https://example.com:

import { defineConfig } from '@playwright/test';
export default defineConfig({
// ...
use: {
clientCertificates: [{
origin: 'https://example.com',
certPath: './cert.pem',
keyPath: './key.pem',
passphrase: 'mysecretpassword',
}],
},
// ...
});

You can also provide client certificates to a particular test project or as a parameter of browser.newContext() and apiRequest.newContext().

--only-changed cli option

New CLI option --only-changed allows to only run test files that have been changed since the last git commit or from a specific git "ref".

... (truncated)

Commits
  • e1c861c cherry-pick(#32021): test: fix failing client-certificate tests
  • 20b0788 chore: mark v1.46.1 (#32194)
  • 57c3240 cherry-pick(#32192): chore: generate self-signed certificates for socks proxy
  • 301f179 cherry-pick(#32189): fix(only-changed): show nice error message about shallow...
  • b2d6a09 cherry-pick(#32164): docs: release video and trace viewer video (#32173)
  • 7cf7aec cherry-pick(#32094): fix(test runner): run project dependencies of `--only-ch...
  • d78ae01 cherry-pick(#32163): fix(client-certificates): stall on tls handshake errors
  • bd13da4 cherry-pick(#32155): fix(client-certificates): when server does tls renegotia...
  • 30684a7 cherry-pick(#32066): fix(types): revert type changes made to support TS 5.5 (...
  • 5e68061 cherry-pick(#32015): docs(release-notes): fix typo in .NET release notes
  • Additional commits viewable in compare view

Updates @types/chrome from 0.0.268 to 0.0.270

Commits

Updates @types/firefox-webext-browser from 120.0.3 to 120.0.4

Commits

Updates ajv from 8.14.0 to 8.17.1

Release notes

Sourced from ajv's releases.

v8.17.1

What's Changed

Full Changelog: ajv-validator/ajv@v8.17.0...v8.17.1

Plus everything in 8.17.0 which failed to release

The only functional change is to switch from uri-js (which is no longer supported), to fast-uri. This is the second attempt and the team on fast-uri have been really helpful addressing the issues we found last time.

Revert "Revert fast-uri change (ajv-validator/ajv#2444)" by @​gurgunday in ajv-validator/ajv#2448 fix: ignore new eslint error for @​typescript-eslint/no-extraneous-class by @​jasoniangreen in ajv-validator/ajv#2455 docs: clarify behaviour of addVocabulary by @​jasoniangreen in ajv-validator/ajv#2454 docs: refactor to improve legibility by @​blottn in ajv-validator/ajv#2432 Fix grammatical typo in managing-schemas.md by @​wetneb in ajv-validator/ajv#2305 docs: Fix broken strict-mode link by @​alexanderjsx in ajv-validator/ajv#2459 feat: add test for encoded refs and bump fast-uri by @​jasoniangreen in ajv-validator/ajv#2449 fix: changes for @​typescript-eslint/array-type rule by @​jasoniangreen in ajv-validator/ajv#2467 fixes ajv-validator/ajv#2217 - clarify custom keyword naming by @​jasoniangreen in ajv-validator/ajv#2457

v8.17.0

What's Changed

The only functional change is to switch from uri-js (which is no longer supported), to fast-uri. This is the second attempt and the team on fast-uri have been really helpful addressing the issues we found last time.

New Contributors

Full Changelog: ajv-validator/ajv@v8.16.0...v8.17.0

v8.16.0

What's Changed

Full Changelog: ajv-validator/ajv@v8.15.0...v8.16.0

... (truncated)

Commits

Updates esbuild from 0.21.4 to 0.23.1

Release notes

Sourced from esbuild's releases.

v0.23.1

  • Allow using the node: import prefix with es* targets (#3821)

    The node: prefix on imports is an alternate way to import built-in node modules. For example, import fs from "fs" can also be written import fs from "node:fs". This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with --target=node14 so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as --target=node18,es2022 removes the node: prefix because none of the es* targets are known to support this feature. This release adds the support for the node: flag to esbuild's internal compatibility table for es* to allow you to use compound targets like this:

    // Original code
import fs from 'node:fs'
fs.open
// Old output (with --bundle --format=esm --platform=node --target=node18,es2022)
import fs from "fs";
fs.open;
// New output (with --bundle --format=esm --platform=node --target=node18,es2022)
import fs from "node:fs";
fs.open;

  • Fix a panic when using the CLI with invalid build flags if --analyze is present (#3834)

    Previously esbuild's CLI could crash if it was invoked with flags that aren't valid for a "build" API call and the --analyze flag is present. This was caused by esbuild's internals attempting to add a Go plugin (which is how --analyze is implemented) to a null build object. The panic has been fixed in this release.

  • Fix incorrect location of certain error messages (#3845)

    This release fixes a regression that caused certain errors relating to variable declarations to be reported at an incorrect location. The regression was introduced in version 0.18.7 of esbuild.

  • Print comments before case clauses in switch statements (#3838)

    With this release, esbuild will attempt to print comments that come before case clauses in switch statements. This is similar to what esbuild already does for comments inside of certain types of expressions. Note that these types of comments are not printed if minification is enabled (specifically whitespace minification).

  • Fix a memory leak with pluginData (#3825)

    With this release, the build context's internal pluginData cache will now be cleared when starting a new build. This should fix a leak of memory from plugins that return pluginData objects from onResolve and/or onLoad callbacks.

v0.23.0

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.22.0 or ~0.22.0. See npm's documentation about semver for more information.

  • Revert the recent change to avoid bundling dependencies for node (#3819)

    This release reverts the recent change in version 0.22.0 that made --packages=external the default behavior with --platform=node. The default is now back to --packages=bundle.

    I've just been made aware that Amazon doesn't pin their dependencies in their "AWS CDK" product, which means that whenever esbuild publishes a new release, many people (potentially everyone?) using their SDK around the world instantly starts using it without Amazon checking that it works first. This change in version 0.22.0 happened to break their SDK. I'm amazed that things haven't broken before this point. This revert attempts to avoid these problems for Amazon's customers. Hopefully Amazon will pin their dependencies in the future.

    In addition, this is probably a sign that esbuild is used widely enough that it now needs to switch to a more complicated release model. I may have esbuild use a beta channel model for further development.

  • Fix preserving collapsed JSX whitespace (#3818)

    When transformed, certain whitespace inside JSX elements is ignored completely if it collapses to an empty string. However, the whitespace should only be ignored if the JSX is being transformed, not if it's being preserved. This release fixes a bug where esbuild was previously incorrectly ignoring collapsed whitespace with --jsx=preserve. Here is an example:

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.23.1

  • Allow using the node: import prefix with es* targets (#3821)

    The node: prefix on imports is an alternate way to import built-in node modules. For example, import fs from "fs" can also be written import fs from "node:fs". This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with --target=node14 so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as --target=node18,es2022 removes the node: prefix because none of the es* targets are known to support this feature. This release adds the support for the node: flag to esbuild's internal compatibility table for es* to allow you to use compound targets like this:

    // Original code
import fs from 'node:fs'
fs.open
// Old output (with --bundle --format=esm --platform=node --target=node18,es2022)
import fs from "fs";
fs.open;
// New output (with --bundle --format=esm --platform=node --target=node18,es2022)
import fs from "node:fs";
fs.open;

  • Fix a panic when using the CLI with invalid build flags if --analyze is present (#3834)

    Previously esbuild's CLI could crash if it was invoked with flags that aren't valid for a "build" API call and the --analyze flag is present. This was caused by esbuild's internals attempting to add a Go plugin (which is how --analyze is implemented) to a null build object. The panic has been fixed in this release.

  • Fix incorrect location of certain error messages (#3845)

    This release fixes a regression that caused certain errors relating to variable declarations to be reported at an incorrect location. The regression was introduced in version 0.18.7 of esbuild.

  • Print comments before case clauses in switch statements (#3838)

    With this release, esbuild will attempt to print comments that come before case clauses in switch statements. This is similar to what esbuild already does for comments inside of certain types of expressions. Note that these types of comments are not printed if minification is enabled (specifically whitespace minification).

  • Fix a memory leak with pluginData (#3825)

    With this release, the build context's internal pluginData cache will now be cleared when starting a new build. This should fix a leak of memory from plugins that return pluginData objects from onResolve and/or onLoad callbacks.

0.23.0

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.22.0 or ~0.22.0. See npm's documentation about semver for more information.

  • Revert the recent change to avoid bundling dependencies for node (#3819)

    This release reverts the recent change in version 0.22.0 that made --packages=external the default behavior with --platform=node. The default is now back to --packages=bundle.

    I've just been made aware that Amazon doesn't pin their dependencies in their "AWS CDK" product, which means that whenever esbuild publishes a new release, many people (potentially everyone?) using their SDK around the world instantly starts using it without Amazon checking that it works first. This change in version 0.22.0 happened to break their SDK. I'm amazed that things haven't broken before this point. This revert attempts to avoid these problems for Amazon's customers. Hopefully Amazon will pin their dependencies in the future.

    In addition, this is probably a sign that esbuild is used widely enough that it now needs to switch to a more complicated release model. I may have esbuild use a beta channel model for further development.

  • Fix preserving collapsed JSX whitespace (#3818)

... (truncated)

Commits

Updates eslint-plugin-vitest from 0.3.22 to 0.5.4

Release notes

Sourced from eslint-plugin-vitest's releases.

v0.5.4

Features

  • support old Eslint configuration
  • update dependencies

v0.5.3

Bug Fixes

v0.5.2

Features

v0.5.1

Bug Fixes

  • no-focused-tests: support .each template strings (#420) (36e5b9a)

v0.5.0

‼️ Breaking Change 🚨

This version only supports new eslint flat config!

If you run into issues, consider downgrading and opening an issue. Remember to include a minimum repro example to help me fix issues quickly!

Full Changelog: vitest-dev/eslint-plugin-vitest@v0.5.0...v0.5.0

v0.4.2-beta.5

No release notes provided.

v0.4.2-beta.4

Bug Fixes

v0.4.2-beta.3

Features

... (truncated)

Commits

Updates html-validate from 8.19.1 to 8.21.0

Release notes

Sourced from html-validate's releases.

v8.21.0

8.21.0 (2024-07-20)

Features

  • api: add DOMTree.readyState (1f6f69b)
  • api: deprecate DOMTree.find(..) in favour of querySelector(..) (ac0bb77)
  • api: internal methods of DOMTree removed from public API (79a03be)
  • api: new walk.depthFirst(..) API to replace now deprecated DOMTree.visitDepthFirst(..) method (f9dbda0)

Bug Fixes

  • html5: spellcheck is a global attribute (46594a1)

v8.20.1

8.20.1 (2024-06-11)

Bug Fixes

  • rules: fix attribute-allowed-values error location for empty values (2c04eeb)

v8.20.0

8.20.0 (2024-06-02)

Features

  • api: new setConfig method on StaticConfigLoader to change config (1bf7559)
  • api: new getter/setter for configuration loader (6283091)
Commits
  • 5575f6f chore(release): 8.21.0
  • 40b32da Merge branch 'renovate/ts-jest-29.x' into 'master'
  • 77135de chore(deps): update dependency ts-jest to v29.2.3
  • 3a7611e Merge branch 'renovate/npm-pkg-lint-3.x' into 'master'
  • a59825f chore(deps): update dependency npm-pkg-lint to v3.6.5
  • 996249d Merge branch 'renovate/node-16.x' into 'master'
  • 06eb36c chore(deps): update dependency @​types/node to v16.18.103
  • 8c6722f Merge branch 'renovate/husky-9.x' into 'master'
  • 2f95544 chore(deps): update dependency husky to v9.1.1
  • 6ee546b chore(deps): update dependency husky to v9.1.0
  • Additional commits viewable in compare view

Updates husky from 9.0.11 to 9.1.5

Release notes

Sourced from husky's releases.

v9.1.5

What's Changed

New Contributors

Full Changelog: typicode/husky@v9.1.4...v9.1.5

v9.1.4

  • Improve deprecation notice

v9.1.3

  • fix: better handle space in PATH

v9.1.2

Show a message instead of automatically removing deprecated code.

This only concerns projects that still have the following code in their hooks:

- #!/usr/bin/env sh # <- This is deprecated, remove it
- . "$(dirname -- "$0")/_/husky.sh"  # <- This is deprecated, remove it
Rest of your hook code

Hooks with these lines will fail in v10.0.0

v9.1.1

Super saiyan god dog! It's over 9.0.0!

What's new

You can now run package commands directly, no need for npx or equivalents. It makes writing hooks more intuitive and is also slightly faster 🐺⚡️

# .husky/pre-commit
- npx jest
+ jest # ~0.2s faster

A new recipe has been added to the docs. Lint staged files without external dependencies (inspired by Prettier docs). Feel free to modify it.

</tr></table>

... (truncated)

Commits

Updates lint-staged from 15.2.5 to 15.2.9

Release notes

Sourced from lint-staged's releases.

v15.2.9

Patch Changes

  • #1463 b69ce2d Thanks @​iiroj! - Set the maximum number of event listeners to the number of tasks. This should silence the console warning MaxListenersExceededWarning: Possible EventEmitter memory leak detected.

v15.2.8

Patch Changes

  • f0480f0 Thanks @​iiroj! - In the previous version the native git rev-parse --show-toplevel command was taken into use for resolving the current git repo root. This version switched the --show-toplevel flag with --show-cdup, because on Git installed via MSYS2 the former was returning absolute paths that do not work with Node.js child_process. The new flag returns a path relative to the working directory, avoiding the issue.

    The GitHub Actions workflow has been updated to install Git via MSYS2, to ensure better future compatibility; using the default Git binary in the GitHub Actions runner was working correctly even with MSYS2.

v15.2.7

Patch Changes

  • #1440 a51be80 Thanks @​iiroj! - In the previous version the native git rev-parse --show-toplevel command was taken into use for resolving the current git repo root. This version drops the --path-format=absolute option to support earlier git versions since it's also the default behavior. If you are still having trouble, please try upgrading git to the latest version.

v15.2.6

Patch Changes

  • #1433 119adb2 Thanks @​iiroj! - Use native "git rev-parse" commands to determine git repo root directory and the .git config directory, instead of using custom logic. This hopefully makes path resolution more robust on non-POSIX systems.
Changelog

Sourced from lint-staged's changelog.

15.2.9

Patch Changes

  • #1463 b69ce2d Thanks @​iiroj! - Set the maximum number of event listeners to the number of tasks. This should silence the console warning MaxListenersExceededWarning: Possible EventEmitter memory leak detected.

15.2.8

Patch Changes

  • f0480f0 Thanks @​iiroj! - In the previous version the native git rev-parse --show-toplevel command was taken into use for resolving the current git repo root. This version switched the --show-toplevel flag with --show-cdup, because on Git installed via MSYS2 the former was returning absolute paths that do not work with Node.js child_process. The new flag returns a path relative to the working directory, avoiding the issue.

    The GitHub Actions workflow has been updated to install Git via MSYS2, to ensure better future compatibility; using the default Git binary in the GitHub Actions runner was working correctly even with MSYS2.

15.2.7

Patch Changes

  • #1440 a51be80 Thanks @​iiroj! - In the previous version the native git rev-parse --show-toplevel command was taken into use for resolving the current git repo root. This version drops the --path-format=absolute option to support earlier git versions since it's also the default behavior. If you are still having trouble, please try upgrading git to the latest version.

15.2.6

Patch Changes

  • #1433 119adb2 Thanks @​iiroj! - Use native "git rev-parse" commands to determine git repo root directory and the .git config directory, instead of using custom logic. This hopefully makes path resolution more robust on non-POSIX systems.
Commits

Updates prettier from 3.2.5 to 3.3.3

Release notes

Sourced from prettier's releases.

3.3.3

🔗 Changelog

3.3.2

🔗 Changelog

3.3.1

🔗 Changelog

3.3.0

diff

🔗 Release note

Changelog

Sourced from prettier's changelog.

3.3.3

diff

Add parentheses for nullish coalescing in ternary (#16391 by @​cdignam-segment)

This change adds clarity to operator precedence.

// Input
foo ? bar ?? foo : baz;
foo ?? bar ? a : b;
a ? b : foo ?? bar;
// Prettier 3.3.2
foo ? bar ?? foo : baz;
foo ?? bar ? a : b;
a ? b : foo ?? bar;
// Prettier 3.3.3
foo ? (bar ?? foo) : baz;
(foo ?? bar) ? a : b;
a ? b : (foo ?? bar);

Add parentheses for decorator expressions (#16458 by @​y-schneider)

Prevent parentheses around member expressions or tagged template literals from being removed to follow the stricter parsing rules of TypeScript 5.5.

// Input
@(foo`tagged template`)
class X {}
// Prettier 3.3.2
@​footagged template
class X {}
// Prettier 3.3.3
@(footagged template)
class X {}

Support @let declaration syntax (#16474 by @​sosukesuzuki)

Adds support for Angular v18 @let declaration syntax.

Please see the following code example. The @let declaration allows you to define local variables within the template:

... (truncated)

Commits

Updates stylelint from 16.6.1 to 16.9.0

Release notes

Sourced from stylelint's releases.

16.9.0

  • Changed: secondaryOptions argument type ...

    Description has been truncated

@dependabot
Bump the minor group across 1 directory with 15 updates
10b0b33 
Bumps the minor group with 15 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@zip.js/zip.js](https://github.com/gildas-lormeau/zip.js) | `2.7.45` | `2.7.52` |
| [@codspeed/vitest-plugin](https://github.com/CodSpeedHQ/codspeed-node) | `3.1.0` | `3.1.1` |
| [@playwright/test](https://github.com/microsoft/playwright) | `1.44.1` | `1.46.1` |
| [@types/chrome](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/chrome) | `0.0.268` | `0.0.270` |
| [@types/firefox-webext-browser](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/firefox-webext-browser) | `120.0.3` | `120.0.4` |
| [ajv](https://github.com/ajv-validator/ajv) | `8.14.0` | `8.17.1` |
| [esbuild](https://github.com/evanw/esbuild) | `0.21.4` | `0.23.1` |
| [eslint-plugin-vitest](https://github.com/veritem/eslint-plugin-vitest) | `0.3.22` | `0.5.4` |
| [html-validate](https://gitlab.com/html-validate/html-validate) | `8.19.1` | `8.21.0` |
| [husky](https://github.com/typicode/husky) | `9.0.11` | `9.1.5` |
| [lint-staged](https://github.com/lint-staged/lint-staged) | `15.2.5` | `15.2.9` |
| [prettier](https://github.com/prettier/prettier) | `3.2.5` | `3.3.3` |
| [stylelint](https://github.com/stylelint/stylelint) | `16.6.1` | `16.9.0` |
| [stylelint-config-recommended](https://github.com/stylelint/stylelint-config-recommended) | `14.0.0` | `14.0.1` |
| [typescript](https://github.com/Microsoft/TypeScript) | `5.4.5` | `5.5.4` |



Updates `@zip.js/zip.js` from 2.7.45 to 2.7.52
- [Release notes](https://github.com/gildas-lormeau/zip.js/releases)
- [Commits](gildas-lormeau/zip.js@v2.7.45...v2.7.52)

Updates `@codspeed/vitest-plugin` from 3.1.0 to 3.1.1
- [Release notes](https://github.com/CodSpeedHQ/codspeed-node/releases)
- [Commits](CodSpeedHQ/codspeed-node@v3.1.0...v3.1.1)

Updates `@playwright/test` from 1.44.1 to 1.46.1
- [Release notes](https://github.com/microsoft/playwright/releases)
- [Commits](microsoft/playwright@v1.44.1...v1.46.1)

Updates `@types/chrome` from 0.0.268 to 0.0.270
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/chrome)

Updates `@types/firefox-webext-browser` from 120.0.3 to 120.0.4
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/firefox-webext-browser)

Updates `ajv` from 8.14.0 to 8.17.1
- [Release notes](https://github.com/ajv-validator/ajv/releases)
- [Commits](ajv-validator/ajv@v8.14.0...v8.17.1)

Updates `esbuild` from 0.21.4 to 0.23.1
- [Release notes](https://github.com/evanw/esbuild/releases)
- [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG.md)
- [Commits](evanw/esbuild@v0.21.4...v0.23.1)

Updates `eslint-plugin-vitest` from 0.3.22 to 0.5.4
- [Release notes](https://github.com/veritem/eslint-plugin-vitest/releases)
- [Commits](vitest-dev/eslint-plugin-vitest@v0.3.22...v0.5.4)

Updates `html-validate` from 8.19.1 to 8.21.0
- [Release notes](https://gitlab.com/html-validate/html-validate/tags)
- [Commits](https://gitlab.com/html-validate/html-validate/compare/v8.19.1...v8.21.0)

Updates `husky` from 9.0.11 to 9.1.5
- [Release notes](https://github.com/typicode/husky/releases)
- [Commits](typicode/husky@v9.0.11...v9.1.5)

Updates `lint-staged` from 15.2.5 to 15.2.9
- [Release notes](https://github.com/lint-staged/lint-staged/releases)
- [Changelog](https://github.com/lint-staged/lint-staged/blob/master/CHANGELOG.md)
- [Commits](lint-staged/lint-staged@v15.2.5...v15.2.9)

Updates `prettier` from 3.2.5 to 3.3.3
- [Release notes](https://github.com/prettier/prettier/releases)
- [Changelog](https://github.com/prettier/prettier/blob/main/CHANGELOG.md)
- [Commits](prettier/prettier@3.2.5...3.3.3)

Updates `stylelint` from 16.6.1 to 16.9.0
- [Release notes](https://github.com/stylelint/stylelint/releases)
- [Changelog](https://github.com/stylelint/stylelint/blob/main/CHANGELOG.md)
- [Commits](stylelint/stylelint@16.6.1...16.9.0)

Updates `stylelint-config-recommended` from 14.0.0 to 14.0.1
- [Release notes](https://github.com/stylelint/stylelint-config-recommended/releases)
- [Changelog](https://github.com/stylelint/stylelint-config-recommended/blob/main/CHANGELOG.md)
- [Commits](stylelint/stylelint-config-recommended@14.0.0...14.0.1)

Updates `typescript` from 5.4.5 to 5.5.4
- [Release notes](https://github.com/Microsoft/TypeScript/releases)
- [Changelog](https://github.com/microsoft/TypeScript/blob/main/azure-pipelines.release.yml)
- [Commits](microsoft/TypeScript@v5.4.5...v5.5.4)

---
updated-dependencies:
- dependency-name: "@zip.js/zip.js"
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: minor
- dependency-name: "@codspeed/vitest-plugin"
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: minor
- dependency-name: "@playwright/test"
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: minor
- dependency-name: "@types/chrome"
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: minor
- dependency-name: "@types/firefox-webext-browser"
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: minor
- dependency-name: ajv
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: minor
- dependency-name: esbuild
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: minor
- dependency-name: eslint-plugin-vitest
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: minor
- dependency-name: html-validate
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: minor
- dependency-name: husky
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: minor
- dependency-name: lint-staged
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: minor
- dependency-name: prettier
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: minor
- dependency-name: stylelint
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: minor
- dependency-name: stylelint-config-recommended
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: minor
- dependency-name: typescript
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot requested a review from a team as a code owner September 1, 2024 03:46
@dependabot dependabot bot added the area/dependencies The issue or PR is related to dependencies label Sep 1, 2024
@github-actions GitHub Actions
Copy link

github-actions bot commented Sep 1, 2024

⚠️ Visual differences introduced by this PR; please validate if they are desirable.

View Playwright Report (note: open the "playwright-report" artifact)

@dependabot Dependabot
Copy link
Author

dependabot bot commented on behalf of github Oct 1, 2024

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

@dependabot dependabot bot closed this Oct 1, 2024
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/minor-dc96c4c57c branch October 1, 2024 03:52
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
area/dependencies The issue or PR is related to dependencies
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants