search

CortexFlow / CortexBrain

A powerful open-source IoT simulation framework for simulating and analyzing devices written in Python. Supporting MQTT,HTTP protocols. Designed for versatility, ease of use, and extensive IoT experimentation
https://www.cortexflow.org
Apache License 2.0
5 stars 2 forks source link

Bump the all-updates group in /frontend with 7 updates #20

Closed dependabot[bot] closed 2 weeks ago

dependabot[bot] commented 2 weeks ago

Bumps the all-updates group in /frontend with 7 updates:

Package From To
@testing-library/jest-dom 5.17.0 6.6.3
@testing-library/react 13.4.0 16.0.1
@testing-library/user-event 13.5.0 14.5.2
web-vitals 2.1.4 4.2.4
concurrently 7.6.0 9.1.0
electron 25.9.8 33.2.0
wait-on 7.2.0 8.0.1

Updates @testing-library/jest-dom from 5.17.0 to 6.6.3

Release notes

Sourced from @​testing-library/jest-dom's releases.

v6.6.3

6.6.3 (2024-10-31)

Bug Fixes

  • add vitest import when extending vitest matchers (#646) (5ba0156)

v6.6.2

6.6.2 (2024-10-17)

Bug Fixes

  • remove recursive type reference in vitest types (#636) (4468378)

v6.6.1

6.6.1 (2024-10-16)

Bug Fixes

  • fix lodash import in to-have-selection.js (#642) (ced792e)

v6.6.0

6.6.0 (2024-10-16)

Features

v6.5.0

6.5.0 (2024-08-23)

Features

  • toHaveValue: Asserting aria-valuenow (#479) (acbf416)

v6.4.8

6.4.8 (2024-07-23)

Bug Fixes

  • Drop peerDependencies from package.json (#610) (faf534b)

v6.4.7

6.4.7 (2024-07-22)

... (truncated)

Commits
  • 5ba0156 fix: add vitest import when extending vitest matchers (#646)
  • 4468378 fix: remove recursive type reference in vitest types (#636)
  • abba961 docs: add billyjanitsch as a contributor for bug (#644)
  • 9490615 docs: add G-Rath as a contributor for code (#643)
  • ced792e fix: fix lodash import in to-have-selection.js (#642)
  • 9b14804 feat: implement toHaveSelection (#637)
  • f5b0e94 docs: add diegohaz as a contributor for ideas (#640)
  • 68e927e docs: add pwolaq as a contributor for code, and test (#639)
  • 04005db docs: add silviuaavram as a contributor for code, and test (#638)
  • 4723de3 docs: add mibcadet as a contributor for doc (#628)
  • Additional commits viewable in compare view


Updates @testing-library/react from 13.4.0 to 16.0.1

Release notes

Sourced from @​testing-library/react's releases.

v16.0.1

16.0.1 (2024-08-29)

Bug Fixes

  • Add support for exactOptionalPropertyTypes in TypeScript (#1351) (3dcd8a9)

v16.0.0

16.0.0 (2024-06-03)

Features

  • Move @testing-library/dom and @types/react-dom to peer dependencies (#1305) (a4744fa)

BREAKING CHANGES

  • @testing-library/dom was moved to a peer dependency and needs to be explicitly installed. This reduces the chance of having conflicting versions of @testing-library/dom installed that frequently caused bugs when used with @testing-library/user-event. We will also be able to allow new versions of @testing-library/dom being used without a SemVer major release of @testing-library/react by just widening the peer dependency. @types/react-dom needs to be installed if you're typechecking files using @testing-library/react.

v15.0.7

15.0.7 (2024-05-07)

Bug Fixes

  • Ensure act is not any when React.act is not declared (#1323) (c1f2957)

v15.0.6

15.0.6 (2024-05-01)

Bug Fixes

v15.0.5

15.0.5 (2024-04-26)

Bug Fixes

  • Stop restricting container option based on hydrate (#1313) (d143f46)

v15.0.4

... (truncated)

Commits
  • 3dcd8a9 fix: Add support for exactOptionalPropertyTypes in TypeScript (#1351)
  • 7a28fa9 Fix React Canary and Experimental tests (#1353)
  • a4744fa feat: Move @testing-library/dom and @types/react-dom to peer dependencie...
  • c1f2957 fix: Ensure act is not any when React.act is not declared (#1323)
  • b6e59f7 fix: export new act when available (#1319)
  • f6a1677 chore: Adjust tests to workaround 18.3.0 bug (#1315)
  • d143f46 fix: Stop restricting container option based on hydrate (#1313)
  • 48282c2 fix: Ensure renderHook options extend options for render (#1308)
  • 067d0c6 fix: Don't raise TypeScript errors when hydating document (#1304)
  • c63b873 fix: Improve legacyRoot error message (#1301)
  • Additional commits viewable in compare view


Updates @testing-library/user-event from 13.5.0 to 14.5.2

Release notes

Sourced from @​testing-library/user-event's releases.

v14.5.2

14.5.2 (2023-12-29)

Bug Fixes

  • remove interop and deep DTL imports (6a3c896)

v14.5.1

14.5.1 (2023-09-15)

Bug Fixes

  • incorrect default import from @​testing-library/dom (#1162) (d7483f0)

v14.5.0

14.5.0 (2023-09-14)

Bug Fixes

  • exports: add a named export for userEvent (4019cee), closes #1146

Features

  • types: Add additional type exports for UserEvent & Options (#1112) (da00e8d)

v14.4.3

14.4.3 (2022-08-09)

Bug Fixes

v14.4.2

14.4.2 (2022-08-04)

Bug Fixes

v14.4.1

14.4.1 (2022-08-02)

... (truncated)

Commits
  • d036279 chore: upgrade node in codesandbox
  • 910fee5 chore: set tsconfig baseUrl
  • fa8d867 revert: swap release script
  • c4b4629 chore: upgrade testing environment
  • 6a3c896 fix: remove interop and deep DTL imports
  • d7483f0 fix: incorrect default import from @​testing-library/dom (#1162)
  • 4be87b3 chore: swap release script
  • d95121d chore: add --experimental-import-meta-resolve
  • 8779eae chore: format, lint, fix lint
  • 4019cee fix(exports): add a named export for userEvent
  • Additional commits viewable in compare view


Updates web-vitals from 2.1.4 to 4.2.4

Changelog

Sourced from web-vitals's changelog.

v4.2.4 (2024-10-22)

  • Fix memory leak in registering new event listeners on every keydown and click (#554)

v4.2.3 (2024-08-06)

  • Fix missing LoAF entries in INP attribution (#512)

v4.2.2 (2024-07-17)

  • Fix interaction count after bfcache restore (#505)

v4.2.1 (2024-06-30)

  • Fix compatibility issues with TypeScript v5.5 (#497)

v4.2.0 (2024-06-20)

  • Refactor INP attribution code to fix errors on Windows 10 (#495)

v4.1.1 (2024-06-10)

  • Fix pending LoAF cleanup logic (#493)

v4.1.0 (2024-06-06)

  • Move the support check to the top of the onINP() function (#490)
  • Fix missing LoAF attribution when entries are dispatched before event entries (#487)

v4.0.1 (2024-05-21)

  • Add the ReportCallback type back but deprecate it (#483)

v4.0.0 (2024-05-13)

  • [BREAKING] Update types to support more generic usage (#471)
  • [BREAKING] Split waitingDuration to make it easier to understand redirect delays (#458)
  • [BREAKING] Rename TTFBAttribution fields from *Time to *Duration (#453)
  • [BREAKING] Rename resourceLoadTime to resourceLoadDuration in LCP attribution (#450)
  • [BREAKING] Add INP breakdown timings and LoAF attribution (#442)
  • [BREAKING] Deprecate onFID() and remove previously deprecated APIs (#435)
  • Expose the target element in INP attribution (#479)
  • Save INP target after interactions to reduce null values when removed from the DOM (#477)
  • Cap TTFB in attribution (#440)
  • Fix reportAllChanges behavior for LCP when library is loaded late (#468)

v3.5.2 (2024-01-25)

  • Pick the first non-null target for INP attribution (#421)

... (truncated)

Commits


Updates concurrently from 7.6.0 to 9.1.0

Release notes

Sourced from concurrently's releases.

v9.1.0

What's Changed

New Contributors

Full Changelog: https://github.com/open-cli-tools/concurrently/compare/v9.0.1...v9.1.0

v9.0.1

What's Changed

Full Changelog: https://github.com/open-cli-tools/concurrently/compare/v9.0.0...v9.0.1

v9.0.0

💥 Breaking Changes

  • Dropped support for Node.js < 18.0.0. Older Node.js version have reached end-of-life, and certain features require new-ish JS APIs.

  • Pending commands no longer run when --max-processes is set and an interruption/kill signal is sent - #433, #452, #460 Before v9.0.0, pressing Ctrl+C when --max-processes is set meant that only those commands would receive it. Once these stopped, the pending commands would start, which in turn meant that another Ctrl+C press would be necessary to stop them, and so on. Similar situation applied to combining --max-processes with --kill-others/--kill-others-on-fail.

    Starting with v9.0.0, this no longer happens, as these flags and/or key presses send a signal to stop the running commands in addition to preventing new commands from running.

  • The concurrently and default exports are now the same - #399 It's reasonable to expect that import { concurrently } from 'concurrently' would work the same as import concurrently from 'concurrently', however this has not been the case. The former used to be an unconfigured version of concurrently, lacking all features that you'd get from the CLI, which was seen as a "footgun". Both are now the same function.

    If you'd like to access the unconfigured function, use import { createConcurrently } from 'concurrently' instead.

✨ New Features

  • Exponential back-off support for process restarting - #265, #462 Use --restart-after exponential. Restarts happen at 2^N seconds.
  • Add prefix padding via new --pad-prefix flag - #166, #417, #495
  • Specify teardown commands via new --teardown flag - #472, #500
  • Expand node:<script> commands to node --run <script> - #475
  • [API only] Inter-Process Communication (ipc) - #498
  • [API only] Make it possible to use no colors at all - #466
  • [API only] Add a state field to Command - #455

🐛 Bug Fixes

  • Fix importing concurrently in ESM package - #454, #456, #494
  • Make sure concurrently doesn't resolve when manually restarting commands through API - #463, #464
  • Fix warning coming from spawn-command when running in Node 22 - #407, #477, #479, #492
  • Make --raw and --hide compatible - #394, #486
  • Ensure prefix is written when logging without a trailing LF - #467

... (truncated)

Commits


Updates electron from 25.9.8 to 33.2.0

Release notes

Sourced from electron's releases.

electron v33.2.0

Release Notes for v33.2.0

Features

  • Added GPU accelerated shared texture offscreen rendering. #44511

Other Changes

  • Updated Chromium to 130.0.6723.118. #44591

electron v33.1.0

Release Notes for v33.1.0

Features

  • Added WebFrameMain.detached for frames in an unloading state.
    • Added WebFrameMain.isDestroyed() to determine if a frame has been destroyed.
    • Fixed webFrameMain.fromId(processId, frameId) returning a WebFrameMain instance which doesn't match the given parameters when the frame is unloading. #44209

Fixes

  • Fixed an issue where EventSource was undefined in both renderer and worker processes when Node.js integration was enabled. #44496 (Also in 32, 34)
  • Fixed crash when network process terminates while a net log is running. #44420 (Also in 31, 32, 34)
  • Fixed crash when rendering super menu accelerator on linux. #44520 (Also in 34)
  • Fixed external window focus when using shell.openExternal. #44468 (Also in 34)
  • Fixed regression with dynamic dependency on libgdk_pixbuf. #44436 (Also in 32, 34)

Other Changes

  • Performance improvements when processing microtasks. #44473 (Also in 32, 34)
  • Updated Chromium to 130.0.6723.91. #44477

electron v33.0.2

Release Notes for v33.0.2

Fixes

  • Fixed trace-startup not working on macOS. #44276 (Also in 32, 34)
  • Fixed an issue where closing a window after printing on Linux triggered a crash. #44285 (Also in 31, 32, 34)
  • Fixed an issue where the exit event could be emitted twice from the utilityProcess. #44266 (Also in 31, 32, 34)
  • Fixed calling setAlwaysOnTop on a hidden window which is then shown with showInactive on Linux under X11. #44324 (Also in 31, 32, 34)
  • Fixed race condition in which WebContents appears as white screen on VDI machines without hardware acceleration capabilities. #44352 (Also in 32, 34)

electron v33.0.1

Release Notes for v33.0.1

Other Changes

  • Updated Chromium to 130.0.6723.59. #44271

electron v33.0.0

Release Notes for 33.0.0

... (truncated)

Changelog

Sourced from electron's changelog.

Breaking Changes

Breaking changes will be documented here, and deprecation warnings added to JS code where possible, at least one major version before the change is made.

Types of Breaking Changes

This document uses the following convention to categorize breaking changes:

  • API Changed: An API was changed in such a way that code that has not been updated is guaranteed to throw an exception.
  • Behavior Changed: The behavior of Electron has changed, but not in such a way that an exception will necessarily be thrown.
  • Default Changed: Code depending on the old default may break, not necessarily throwing an exception. The old behavior can be restored by explicitly specifying the value.
  • Deprecated: An API was marked as deprecated. The API will continue to function, but will emit a deprecation warning, and will be removed in a future release.
  • Removed: An API or feature was removed, and is no longer supported by Electron.

Planned Breaking API Changes (34.0)

Deprecated: level, message, line, and sourceId arguments in console-message event on WebContents

The console-message event on WebContents has been updated to provide details on the Event argument.

// Deprecated
webContents.on('console-message', (event, level, message, line, sourceId) => {})

// Replace with:

webContents.on('console-message', ({ level, message, lineNumber, sourceId, frame }) => {})

Additionally, level is now a string with possible values of info, warning, error, and debug.

Planned Breaking API Changes (33.0)

Behavior Changed: frame properties may retrieve detached WebFrameMain instances or none at all

APIs which provide access to a WebFrameMain instance may return an instance with frame.detached set to true, or possibly return null.

When a frame performs a cross-origin navigation, it enters into a detached state in which it's no longer attached to the page. In this state, it may be running unload handlers prior to being deleted. In the event of an IPC sent during this state, frame.detached will be set to true with the frame being destroyed shortly thereafter.

When receiving an event, it's important to access WebFrameMain properties immediately upon being received. Otherwise, it's not guaranteed to point to the same webpage as when received. To avoid misaligned expectations, Electron will return null in the case of late access where the webpage has changed.

... (truncated)

Commits


Updates wait-on from 7.2.0 to 8.0.1

Release notes

Sourced from wait-on's releases.

v8.0.0 - breaking change for http unix socket use

Updated for security vulnerabilities with axios@1.7.4 and braces.

Breaking change in using latest axios with a unix socket URL

As part of the axios update, the syntax for using a socket with an http URL in axios has changed so you must specify the protocol and server

For example:

http://unix:SOCKETPATH:http://server/foo/bar

instead of just using only the path (no protocol and no server)

http://unix:SOCKETPATH:/foo/bar

Due to this change, I have updated my tests, docs, bumped the major version.

Commits
  • a99e05f 8.0.1
  • 0a4df4c Merge pull request #166 from jeffbski/update-deps-2024-09-10
  • 5e208fa update minor deps
  • bbdac66 Merge pull request #165 from jeffbski/remove-travis-finish-gh-actions-migration
  • 4762007 update README with badge, remove .travis.yml
  • 7cab7b0 Merge pull request #164 from jeffbski/migrate-gh-actions
  • c1a8527 update badge on readme to point to gh-actions
  • df619a9 rename to CI
  • 65455f5 Create node.js.yml for gh-actions
  • 0b193cf 8.0.0
  • 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 2 weeks ago

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.

To ignore these dependencies, configure ignore rules in dependabot.yml