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

Update package.json dependencies to latest versions #2746

Closed
DonJayamanne opened this issue Oct 2, 2018 · 3 comments
Closed

Update package.json dependencies to latest versions #2746

DonJayamanne opened this issue Oct 2, 2018 · 3 comments
Assignees
Labels
debt Covers everything internal: CI, testing, refactoring of the codebase, etc. important Issue identified as high-priority

Comments

@DonJayamanne
Copy link

DonJayamanne commented Oct 2, 2018

We need to do this before we end up in a situation where our dependencies are too old.
We've been caught out to this in the past, and once again now #2745.
Need to review all dependencies and update for the next release.

@DonJayamanne DonJayamanne changed the title Update dependencies to latest versions Update package.json dependencies to latest versions Oct 2, 2018
@DonJayamanne DonJayamanne added needs PR debt Covers everything internal: CI, testing, refactoring of the codebase, etc. important Issue identified as high-priority labels Oct 2, 2018
@DonJayamanne
Copy link
Author

@brettcannon @qubitron
Please could you ensure this gets added into the next sprint.

@brettcannon
Copy link
Member

This is a matter of us getting on to Component Governance, as that will let us unpin our dependencies, but that's a bigger task as it requires setting up a parallel build of the extension internally in Azure DevOps.

@brettcannon
Copy link
Member

We are now registered with Component Governance, so we can now begin unpinning our dependencies. We should probably start by switching to the carrot operator and see how that goes and then consider further upgrade beyond that on a case-by-case basis.

@brettcannon brettcannon self-assigned this Oct 17, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Nov 14, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
debt Covers everything internal: CI, testing, refactoring of the codebase, etc. important Issue identified as high-priority
Projects
None yet
Development

No branches or pull requests

2 participants