Bump debug and @angular/cli #45

dependabot · 2023-10-03T05:42:29Z

Bumps debug to 4.3.4 and updates ancestor dependencies debug and @angular/cli. 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: debug-js/debug@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: debug-js/debug@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 @angular/cli from 9.1.0 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

... (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 |

... (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

Maintainer changes

This version was pushed to npm by google-wombot, a new releaser for @angular/cli since your current version.

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 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.

Bumps [debug](https://github.com/debug-js/debug) to 4.3.4 and updates ancestor dependencies [debug](https://github.com/debug-js/debug) and [@angular/cli](https://github.com/angular/angular-cli). These dependencies need to be updated together. Updates `debug` from 4.1.1 to 4.3.4 - [Release notes](https://github.com/debug-js/debug/releases) - [Commits](debug-js/debug@4.1.1...4.3.4) Updates `debug` from 3.2.6 to 4.3.4 - [Release notes](https://github.com/debug-js/debug/releases) - [Commits](debug-js/debug@4.1.1...4.3.4) Updates `@angular/cli` from 9.1.0 to 16.2.4 - [Release notes](https://github.com/angular/angular-cli/releases) - [Changelog](https://github.com/angular/angular-cli/blob/main/CHANGELOG.md) - [Commits](angular/angular-cli@v9.1.0...16.2.4) --- updated-dependencies: - dependency-name: debug dependency-type: indirect - dependency-name: debug dependency-type: indirect - dependency-name: "@angular/cli" dependency-type: direct:development ... Signed-off-by: dependabot[bot] <[email protected]>

dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Oct 3, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Bump debug and @angular/cli #45

Bump debug and @angular/cli #45

dependabot bot commented on behalf of github Oct 3, 2023

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

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

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

Bump debug and @angular/cli #45

Are you sure you want to change the base?

Bump debug and @angular/cli #45

Conversation

dependabot bot commented on behalf of github Oct 3, 2023

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?

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

`@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`