Releases: simon360/jest-environment-jsdom-global
Releases · simon360/jest-environment-jsdom-global
v4.0.0: Jest 29 and EOL for Node 12
v3.1.2: Bug fix
v3.1.1: README updates
An update to the README, explaining some changes in Jest 28 that may, in some cases, remove the need to use jest-environment-jsdom-global
.
v3.1.0: Jest 28 support
New features
- Includes compatibility with Jest 28
- Maintains compatibility with older versions of Jest. This will be dropped in a future version, but am doing this as a courtesy while everyone gets up to a newer Jest version.
Internal changes
- Updated all packages
- Added a CI stage that tests on older versions of Jest and
jest-environment-jsdom
v3.0.0: Jest 27 support + general hygiene
Breaking changes:
- Node >= 12 is now required. Node 10 is out of mainstream support, so I've dropped support here, too
jest-environment-jsdom-sixteen
is no longer supported. Jest > 26 includes support out of the box. If you requirejest-environment-jsdom-sixteen
, continue using the latestv2.x
release of this package
Minor changes:
- Adds Jest 27 to the peer dependency range
Internal
- All dependencies have been updated to the latest versions
- The primary branch has been renamed from
master
tomain
v2.0.4: Update docs for JSDOM 16
Changelog
- docs: Add a version disclaimer for JSDOM 16 (#38)
v2.0.3: Add support for Jest 26
Update dependencies and remove GitHub Package Registry publishing
- chore: remove GitHub Package Registry publish script
- chore: update all packages
Publish to GitHub Package Registry
A bug in the release script caused publishes to GPR to fail.
v2.0.0: Support for jest-environment-jsdom-sixteen
feat: add support for jest-environment-jsdom-sixteen
BREAKING CHANGES
- in some cases, if jest-environment-jsdom-sixteen is resolvable, and Jest is running on Node 8 or lower, test suites may begin failing. This may happen if a subdependency of your project has jest-environment-jsdom-sixteen as a dependency, instead of a devDependency.