fix floating point precision in closeTo assertion (#1667)

Support big int in approximently (#1606)

* Add `numeric` assertion

* Use `numeric` assertion in `approximately`

* Use home-made `abs` to support BigInt in `approximately`

* support bigint in "above" assertion

* add bigint test for typeOf

* add isNumeric and isNotNumeric to assert.js

* support BigInt in `atLeast`

* support bigint in `below`

* add support for bigint in `atMost`

* add bigint support to `within`

4.5.0

fix: support some virtual contexts in `toThrow` (#1609)

* fix: support some virtual contexts in `toThrow`

This adds support for VM situations where we pass a `RegExp` from
another process.

Note that we don't have a full fix for this stuff until `check-error`
also supports `Error` being from another origin.

* fix: support throwing of unusual errors

Adds support for throwing things like `undefined`, functions, etc.

* chore: upgrade check-error

Fix publish script (#1602)

* Don't publish to GPR

* Update node and actions versions

* Install playwright before testing and publishing

5.0.3

Fix 1564 (#1566)

* add function assertions

* implement function checks in expect interface

* fix flag message

* correctly reference inspect

* use existing assersions in asserts

* Fix typo

Co-authored-by: San Mônico <alanderson_laird@yahoo.com.br>

* Add `AsyncGeneratorFunction` assertion

* update assertion messages

* alias `isFunction` to `isCallable`

* Square up boolean logic in `isCallable` function

* Update callable JSDoc comment

* Add error tests for function expect assertions

* Add negation to other callable assertions

* Convert expect calls in test to type string assertions

* Remove assertion properties in favor of a normal type assertion

* Remove `.is{FunctionType}` assert interfaces

* Move `functionTypes` object

* Add a bunch of tests

* Move test

* Add more tests to should interface

* Revert formatting change

* Add should test for `callable`

---------

Co-authored-by: San Mônico <alanderson_laird@yahoo.com.br>

fix: removes `??` for node compat (#1574)

We shipped syntax which is beyond our `engine` constraint. `??` is
available in node 14 but 4.x is node 4 and above, while 5.x is node 12
and above.

This just dumbs it back down to `||` for now at least.

Fixes #1573

bump version

5.0.1