Bump the all-updates group in /frontend with 5 updates

[dependabot]

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

Package	From	To
@testing-library/react	13.4.0	16.0.1
@testing-library/user-event	13.5.0	14.5.2
postcss	8.4.47	8.4.49
electron	25.9.8	33.2.0
wait-on	7.2.0	8.0.1

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

• export new act when available (#1319) (b6e59f7)

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

• build: add types field in exports (#1029) (5bed8c6)
• remove circular dependencies (#1027) (1aa2027)

v14.4.2

14.4.2 (2022-08-04)

Bug Fixes

• build: add exports field (#1022) (7839e29)

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 postcss from 8.4.47 to 8.4.49

Release notes

Sourced from postcss's releases.

8.4.49

• Fixed custom syntax without source.offset (by @​romainmenke).

8.4.48

• Fixed position calculation in error/warnings methods (by @​romainmenke).

Changelog

Sourced from postcss's changelog.

8.4.49

• Fixed custom syntax without source.offset (by @​romainmenke).

8.4.48

• Fixed position calculation in error/warnings methods (by @​romainmenke).

Commits

• aed8b89 Release 8.4.49 version
• 3450630 Fix position calculations when offset is missing (#1983)
• 77420d6 Release 8.4.48 version
• 341529f Update dependencies
• 66fa667 Add Node.js 23 to CI
• 1a8b261 fix inconsistent position calculations (#1980)
• 1cc6ac3 Clarify usage in docs
• See full diff in compare view

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

• c9d026e chore: bump chromium to 130.0.6723.118 (33-x-y) (#44591)
• 65cd09f feat: GPU shared texture offscreen rendering (33-x-y) (#44511)
• c8dc871 chore: bump chromium to 130.0.6723.116 (33-x-y) (#44583)
• 6e44a27 chore: remove executable flag from docs/api/app.md file permissions (#44578)
• 743fe6f test: fixup flaky session tests (#44565)
• bd81baa fix: remove use of banned std::to_string() (#44563)
• 6e1d940 docs: capitalize POSIX and Windows correctly (#44558)
• be69311 build: add new status to verify if all the required gha jobs have run (#44553)
• fcf0c11 chore: remove use of banned absl::optional (#44551)
• 4fad573 build: remove unused lint package (#44535)
• Additional commits viewable in compare view

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 <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> 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 <dependency name> 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 <dependency name> 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 <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

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