Skip to content

ci: use --frozen-lockfile #6841

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

Merged
merged 1 commit into from
Jun 29, 2017
Merged

Conversation

filipesilva
Copy link
Contributor

Use yarn --frozen-lockfile to ensure up to date dependencies.

Thanks to @ishitatsuyuki for pushing for this change.

Followup to #6254, #6772.
Fix #6237.

Use `yarn --frozen-lockfile` to ensure up to date dependencies.

Thanks to @ishitatsuyuki for pushing for this change.

Followup to angular#6254, angular#6772.
Fix angular#6237.
Copy link
Contributor

@Brocco Brocco left a comment

Choose a reason for hiding this comment

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

LGTM

@filipesilva filipesilva merged commit ba5be21 into angular:master Jun 29, 2017
@filipesilva filipesilva deleted the frozen-lockfile branch June 29, 2017 18:09
@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 12, 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.

CI: take care of yarn.lock
3 participants