1.8.2

[jdevcs]

Changed

• Updated Webpack 4 to Webpack 5, more details at (Update 1.x build tools #5629)
• crypto-browserify module is now used only in webpack builds for polyfilling browsers (Update 1.x build tools #5629)
• Updated ethereumjs-util to 7.1.5 (Update 1.x build tools #5629)
• Updated lerna 4 to version 6 (5629/lerna #5680)
• Bump utils 0.12.0 to 0.12.5 (chore(deps): bump util from 0.12.0 to 0.12.5 #5691)

Fixed

• Fixed types for web3.utils._jsonInterfaceMethodToString (Fix: _jsonInterfaceMethodToString export in types #5550)
• Fixed Next.js builds failing on Node.js v16, Abortcontroller added if it doesn't exist globally (Next.js, node.js 16 TypeError: Cannot set property Request of #<Object> which has only a getter #5601)
• Builds fixed by updating all typescript versions to 4.1 (1.x build failing due to types error #5675)

Removed

• clean-webpack-plugin has been removed from dev-dependencies (Update 1.x build tools #5629)

Added

• https-browserify, process, stream-browserify, stream-http, crypto-browserify added to dev-dependencies for polyfilling (Update 1.x build tools #5629)
• Add readable-stream to dev-dependancies for webpack (Update 1.x build tools #5629)

Security

• npm audit fix for libraries update (1.x dependencies update #5726)

[coveralls]

Pull Request Test Coverage Report for Build 3886282402

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 269 unchanged lines in 7 files lost coverage.
• Overall coverage increased (+2.4%) to 75.028%

---

Files with Coverage Reduction	New Missed Lines	%
packages/web3-core-requestmanager/src/jsonrpc.js	2	64.29%
packages/web3-core-helpers/src/formatters.js	8	84.3%
packages/web3-core-helpers/src/errors.js	29	1.56%
packages/web3-utils/src/soliditySha3.js	34	3.43%
packages/web3-utils/src/index.js	40	40.3%
packages/web3-utils/src/utils.js	45	10.67%
packages/web3-eth-accounts/src/index.js	111	22.94%

Totals
Change from base Build 3886244727:	2.4%
Covered Lines:	3299
Relevant Lines:	4146

---

💛 - Coveralls

[jdevcs]

As part of the RC process, following test installations are performed 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
synthetix	~1000 units

[luu-alex]

When running synthetix, I got a few errors

edit:

ISSUE RESOLVED ✅

[luu-alex]

Openzeppelin tests are passing ✅

[avkos]

synthetix test results

 4435 passing (1h)
  71 pending
  1 failing

  1) Contract: SupplySchedule
       functions and modifiers
         Given inflation amount of 800,000 - mintable supply
           should calculate the mintable supply as 0 within 1st week of inflation start date:
     Error: Time parameter (Wed Mar 06 2019 23:00:00 GMT-0500 (Eastern Standard Time)) is less than now Wed Mar 06 2019 23:11:08 GMT-0500 (Eastern Standard Time). You can only fast forward to times in the future.
      at fastForwardTo (test/utils/index.js:111:10)
      at runMicrotasks (<anonymous>)
      at processTicksAndRejections (node:internal/process/task_queues:96:5)
      at Context.<anonymous> (test/contracts/SupplySchedule.js:205:5)

@openzeppelin/test-helpers finished with errors:

 275 passing (55s)
  3 failing

  1) expectRevert
       expectRevert
         rejects a revert with incorrect expected reason:

      AssertionError: expected 'VM Exception while processing transac…' to equal 'Call to revert'
      + expected - actual

      -VM Exception while processing transaction: revert Call to revert
      +Call to revert
      
      at Context.<anonymous> (test/src/expectRevert.test.js:34:35)

  2) expectRevert
       assertion
         rejects an outOfGas:
     AssertionError: expect.fail()
      at assertFailure (test/helpers/assertFailure.js:9:10)
      at runMicrotasks (<anonymous>)
      at processTicksAndRejections (node:internal/process/task_queues:96:5)
      at Context.<anonymous> (test/src/expectRevert.test.js:123:7)

  3) expectRevert
       outOfGas
         accepts an outOfGas:

      Wrong kind of exception received
      + expected - actual

      -Transaction: 0x30de5aa6fcc2811d6a7407af251c16b423e14efe5219ebfd895a273de802c567 exited with an error (status 0) after consuming all gas.
      -     Please check that the transaction:
      -     - satisfies all conditions set by Solidity `assert` statements.
      -     - has enough gas to execute the full transaction.
      -     - does not trigger an invalid opcode by other means (ex: accessing an array out of bounds).
      +out of gas
      
      at expectException (src/expectRevert.js:20:30)
      at runMicrotasks (<anonymous>)
      at processTicksAndRejections (node:internal/process/task_queues:96:5)
      at Context.<anonymous> (test/src/expectRevert.test.js:153:7)

[luu-alex]

I just checked and the all failing testcases I have mentioned have been reported by me since a year ago. I don't believe anything has changed.

[jdevcs]

I just checked and the all failing testcases I have mentioned have been reported by me since a year ago. I don't believe anything has changed.

Thanks @luu-alex , @avkos and @Muhammad-Altabba #5760

[jdevcs]

We will include #5752 in this release if there are any code changes required , discussed in web3 team meeting.

[jdevcs]

There are no code changes required for fixing #5752 in #5779 , only test code is changed so we will include/merge this PR in next release.