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 - 2.0.0-alpha.1 #3006

Merged
merged 4 commits into from
Aug 6, 2019
Merged

Release - 2.0.0-alpha.1 #3006

merged 4 commits into from
Aug 6, 2019

Conversation

nivida
Copy link
Contributor

@nivida nivida commented Aug 5, 2019

Description

Added

Changed

Fixed

Compare View

v2.0.0-alpha -> v2.0.0-alpha.1

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 to cover all changes.
  • I ran npm run build in the root folder and tested it in the browser and with node.
  • I have tested my code with an ethereum test network.

@nivida nivida added In Progress Currently being worked on Release 2.x 2.0 related issues labels Aug 5, 2019
@coveralls
Copy link

coveralls commented Aug 5, 2019

Coverage Status

Coverage remained the same at 95.371% when pulling cb266cc on release/2.0.0-alpha.1 into 55a6a9f on 2.x.

@nivida nivida removed the In Progress Currently being worked on label Aug 6, 2019
@nivida nivida merged commit 58a4432 into 2.x Aug 6, 2019
@nivida nivida deleted the release/2.0.0-alpha.1 branch August 6, 2019 11:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2.x 2.0 related issues Release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants