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

Release 0.16.0 #1603

Merged
merged 2 commits into from
Jun 10, 2020
Merged

Release 0.16.0 #1603

merged 2 commits into from
Jun 10, 2020

Conversation

pquentin
Copy link
Member

@pquentin pquentin commented Jun 10, 2020

Note that with the new process, I'll merge this myself when the release is over.

@codecov
Copy link

codecov bot commented Jun 10, 2020

Codecov Report

Merging #1603 into master will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master    #1603   +/-   ##
=======================================
  Coverage   99.69%   99.69%           
=======================================
  Files         110      110           
  Lines       13838    13838           
  Branches     1057     1057           
=======================================
  Hits        13796    13796           
  Misses         27       27           
  Partials       15       15           
Impacted Files Coverage Δ
trio/_version.py 100.00% <100.00%> (ø)

@pquentin
Copy link
Member Author

Failed due to #1604. Cycling.

@pquentin pquentin closed this Jun 10, 2020
@pquentin pquentin reopened this Jun 10, 2020
@pquentin
Copy link
Member Author

#1604 again. :( Third time's a charm?

@pquentin pquentin closed this Jun 10, 2020
@pquentin pquentin reopened this Jun 10, 2020
@pquentin pquentin merged commit f63dc0c into python-trio:master Jun 10, 2020
@pquentin pquentin deleted the release-0.16 branch June 10, 2020 06:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant