Skip to content

Commit

Permalink
Bump version to 2.0.0
Browse files Browse the repository at this point in the history
  • Loading branch information
sgravrock committed May 13, 2023
1 parent 6e64034 commit 1e7a982
Show file tree
Hide file tree
Showing 2 changed files with 51 additions and 4 deletions.
8 changes: 4 additions & 4 deletions package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "jasmine-browser-runner",
"version": "2.0.0-beta.1",
"version": "2.0.0",
"description": "Serve and run your Jasmine specs in a browser",
"bin": "bin/jasmine-browser-runner",
"exports": "./index.js",
Expand Down Expand Up @@ -43,14 +43,14 @@
"selenium-webdriver": "^4.8.2"
},
"peerDependencies": {
"jasmine-core": "^5.0.0-beta.0"
"jasmine-core": "^5.0.0"
},
"devDependencies": {
"ejs-lint": "^2.0.0",
"eslint": "^8.38.0",
"eslint-plugin-jasmine": "^4.1.3",
"jasmine": "^5.0.0-beta.0",
"jasmine-core": "^5.0.0-beta.0",
"jasmine": "^5.0.0",
"jasmine-core": "^5.0.0",
"prettier": "^1.17.1",
"shelljs": "^0.8.3",
"temp": "^0.9.4"
Expand Down
47 changes: 47 additions & 0 deletions release_notes/2.0.0.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,47 @@
# jasmine-browser-runner 2.0.0 Release Notes

This is a major release that includes breaking changes. Please see the
[Jasmine 5 migration guide](https://jasmine.github.io/tutorials/upgrading_to_Jasmine_5.0)
in addition to reading the list of changes below.

## Breaking changes

* jasmine-core peer dependency has been updated to 5.0.
* Dropped support for Node 12, 14, and 16
* Dropped support for Safari 14 and Firefox 91
* Backslashes in file globs (e.g. `spec_files`) are treated as escape characters
on all platforms. Previously they were treated as directory separators on
Windows and escape characters elsewhere.

## New features

* Made ES module file extension configurable
* Fixes [#22](https://github.com/jasmine/jasmine-browser-runner/issues/22).
* Opt-in support for top-level-await in ES modules

This can be enabled by adding enableTopLevelAwait: true to the configuration.
It's off by default because HTTP requests for scripts are performed
sequentially rather than potentially in parallel. This comes at a cost in
performance but is the only way to ensure a stable order when randomization
is disabled or a random seed is specified.

## Internal improvements

* Updated dev dependencies
* Removed leftover Safari <12 support code

## Supported environments

This version has been tested in the following environments.

| Environment | Supported versions |
|-------------------|--------------------|
| Node | 18, 20 |
| Safari | 15-16 |
| Chrome | 113 |
| Firefox | 102, 113 |
| Edge | 113 |

------

_Release Notes generated with _[Anchorman](http://github.com/infews/anchorman)_

0 comments on commit 1e7a982

Please sign in to comment.