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

Upgrade angular to 6.1.1 to fix security vulnerability #2850

Merged
merged 8 commits into from
Aug 24, 2018

Conversation

irfanhabib
Copy link
Contributor

@irfanhabib irfanhabib commented Aug 17, 2018

Fixes #2851
This updates to angular 6.1.1 (from 6.0.3). The dependency that introduced the security vulnerability was imported by @angular-devkit/build-angular and is fixed by 0.7.4.

@cfdreddbot
Copy link

Hey irfanhabib!

Thanks for submitting this pull request! I'm here to inform the recipients of the pull request that you and the commit authors have already signed the CLA.

@codecov
Copy link

codecov bot commented Aug 17, 2018

Codecov Report

Merging #2850 into v2-master will increase coverage by <.01%.
The diff coverage is 83.13%.

@@              Coverage Diff              @@
##           v2-master    #2850      +/-   ##
=============================================
+ Coverage      71.35%   71.35%   +<.01%     
=============================================
  Files            604      604              
  Lines          25857    25859       +2     
  Branches        5855     5859       +4     
=============================================
+ Hits           18449    18452       +3     
+ Misses          7408     7407       -1

@@ -68,12 +68,13 @@ export class CurrentUserPermissionsChecker {
filter(state => !!state),
map(state => {
const permissionString = permission as PermissionStrings;
let orgOrSpaceState;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should rename the variable rather than using let here.

@@ -122,6 +122,7 @@ export class DeployApplicationStep2Component
this.stepperText = 'Review source details';
}

let action;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Again, we should try to avoid using let.

const filterStoreToWidget = this.paginationController.filter$.pipe(tap((filter: ListFilter) => {
this.filterString = filter.string;
this.multiFilters = { ...filter.items };
const filterStoreToWidget = this.paginationController.filter$.pipe(tap((f: ListFilter) => {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we rename f to paginationFilter? Just to be a little more explicit.

@richard-cox richard-cox merged commit 1b5da18 into v2-master Aug 24, 2018
@richard-cox richard-cox deleted the fix-cve2018-3774 branch August 24, 2018 14:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Fix security vulnerability CVE-2018-3774 introduced by nested dependency
4 participants