MHCommunity / mousehunt-improved

MouseHunt Improved - improves your MouseHunt experience
MIT License
12 stars 13 forks source link

Bump the dev-dependencies group with 4 updates #443

Closed dependabot[bot] closed 1 month ago

dependabot[bot] commented 1 month ago

Updates the requirements on @sentry/browser, @sentry/cli, @wordpress/eslint-plugin and esbuild to permit the latest version. Updates @sentry/browser to 8.31.0

Release notes

Sourced from @​sentry/browser's releases.

8.31.0

Important Changes

  • feat(node): Add dataloader integration (#13664)

This release adds a new integration for the dataloader package. The Node SDK (and all SDKs that depend on it) will now automatically instrument dataloader instances. You can also add it manually:

Sentry.init({
  integrations: [Sentry.dataloaderIntegration()],
});

Other Changes

  • feat(browser): Add navigation activationStart timestamp to pageload span (#13658)
  • feat(gatsby): Add optional deleteSourcemapsAfterUpload (#13610)
  • feat(nextjs): Give app router prefetch requests a http.server.prefetch op (#13600)
  • feat(nextjs): Improve Next.js serverside span data quality (#13652)
  • feat(node): Add disableInstrumentationWarnings option (#13693)
  • feat(nuxt): Adding experimental_basicServerTracing option to Nuxt module (#13643)
  • feat(nuxt): Improve logs about adding Node option 'import' (#13726)
  • feat(replay): Add onError callback + other small improvements to debugging (#13721)
  • feat(replay): Add experimental option to allow for a checkout every 6 minutes (#13069)
  • feat(wasm): Unconditionally parse instruction addresses (#13655)
  • fix: Ensure all logs are wrapped with consoleSandbox (#13690)
  • fix(browser): Try multiple options for lazyLoadIntegration script parent element lookup (#13717)
  • fix(feedback): Actor color applies to feedback icon (#13702)
  • fix(feedback): Fix form width on mobile devices (#13068)
  • fix(nestjs): Preserve original function name on SentryTraced functions (#13684)
  • fix(node): Don't overwrite local variables for re-thrown errors (#13644)
  • fix(normalize): Treat Infinity as NaN both are non-serializable numbers (#13406)
  • fix(nuxt): Use correct server output file path (#13725)
  • fix(opentelemetry): Always use active span in Propagator.inject (#13381)
  • fix(replay): Fixes potential out-of-order segments (#13609)

Work in this release was contributed by @​KyGuy2002, @​artzhookov, and @​julianCast. Thank you for your contributions!

Changelog

Sourced from @​sentry/browser's changelog.

8.31.0

Important Changes

  • feat(node): Add dataloader integration (#13664)

This release adds a new integration for the dataloader package. The Node SDK (and all SDKs that depend on it) will now automatically instrument dataloader instances. You can also add it manually:

Sentry.init({
  integrations: [Sentry.dataloaderIntegration()],
});

Other Changes

  • feat(browser): Add navigation activationStart timestamp to pageload span (#13658)
  • feat(gatsby): Add optional deleteSourcemapsAfterUpload (#13610)
  • feat(nextjs): Give app router prefetch requests a http.server.prefetch op (#13600)
  • feat(nextjs): Improve Next.js serverside span data quality (#13652)
  • feat(node): Add disableInstrumentationWarnings option (#13693)
  • feat(nuxt): Adding experimental_basicServerTracing option to Nuxt module (#13643)
  • feat(nuxt): Improve logs about adding Node option 'import' (#13726)
  • feat(replay): Add onError callback + other small improvements to debugging (#13721)
  • feat(replay): Add experimental option to allow for a checkout every 6 minutes (#13069)
  • feat(wasm): Unconditionally parse instruction addresses (#13655)
  • fix: Ensure all logs are wrapped with consoleSandbox (#13690)
  • fix(browser): Try multiple options for lazyLoadIntegration script parent element lookup (#13717)
  • fix(feedback): Actor color applies to feedback icon (#13702)
  • fix(feedback): Fix form width on mobile devices (#13068)
  • fix(nestjs): Preserve original function name on SentryTraced functions (#13684)
  • fix(node): Don't overwrite local variables for re-thrown errors (#13644)
  • fix(normalize): Treat Infinity as NaN both are non-serializable numbers (#13406)
  • fix(nuxt): Use correct server output file path (#13725)
  • fix(opentelemetry): Always use active span in Propagator.inject (#13381)
  • fix(replay): Fixes potential out-of-order segments (#13609)

Work in this release was contributed by @​KyGuy2002, @​artzhookov, and @​julianCast. Thank you for your contributions!

8.30.0

Important Changes

  • feat(node): Add kafkajs integration (#13528)

This release adds a new integration that instruments kafkajs library with spans and traces. This integration is automatically enabled by default, but can be included with the Sentry.kafkaIntegration() import.

... (truncated)

Commits
  • 5456e2c release: 8.31.0
  • b1a26c8 Merge pull request #13734 from getsentry/prepare-release/8.31.0
  • 1914376 meta(changelog): Update changelog for 8.31.0
  • cf0152a feat(replay): Add onError callback + other small improvements to debugging ...
  • 336a236 feat(nuxt): Improve logs about adding Node option 'import' (#13726)
  • 2ab7518 feat(node): Add dataloader integration (#13664)
  • 37c4c42 ref: Add external contributor to CHANGELOG.md (#13727)
  • 32f5f00 fix(nuxt): Use correct server output file path (#13725)
  • fc7634e feat(gatsby): Add optional deleteSourcemapsAfterUpload (#13610)
  • 1e9a1a3 test(ci): Use latest node 22 version again for Node unit tests (#13720)
  • Additional commits viewable in compare view


Updates @sentry/cli to 2.36.2

Release notes

Sourced from @​sentry/cli's releases.

2.36.2

Various fixes & improvements

Changelog

Sourced from @​sentry/cli's changelog.

2.36.2

Various fixes & improvements

2.36.1

Various fixes & improvements

  • Fix a bug where background Xcode uploads sometimes failed

2.36.0

Various fixes & improvements

  • Log when file not added to source bundle (#2146) by @​szokeasaurusrex
  • Bump Symbolic to 12.11.0. This fixes a bug where uploading source files sometimes failed when any of the files were not UTF-8 encoded

2.35.0

Various fixes & improvements

2.34.1

Various fixes & improvements

  • build: Bump symbolic to 12.10.1 (#2134) by @​szokeasaurusrex
    • This includes an upstream bugfix for a bug that prevented debug file uploading with sources when any of the sources were not valid UTF-8.
  • fix(debugIds): Always instantiate global Error class in debugId injection snippet (#2132) by @​Lms24

2.34.0

Various fixes & improvements

2.33.1

Security fix

This release contains a fix for a bug where auth tokens would, under the following circumstances, be logged to stdout:

... (truncated)

Commits


Updates @wordpress/eslint-plugin to 21.1.2

Changelog

Sourced from @​wordpress/eslint-plugin's changelog.

Unreleased

21.1.0 (2024-09-19)

21.0.0 (2024-09-05)

Breaking Changes

20.3.0 (2024-08-21)

20.2.0 (2024-08-07)

20.1.0 (2024-07-24)

20.0.0 (2024-07-10)

Breaking Changes

19.2.0 (2024-06-26)

19.1.0 (2024-06-15)

19.0.0 (2024-05-31)

Breaking Changes

  • @wordpress/is-gutenberg-plugin rule has been replaced by @wordpress/wp-global-usage (#61486).
  • @wordpress/wp-process-env rule has been added and included in the recommended configurations (#61486).
  • @wordpress/gutenberg-phase rule has been removed (deprecated in v10.0.0) (#61486).
  • Increase the minimum required Node.js version to v18.12.0 matching long-term support releases (#31270). Learn more about Node.js releases.

18.1.0 (2024-05-16)

Internal

  • Replaced classnames package with the faster and smaller clsx package (#61138).

18.0.0 (2024-05-02)

Breaking Changes

  • Enable curly eslint rule when using prettier (#61204).

... (truncated)

Commits


Updates esbuild from 0.23.1 to 0.24.0

Release notes

Sourced from esbuild's releases.

v0.24.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.23.0 or ~0.23.0. See npm's documentation about semver for more information.

  • Drop support for older platforms (#3902)

    This release drops support for the following operating system:

    • macOS 10.15 Catalina

    This is because the Go programming language dropped support for this operating system version in Go 1.23, and this release updates esbuild from Go 1.22 to Go 1.23. Go 1.23 now requires macOS 11 Big Sur or later.

    Note that this only affects the binary esbuild executables that are published to the esbuild npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.23). That might look something like this:

    git clone https://github.com/evanw/esbuild.git
    cd esbuild
    go build ./cmd/esbuild
    ./esbuild --version
    
  • Fix class field decorators in TypeScript if useDefineForClassFields is false (#3913)

    Setting the useDefineForClassFields flag to false in tsconfig.json means class fields use the legacy TypeScript behavior instead of the standard JavaScript behavior. Specifically they use assign semantics instead of define semantics (e.g. setters are triggered) and fields without an initializer are not initialized at all. However, when this legacy behavior is combined with standard JavaScript decorators, TypeScript switches to always initializing all fields, even those without initializers. Previously esbuild incorrectly continued to omit field initializers for this edge case. These field initializers in this case should now be emitted starting with this release.

  • Avoid incorrect cycle warning with tsconfig.json multiple inheritance (#3898)

    TypeScript 5.0 introduced multiple inheritance for tsconfig.json files where extends can be an array of file paths. Previously esbuild would incorrectly treat files encountered more than once when processing separate subtrees of the multiple inheritance hierarchy as an inheritance cycle. With this release, tsconfig.json files containing this edge case should work correctly without generating a warning.

  • Handle Yarn Plug'n'Play stack overflow with tsconfig.json (#3915)

    Previously a tsconfig.json file that extends another file in a package with an exports map could cause a stack overflow when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release.

  • Work around more issues with Deno 1.31+ (#3917)

    This version of Deno broke the stdin and stdout properties on command objects for inherited streams, which matters when you run esbuild's Deno module as the entry point (i.e. when import.meta.main is true). Previously esbuild would crash in Deno 1.31+ if you ran esbuild like that. This should be fixed starting with this release.

    This fix was contributed by @​Joshix-1.

Changelog

Sourced from esbuild's changelog.

0.24.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.23.0 or ~0.23.0. See npm's documentation about semver for more information.

  • Drop support for older platforms (#3902)

    This release drops support for the following operating system:

    • macOS 10.15 Catalina

    This is because the Go programming language dropped support for this operating system version in Go 1.23, and this release updates esbuild from Go 1.22 to Go 1.23. Go 1.23 now requires macOS 11 Big Sur or later.

    Note that this only affects the binary esbuild executables that are published to the esbuild npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.23). That might look something like this:

    git clone https://github.com/evanw/esbuild.git
    cd esbuild
    go build ./cmd/esbuild
    ./esbuild --version
    
  • Fix class field decorators in TypeScript if useDefineForClassFields is false (#3913)

    Setting the useDefineForClassFields flag to false in tsconfig.json means class fields use the legacy TypeScript behavior instead of the standard JavaScript behavior. Specifically they use assign semantics instead of define semantics (e.g. setters are triggered) and fields without an initializer are not initialized at all. However, when this legacy behavior is combined with standard JavaScript decorators, TypeScript switches to always initializing all fields, even those without initializers. Previously esbuild incorrectly continued to omit field initializers for this edge case. These field initializers in this case should now be emitted starting with this release.

  • Avoid incorrect cycle warning with tsconfig.json multiple inheritance (#3898)

    TypeScript 5.0 introduced multiple inheritance for tsconfig.json files where extends can be an array of file paths. Previously esbuild would incorrectly treat files encountered more than once when processing separate subtrees of the multiple inheritance hierarchy as an inheritance cycle. With this release, tsconfig.json files containing this edge case should work correctly without generating a warning.

  • Handle Yarn Plug'n'Play stack overflow with tsconfig.json (#3915)

    Previously a tsconfig.json file that extends another file in a package with an exports map could cause a stack overflow when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release.

  • Work around more issues with Deno 1.31+ (#3917)

    This version of Deno broke the stdin and stdout properties on command objects for inherited streams, which matters when you run esbuild's Deno module as the entry point (i.e. when import.meta.main is true). Previously esbuild would crash in Deno 1.31+ if you ran esbuild like that. This should be fixed starting with this release.

    This fix was contributed by @​Joshix-1.

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 1 month ago

Superseded by #444.