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 - 1.0.0-beta.52 #2649

Merged
merged 4 commits into from
Apr 4, 2019
Merged

Release - 1.0.0-beta.52 #2649

merged 4 commits into from
Apr 4, 2019

Conversation

nivida
Copy link
Contributor

@nivida nivida commented Apr 4, 2019

Fixed issues

Compare view beta.51 - beta.52

Type of change

  • Release

Checklist:

  • I have selected the correct base branch.
  • I have performed a self-review of my own code.
  • I have commented my code, particularly in hard-to-understand areas.
  • I have made corresponding changes to the documentation.
  • My changes generate no warnings.
  • I have updated or added types for all modules I've changed
  • Any dependent changes have been merged and published in downstream modules.
  • I ran npm run test in the root folder with success and extended the tests if necessary.
  • I ran npm run build in the root folder and tested it in the browser and with node.
  • I ran npm run dtslint in the root folder and tested that all my types are correct
  • I have tested my code on an ethereum test network.

@nivida nivida added Release In Progress Currently being worked on labels Apr 4, 2019
@coveralls
Copy link

Coverage Status

Coverage remained the same at 95.376% when pulling db28ca4 on release/1.0.0-beta.52 into 512c189 on 1.0.

@coveralls
Copy link

coveralls commented Apr 4, 2019

Coverage Status

Coverage decreased (-0.002%) to 95.374% when pulling 1c89f50 on release/1.0.0-beta.52 into 512c189 on 1.0.

@nivida nivida removed the In Progress Currently being worked on label Apr 4, 2019
@nivida nivida merged commit bb7827d into 1.0 Apr 4, 2019
@nivida nivida deleted the release/1.0.0-beta.52 branch April 4, 2019 18:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants