Skip to content

Bump @angular/core from 7.2.7 to 10.2.5 #18

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

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

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Jul 22, 2024

Bumps @angular/core from 7.2.7 to 10.2.5.

Changelog

Sourced from @​angular/core's changelog.

10.2.5 (2021-04-14)

Bug Fixes

  • compiler-cli: show a more specific error for Ivy NgModules (#41534) (#41598) (f630f33)
  • core: fix possible XSS attack in development through SSR (#40525) (ba8da74)

10.2.4 (2020-12-17)

Bug Fixes

  • core: fix possible XSS attack in development through SSR. (#40152) (0b8e3d5)
  • core: set ngDevMode to false when calling enableProdMode() (#40160) (90570c0)

10.2.3 (2020-11-09)

Bug Fixes

  • compiler: ensure that i18n message-parts have the correct source-span (#39589) (e67a331)
  • compiler: skipping leading whitespace should not break placeholder source-spans (#39589) (2b684b7), closes #39195
  • compiler-cli: avoid duplicate diagnostics about unknown pipes (#39517) (861e4fa)
  • compiler-cli: do not drop non-Angular decorators when downleveling (#39577) (1c6cf8a), closes #39574

10.2.2 (2020-11-04)

Bug Fixes

  • compiler-cli: report missing pipes when fullTemplateTypeCheck is disabled (#39320) (71d0063), closes #38195
  • core: markDirty() should only mark flags when really scheduling tick. (#39316) (8c82106), closes #39296
  • router: Ensure all outlets are used when commands have a prefix (#39456) (85d5242)

Performance Improvements

  • core: do not recurse into modules that have already been registered (#39514) (812355c), closes #39487

... (truncated)

Commits
  • ba8da74 fix(core): fix possible XSS attack in development through SSR (#40525)
  • 90570c0 fix(core): set ngDevMode to false when calling enableProdMode() (#40160)
  • 0b8e3d5 fix(core): fix possible XSS attack in development through SSR. (#40152)
  • 1aee8b3 refactor(compiler): store the fullStart location on ParseSourceSpans (#39...
  • 812355c perf(core): do not recurse into modules that have already been registered (#3...
  • 8f36c21 refactor(router): Small refactor of createUrlTree and extra tests (#39456)
  • 90acb91 docs: tView.preOrderHooks and tView.preOrderCheckHooks docs update (#39497)
  • 8c82106 fix(core): markDirty() should only mark flags when really scheduling tick. (#...
  • 0b37249 docs(core): update a typo in the comment of ngZoneEventCoalescing (#39423)
  • 3b779a1 docs: fix typo in initializeInputAndOutputAliases docstring (#39438)
  • Additional commits viewable in compare view
Maintainer changes

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


Dependabot compatibility score

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 [@angular/core](https://github.com/angular/angular/tree/HEAD/packages/core) from 7.2.7 to 10.2.5.
- [Release notes](https://github.com/angular/angular/releases)
- [Changelog](https://github.com/angular/angular/blob/10.2.5/CHANGELOG.md)
- [Commits](https://github.com/angular/angular/commits/10.2.5/packages/core)

---
updated-dependencies:
- dependency-name: "@angular/core"
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Jul 22, 2024
Copy link

dryrunsecurity bot commented Jul 22, 2024

DryRun Security Summary

The provided code change updates the package.json file of an Angular-based application called "Sengi" by upgrading the @angular/core dependency from version ^7.2.7 to ^10.2.5, which is a significant change that can have security implications and should be carefully reviewed and tested.

Expand for full summary

Summary:

The provided code change is an update to the package.json file, which is a crucial configuration file for an Angular-based application called "Sengi". The key change is the update of the @angular/core dependency from version ^7.2.7 to ^10.2.5. From an application security perspective, this change is noteworthy as it represents a significant upgrade to the Angular core version, which can have implications for the application's security posture.

Upgrading the Angular core version from 7.x to 10.x is a significant change that can include security fixes and improvements. It's important to carefully review the changes to ensure that the updated dependencies are compatible with the rest of the application's components and do not introduce any new vulnerabilities or breaking changes. Additionally, the application security engineer should review the Angular release notes and security advisories to understand the specific changes and their potential impact on the application's security. Regular dependency auditing, including both direct and transitive dependencies, is also recommended to identify any known vulnerabilities.

Files Changed:

  • package.json: The key change in this file is the update of the @angular/core dependency from version ^7.2.7 to ^10.2.5. This represents a significant upgrade to the Angular core version, which can have implications for the application's security posture and should be thoroughly reviewed and tested.

Code Analysis

We ran 9 analyzers against 2 files and 1 analyzer had findings. 8 analyzers had no findings.

Analyzer Findings
Sensitive Files Analyzer 2 findings

Riskiness

🟢 Risk threshold not exceeded.

View PR in the DryRun Dashboard.

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