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.2.9 #3561

Merged
merged 3 commits into from
Jun 9, 2020
Merged

Release - 1.2.9 #3561

merged 3 commits into from
Jun 9, 2020

Conversation

ryanio
Copy link
Collaborator

@ryanio ryanio commented Jun 2, 2020

Description

This PR introduces web3.js version 1.2.9 beginning with 1.2.9-rc.0.

Release notes

In addition to dependency updates, small bug fixes for the ABI Coder change in 1.2.8, and many documentation improvements, this release extends the transaction event API for more granular tracking of transaction submissions.

These additions were proposed by client engineer @benjamincburns in #3438 and should:

The new / changed Promievents are:

Event Description Handler args
sending Fired immediately before transmitting the transaction request, after all intermediate requests such as eth_chainId, eth_estimateGas, or eth_gasPrice have completed. transactionPayload
sent Fired immediately after the request body has been written to the client, but before the transaction hash is received transactionPayload
confirmation Behaves as it does today, but includes the block hash for the most recently mined block in the event handler arguments confNumber, receipt, latestBlockHash

Also of note...

As reported in #3432 by @dmihal, Web3 has long had some interaction issues with provider middle-ware like web3-provider-engine that uses http and provides an event emitter interface. The library has assumed that these packages support subscription endpoints when they don't. This bug should be fixed by PR #3517.

Changelog

Added

Changed

Fixed

Compare View

v1.2.8 -> v1.2.9-rc.0

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 new warnings.
  • Any dependent changes have been merged and published in downstream modules.
  • I ran npm run dtslint with success and extended the tests and types if necessary.
  • I ran npm run test:unit with success.
  • I ran npm run test:cov and my test cases cover all the lines and branches of the added code.
  • I ran npm run build-all and tested the resulting files from dist folder in a browser.
  • I have updated the CHANGELOG.md file in the root folder.
  • I have tested my code on the live network.

@ryanio ryanio added Release 1.x 1.0 related issues labels Jun 2, 2020
@coveralls
Copy link

coveralls commented Jun 2, 2020

Coverage Status

Coverage remained the same at 89.855% when pulling 0e7ee33 on release/1.2.9 into f52bf55 on 1.x.

@cgewecke
Copy link
Collaborator

cgewecke commented Jun 3, 2020

As part of the RC process, am doing some test installations in other projects and running their tests to see if everything.

  • installs properly
  • builds
  • tests pass

This list will be actively edited:

Project Desc Status
oz-test-helpers Test utils. Subset of their suite is web3 contracts
gnosis/dex-react TS React app ~200 tests + webpack build + jest
synthetix ~1000 units

Live test from CI at http://sudden-playground.surge.sh/

Screen Shot 2020-06-03 at 3 59 00 PM

edit from ryan: we have changed from surge to netlify in #3575

@cgewecke cgewecke self-requested a review June 9, 2020 19:05
Copy link
Collaborator

@cgewecke cgewecke left a comment

Choose a reason for hiding this comment

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

LGTM!

@ryanio ryanio merged commit 8ff9d6d into 1.x Jun 9, 2020
@GregTheGreek GregTheGreek deleted the release/1.2.9 branch July 26, 2020 04:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.x 1.0 related issues Release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants