Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump debug and @angular/cli #236

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Oct 2, 2023

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

New Contributors

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.

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

New Contributors

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.

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 10.0.5 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
fix - 5dc7fb1a1 update @angular/cli version specifier to use ^

v16.2.3

16.2.3 (2023-09-20)

@​angular-devkit/build-angular

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

@​ngtools/webpack

Commit Description
fix - f1195d035 fix recursion in webpack resolve

v16.2.2

16.2.2 (2023-09-13)

@​angular-devkit/build-angular

Commit Description
fix - e3a40a49a 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
fix - 221ab2483 display warning when using resourcesOutputPath with esbuild builder
fix - fe752ad87 encode Sass package resolve directories in importer URLs
fix - 82b0f94fd handle HMR updates of global CSS when using Vite
fix - 6a48a11b8 update vite to be able to serve app-shell and SSG pages
fix - fdb16f7cd use correct type for extraEntryPoints

v16.2.0

16.2.0 (2023-08-09)

@​angular-devkit/build-angular

Commit Description
feat - e6b377436 add ssr option in application builder
feat - c05c83be7 add initial application builder implementation
feat - 095f5aba6 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

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 10.0.5 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@v10.0.5...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 dependabot bot added the dependencies Pull requests that update a dependency file label Oct 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants