Skip to content

Please merge revision #19442451d70bc5c7384f9669425cfcea1b05d368 into dev channel #26300

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.

Sign up for GitHub

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

Jump to bottom
Closed
munificent opened this issue Apr 19, 2016 · 2 comments
Closed

Please merge revision #19442451d70bc5c7384f9669425cfcea1b05d368 into dev channel #26300

munificent opened this issue Apr 19, 2016 · 2 comments
Labels
merge-to-dev
Milestone
1.16

Comments

@munificent
Copy link
Member

munificent commented Apr 19, 2016 •
edited
Loading

@whesse @mit-mit @kasperl

Fixes a bug I introduced in pub in 1.16.0-dev.5.

See #26295, and pub/#1407.

This is just revving the version of pub in the SDK, so it's a one-line DEPS change in 19442451d70bc5c7384f9669425cfcea1b05d368.

Thanks!
@munificent munificent added this to the 1.16 milestone Apr 19, 2016
@munificent
Copy link
Member Author

Actually, it turns out that revision is no good because it doesn't work with the version of the crypto package that's in the repo. Instead, we'll want to use this one once it lands:

https://codereview.chromium.org/1901053004

@whesse
Copy link
Contributor

whesse commented Apr 20, 2016

Merged in version 1.16.0-dev.5.3, before it was landed on master.

@whesse whesse closed this as completed Apr 20, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
merge-to-dev
Projects
None yet
Milestone
1.16
Development

No branches or pull requests
2 participants
@munificent @whesse