Bump debug, socket.io, @angular/cli and karma in /archimedes

Bumps debug to 4.3.4 and updates ancestor dependencies debug, socket.io, @angular/cli and karma. These dependencies need to be updated together.

Updates debug from 4.1.1 to 4.3.4

Release notes

Sourced from debug's releases.

4.3.4

What's Changed

Add section about configuring JS console to show debug messages by @gitname in debug-js/debug#866

Replace deprecated String.prototype.substr() by @CommanderRoot in debug-js/debug#876

New Contributors

@gitname made their first contribution in debug-js/debug#866

@CommanderRoot made their first contribution in debug-js/debug#876

Full Changelog: https://github.com/debug-js/debug/compare/4.3.3...4.3.4

4.3.3

Patch Release 4.3.3

This is a documentation-only release. Further, the repository was transferred. Please see notes below.

Migrates repository from https://github.com/visionmedia/debug to https://github.com/debug-js/debug. Please see notes below as to why this change was made.

Updates repository maintainership information

Updates the copyright (no license terms change has been made)

Removes accidental epizeuxis (#828)

Adds README section regarding usage in child procs (#850)

Thank you to @taylor1791 and @kristofkalocsai for their contributions.

Repository Migration Information

I've formatted this as a FAQ, please feel free to open an issue for any additional question and I'll add the response here.

Q: What impact will this have on me?

In most cases, you shouldn't notice any change.

The only exception I can think of is if you pull code directly from https://github.com/visionmedia/debug, e.g. via a "debug": "visionmedia/debug"-type version entry in your package.json - in which case, you should still be fine due to the automatic redirection Github sets up, but you should also update any references as soon as possible.

Q: What are the security implications of this change?

If you pull code directly from the old URL, you should update the URL to https://github.com/debug-js/debug as soon as possible. The old organization has many approved owners and thus a new repository could (in theory) be created at the old URL, circumventing Github's automatic redirect that is in place now and serving malicious code. I (@qix-) also wouldn't have access to that repository, so while I don't think it would happen, it's still something to consider.

Even in such a case, however, the officially released package on npm (debug) would not be affected. That package is still very much under control (even more than it used to be).

Q: What should I do if I encounter an issue related to the migration?

Search the issues first to see if someone has already reported it, and then open a new issue if someone has not.

Q: Why was this done as a 'patch' release? Isn't this breaking?

No, it shouldn't be breaking. The package on npm shouldn't be affected (aside from this patch release) and any references to the old repository should automatically redirect.

Thus, according to all of the "APIs" (loosely put) involved, nothing should have broken.

... (truncated)

Commits

da66c86 4.3.4
9b33412 replace deprecated String.prototype.substr() (#876)
c0805cc add section about configuring JS console to show debug messages (#866)
043d3cd 4.3.3
4079aae update license and more maintainership information
19b36c0 update repository location + maintainership information
f851b00 adds README section regarding usage in child procs (#850)
d177f2b Remove accidental epizeuxis
e47f96d 4.3.2
1e9d38c cache enabled status per-logger (#799)
Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by qix, a new releaser for debug since your current version.

Updates debug from 3.2.6 to 4.3.4

Release notes

Sourced from debug's releases.

4.3.4

What's Changed

Add section about configuring JS console to show debug messages by @gitname in debug-js/debug#866

Replace deprecated String.prototype.substr() by @CommanderRoot in debug-js/debug#876

New Contributors

@gitname made their first contribution in debug-js/debug#866

@CommanderRoot made their first contribution in debug-js/debug#876

Full Changelog: https://github.com/debug-js/debug/compare/4.3.3...4.3.4

4.3.3

Patch Release 4.3.3

This is a documentation-only release. Further, the repository was transferred. Please see notes below.

Migrates repository from https://github.com/visionmedia/debug to https://github.com/debug-js/debug. Please see notes below as to why this change was made.

Updates repository maintainership information

Updates the copyright (no license terms change has been made)

Removes accidental epizeuxis (#828)

Adds README section regarding usage in child procs (#850)

Thank you to @taylor1791 and @kristofkalocsai for their contributions.

Repository Migration Information

I've formatted this as a FAQ, please feel free to open an issue for any additional question and I'll add the response here.

Q: What impact will this have on me?

In most cases, you shouldn't notice any change.

The only exception I can think of is if you pull code directly from https://github.com/visionmedia/debug, e.g. via a "debug": "visionmedia/debug"-type version entry in your package.json - in which case, you should still be fine due to the automatic redirection Github sets up, but you should also update any references as soon as possible.

Q: What are the security implications of this change?

If you pull code directly from the old URL, you should update the URL to https://github.com/debug-js/debug as soon as possible. The old organization has many approved owners and thus a new repository could (in theory) be created at the old URL, circumventing Github's automatic redirect that is in place now and serving malicious code. I (@qix-) also wouldn't have access to that repository, so while I don't think it would happen, it's still something to consider.

Even in such a case, however, the officially released package on npm (debug) would not be affected. That package is still very much under control (even more than it used to be).

Q: What should I do if I encounter an issue related to the migration?

Search the issues first to see if someone has already reported it, and then open a new issue if someone has not.

Q: Why was this done as a 'patch' release? Isn't this breaking?

No, it shouldn't be breaking. The package on npm shouldn't be affected (aside from this patch release) and any references to the old repository should automatically redirect.

Thus, according to all of the "APIs" (loosely put) involved, nothing should have broken.

... (truncated)

Commits

da66c86 4.3.4
9b33412 replace deprecated String.prototype.substr() (#876)
c0805cc add section about configuring JS console to show debug messages (#866)
043d3cd 4.3.3
4079aae update license and more maintainership information
19b36c0 update repository location + maintainership information
f851b00 adds README section regarding usage in child procs (#850)
d177f2b Remove accidental epizeuxis
e47f96d 4.3.2
1e9d38c cache enabled status per-logger (#799)
Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by qix, a new releaser for debug since your current version.

Updates socket.io from 2.4.1 to 4.7.2

Release notes

Sourced from socket.io's releases.

4.7.2

Bug Fixes

clean up child namespace when client is rejected in middleware (#4773) (0731c0d)

webtransport: properly handle WebTransport-only connections (3468a19)

webtransport: add proper framing (a306db0)

Links

Diff: https://github.com/socketio/socket.io/compare/4.7.1...4.7.2

Client release: 4.7.2

engine.io@~6.5.2 (diff)

ws@~8.11.0 (no change)

4.7.1

The client bundle contains a few fixes regarding the WebTransport support.

Links

Diff: https://github.com/socketio/socket.io/compare/4.7.0...4.7.1

Client release: 4.7.1

engine.io@~6.5.0 (no change)

ws@~8.11.0 (no change)

4.7.0

Bug Fixes

remove the Partial modifier from the socket.data type (#4740) (e5c62ca)

Features

Support for WebTransport

The Socket.IO server can now use WebTransport as the underlying transport.

WebTransport is a web API that uses the HTTP/3 protocol as a bidirectional transport. It's intended for two-way communications between a web client and an HTTP/3 server.

References:

https://w3c.github.io/webtransport/

https://developer.mozilla.org/en-US/docs/Web/API/WebTransport

https://developer.chrome.com/articles/webtransport/

Until WebTransport support lands in Node.js, you can use the @fails-components/webtransport package:
import { readFileSync } from "fs";
import { createServer } from "https";
import { Server } from "socket.io";
</tr></table> 

... (truncated)

Changelog

Sourced from socket.io's changelog.

4.7.2 (2023-08-02)

Bug Fixes

clean up child namespace when client is rejected in middleware (#4773) (0731c0d)

webtransport: properly handle WebTransport-only connections (3468a19)

webtransport: add proper framing (a306db0)

Dependencies

engine.io@~6.5.2 (diff)

ws@~8.11.0 (no change)

4.7.1 (2023-06-28)

The client bundle contains a few fixes regarding the WebTransport support.

Dependencies

engine.io@~6.5.0 (no change)

ws@~8.11.0 (no change)

4.7.0 (2023-06-22)

Bug Fixes

remove the Partial modifier from the socket.data type (#4740) (e5c62ca)

Features

Support for WebTransport

The Socket.IO server can now use WebTransport as the underlying transport.

WebTransport is a web API that uses the HTTP/3 protocol as a bidirectional transport. It's intended for two-way communications between a web client and an HTTP/3 server.

References:

https://w3c.github.io/webtransport/

https://developer.mozilla.org/en-US/docs/Web/API/WebTransport

https://developer.chrome.com/articles/webtransport/

... (truncated)

Commits

c332643 chore(release): 4.7.2
3468a19 fix(webtransport): properly handle WebTransport-only connections
09d4549 chore: bump engine.io to version 6.5.2
0731c0d fix: clean up child namespace when client is rejected in middleware (#4773)
03046a6 docs: update the list of supported Node.js versions
443e447 docs(examples): add example with WebTransport
2f6cc2f chore(release): 4.7.1
00d8ee5 chore(release): 4.7.0
2dd5fa9 ci: add Node.js 20 in the test matrix
a5dff0a docs(examples): increase httpd ProxyTimeout value (2)
Additional commits viewable in compare view

Updates @angular/cli from 10.1.1 to 16.2.4

Release notes

Sourced from @angular/cli's releases.

v16.2.4

16.2.4 (2023-09-27)

@schematics/angular

Commit Description

update @angular/cli version specifier to use ^

v16.2.3

16.2.3 (2023-09-20)

@angular-devkit/build-angular

Commit Description

correctly re-point RXJS to ESM on Windows

several windows fixes to application builder prerendering

@ngtools/webpack

Commit Description

fix recursion in webpack resolve

v16.2.2

16.2.2 (2023-09-13)

@angular-devkit/build-angular

Commit Description

support dev server proxy pathRewrite field in Vite-based server

v16.2.1

16.2.1 (2023-08-30)

@angular-devkit/build-angular

Commit Description

display warning when using resourcesOutputPath with esbuild builder

encode Sass package resolve directories in importer URLs

handle HMR updates of global CSS when using Vite

update vite to be able to serve app-shell and SSG pages

use correct type for extraEntryPoints

v16.2.0

16.2.0 (2023-08-09)

@angular-devkit/build-angular

Commit Description

add ssr option in application builder

add initial application builder implementation

add initial support for server bundle generation using esbuild

Commit	Description
	update `@angular/cli` version specifier to use `^`

Commit	Description
	correctly re-point RXJS to ESM on Windows
	several windows fixes to application builder prerendering

Commit	Description
	fix recursion in webpack resolve

Commit	Description
	support dev server proxy pathRewrite field in Vite-based server

Commit	Description
	display warning when using `resourcesOutputPath` with esbuild builder
	encode Sass package resolve directories in importer URLs
	handle HMR updates of global CSS when using Vite
	update vite to be able to serve app-shell and SSG pages
	use correct type for `extraEntryPoints`

Commit	Description
	add `ssr` option in application builder
	add initial application builder implementation
	add initial support for server bundle generation using esbuild

... (truncated)

Changelog

Sourced from @angular/cli's changelog.

16.2.4 (2023-09-27)

@schematics/angular

Commit Type Description

5dc7fb1a1 fix update @angular/cli version specifier to use ^

17.0.0-next.5 (2023-09-20)

Breaking Changes

Versions of TypeScript older than 5.2 are no longer supported.

Commit Type Description

1c00fd3fe refactor drop support for older TypeScript versions

@angular-devkit/build-angular

Commit Type Description

8168ae2a8 feat apply global CSS updates without a live-reload when using vite

8f9a0d70c feat support standalone apps route discovery during prerendering

c8909406a fix correctly re-point RXJS to ESM on Windows

48963fc17 fix several windows fixes to application builder prerendering

@ngtools/webpack

Commit Type Description

9291ddab8 fix fix recursion in webpack resolve

16.2.3 (2023-09-20)

@angular-devkit/build-angular

| Commit | Type | Description |

Commit	Type	Description
5dc7fb1a1	fix	update `@angular/cli` version specifier to use `^`

Commit	Type	Description
1c00fd3fe	refactor	drop support for older TypeScript versions

Commit	Type	Description
8168ae2a8	feat	apply global CSS updates without a live-reload when using `vite`
8f9a0d70c	feat	support standalone apps route discovery during prerendering
c8909406a	fix	correctly re-point RXJS to ESM on Windows
48963fc17	fix	several windows fixes to application builder prerendering

Commit	Type	Description
9291ddab8	fix	fix recursion in webpack resolve

... (truncated)

Commits

660d849 release: cut the v16.2.4 release
5dc7fb1 fix(@schematics/angular): update @angular/cli version specifier to use ^
ae41ab5 refactor(@angular-devkit/build-angular): typo in ignore list plugin function
64b3586 release: cut the v16.2.3 release
f1195d0 fix(@ngtools/webpack): fix recursion in webpack resolve
1f9caa9 refactor(@schematics/angular): remove empty space in app.config.ts.template
7d61494 Revert "ci: use head_ref for concurrency group"
7801185 ci: use head_ref for concurrency group
d8d116b fix(@angular-devkit/build-angular): several windows fixes to application buil...
39643be fix(@angular-devkit/build-angular): correctly re-point RXJS to ESM on Windows
Additional commits viewable in compare view

Updates karma from 5.2.2 to 6.4.2

Release notes

Sourced from karma's releases.

v6.4.2

6.4.2 (2023-04-21)

Bug Fixes

few typos (c6a4271)

v6.4.1

6.4.1 (2022-09-19)

Bug Fixes

pass integrity value (63d86be)

v6.4.0

6.4.0 (2022-06-14)

Features

support SRI verification of link tags (dc51a2e)

support SRI verification of script tags (6a54b1c)

v6.3.20

6.3.20 (2022-05-13)

Bug Fixes

prefer IPv4 addresses when resolving domains (e17698f), closes #3730

v6.3.19

6.3.19 (2022-04-19)

Bug Fixes

client: error out when opening a new tab fails (099b85e)

v6.3.18

6.3.18 (2022-04-13)

Bug Fixes

deps: upgrade socket.io to v4.4.1 (52a30bb)

v6.3.17

... (truncated)

Changelog

Sourced from karma's changelog.

6.4.2 (2023-04-21)

Bug Fixes

few typos (c6a4271)

6.4.1 (2022-09-19)

Bug Fixes

pass integrity value (63d86be)

6.4.0 (2022-06-14)

Features

support SRI verification of link tags (dc51a2e)

support SRI verification of script tags (6a54b1c)

6.3.20 (2022-05-13)

Bug Fixes

prefer IPv4 addresses when resolving domains (e17698f), closes #3730

6.3.19 (2022-04-19)

Bug Fixes

client: error out when opening a new tab fails (099b85e)

6.3.18 (2022-04-13)

Bug Fixes

deps: upgrade socket.io to v4.4.1 (52a30bb)

6.3.17 (2022-02-28)

Bug Fixes

deps: update colors to maintained version (#3763) (fca1884)

... (truncated)

Commits

9de3c00 chore(release): 6.4.2 [skip ci]
c6a4271 fix: few typos
50f9635 docs: update codeclimate badge in readme.md
0013121 chore(release): 6.4.1 [skip ci]
63d86be fix: pass integrity value
84f7cc3 chore(release): 6.4.0 [skip ci]
f2d0663 docs: add integrity parameter
dc51a2e feat: support SRI verification of link tags
6a54b1c feat: support SRI verification of script tags
5e71cf5 chore(release): 6.3.20 [skip ci]
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 this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/UCF/Search-Service-Django/network/alerts).

UCF / Search-Service-Django

Bump debug, socket.io, @angular/cli and karma in /archimedes #375

4.3.4

What's Changed

New Contributors

4.3.3

Patch Release 4.3.3

Repository Migration Information

Q: What impact will this have on me?

Q: What are the security implications of this change?

Q: What should I do if I encounter an issue related to the migration?

Q: Why was this done as a 'patch' release? Isn't this breaking?

4.3.4

What's Changed

New Contributors

4.3.3

Patch Release 4.3.3

Repository Migration Information

Q: What impact will this have on me?

Q: What are the security implications of this change?

Q: What should I do if I encounter an issue related to the migration?

Q: Why was this done as a 'patch' release? Isn't this breaking?

4.7.2

Bug Fixes

Links

4.7.1

Links

4.7.0

Bug Fixes

Features

Support for WebTransport

4.7.2 (2023-08-02)

Bug Fixes

Dependencies

4.7.1 (2023-06-28)

Dependencies

4.7.0 (2023-06-22)

Bug Fixes

Features

Support for WebTransport

v16.2.4

16.2.4 (2023-09-27)

@​schematics/angular

v16.2.3

16.2.3 (2023-09-20)

@​angular-devkit/build-angular

@​ngtools/webpack

v16.2.2

16.2.2 (2023-09-13)

@​angular-devkit/build-angular

v16.2.1

16.2.1 (2023-08-30)

@​angular-devkit/build-angular

v16.2.0

16.2.0 (2023-08-09)

@​angular-devkit/build-angular

16.2.4 (2023-09-27)

@​schematics/angular

17.0.0-next.5 (2023-09-20)

Breaking Changes

@​angular-devkit/build-angular

@​ngtools/webpack

16.2.3 (2023-09-20)

@​angular-devkit/build-angular

v6.4.2

6.4.2 (2023-04-21)

Bug Fixes

v6.4.1

6.4.1 (2022-09-19)

Bug Fixes

v6.4.0

6.4.0 (2022-06-14)

Features

v6.3.20

6.3.20 (2022-05-13)

Bug Fixes

v6.3.19

6.3.19 (2022-04-19)

Bug Fixes

v6.3.18

`@schematics/angular`

`@angular-devkit/build-angular`

`@ngtools/webpack`

`@angular-devkit/build-angular`

`@angular-devkit/build-angular`

`@angular-devkit/build-angular`

`@schematics/angular`

`@angular-devkit/build-angular`

`@ngtools/webpack`

`@angular-devkit/build-angular`