Skip to content

[feat]partially upgrade dependencies #3515

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

Closed
wants to merge 10 commits into from
Closed

Conversation

e-cloud
Copy link
Contributor

@e-cloud e-cloud commented Dec 11, 2016

The PR upgrade some of dependencies that doesn't need big code changes, and provide a script for better dependencies management.

Fix #3504

@googlebot
Copy link

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.


  • If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
  • If you signed the CLA as a corporation, please let us know the company's name.

@e-cloud
Copy link
Contributor Author

e-cloud commented Dec 11, 2016

I signed it!

@googlebot
Copy link

CLAs look good, thanks!

@hansl
Copy link
Contributor

hansl commented Dec 16, 2016

Hi. Please rebase; we updated a bunch of other dependencies already. I'll review once this PR is up to date.

@hansl hansl self-requested a review December 16, 2016 21:57
@e-cloud
Copy link
Contributor Author

e-cloud commented Dec 17, 2016

@hansl it's rebased now.

@hansl
Copy link
Contributor

hansl commented Dec 17, 2016

Seems like this PR is a mess now. The changes to validate_dependencies are weird and the sync-deps doesn't seem to work...

@e-cloud
Copy link
Contributor Author

e-cloud commented Dec 18, 2016

My mistake! @hansl sorry, what i want is to check the dependencies version across the packages in this repo. Perhaps i should not exit with 1, a warning it's better.

Do you think it's reasonable? What's the weird part you are talking about?

@e-cloud e-cloud force-pushed the update-deps branch 3 times, most recently from 72687c3 to d665f83 Compare December 24, 2016 12:31
@e-cloud
Copy link
Contributor Author

e-cloud commented Dec 24, 2016

@hansl please have a review :).

@ghost
Copy link

ghost commented Dec 30, 2016

@e-cloud fix conflicts please

@e-cloud
Copy link
Contributor Author

e-cloud commented Dec 30, 2016

conflicts resolved and I don't upgrade the yarn.lock @hansl

@e-cloud e-cloud force-pushed the update-deps branch 3 times, most recently from fe88671 to cdfbbb8 Compare January 10, 2017 01:08
@e-cloud
Copy link
Contributor Author

e-cloud commented Jan 10, 2017

@hansl Would you give some time to review this? or just let it be? You can close this PR if not your desire.

@e-cloud e-cloud force-pushed the update-deps branch 3 times, most recently from 22191c8 to c820f83 Compare January 23, 2017 05:56
and increase the timeout for computer with low io rate
adjust eslint config, and adjust some code to fit the style.
not upgrading to v1.2 is because it require extra config file. That should be determine by the maintainer.
@e-cloud
Copy link
Contributor Author

e-cloud commented Jan 24, 2017

@hansl request for review

@e-cloud
Copy link
Contributor Author

e-cloud commented Feb 8, 2017

will split the PR into two

@e-cloud e-cloud closed this Feb 8, 2017
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 11, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Suggestion]Better dependencies management of the repo
3 participants