Bump jasmine-core from 2.8.0 to 3.1.0

[dependabot-preview]

Bumps jasmine-core from 2.8.0 to 3.1.0.

Release notes

Sourced from jasmine-core's releases.

3.1.0

Please see the release notes

3.0.0

Please see the release notes

2.99.2

This is a patch release for the Ruby Gem to fix a bug in the packaging.

2.99.1

This is a patch release to fix the deprecation message for catch exceptions in 2.99

See #1497

2.99

This release deprecates some things in preparation for Jasmine 3.0. Please see the release notes

2.9.1

Please see the release notes

2.9.0

Please see the release notes

Changelog

Sourced from jasmine-core's changelog.

How to work on a Jasmine Release

Development

Jasmine Core Maintainers Only

Follow the instructions in CONTRIBUTING.md during development.

Git Rules

Please attempt to keep commits to master small, but cohesive. If a feature is contained in a bunch of small commits (e.g., it has several wip commits or small work), please squash them when pushing to master.

Version

We attempt to stick to Semantic Versioning. Most of the time, development should be against a new minor version - fixing bugs and adding new features that are backwards compatible.

The current version lives in the file /package.json. This version will be the version number that is currently released. When releasing a new version, update package.json with the new version and grunt build:copyVersionToGem to update the gem version number.

This version is used by both jasmine.js and the jasmine-core Ruby gem.

Note that Jasmine should only use the "patch" version number in the following cases:

• Changes related to packaging for a specific platform (npm, gem, or pip).
• Fixes for regressions.

When jasmine-core revs its major or minor version, the binding libraries should also rev to that version.

Release

When ready to release - specs are all green and the stories are done:

1. Update the release notes in release_notes - use the Anchorman gem to generate the markdown file and edit accordingly
2. Update the version in package.json to a release candidate
3. Update any links or top-level landing page for the Github Pages

Build standalone distribution

1. Build the standalone distribution with grunt buildStandaloneDist

Release the Python egg

Install twine

1. python setup.py sdist
2. twine upload dist/jasmine-core-<version>.tar.gz You will need pypi credentials to upload the egg.

Release the Ruby gem

1. Copy version to the Ruby gem with grunt build:copyVersionToGem
2. NOTE: You will likely need to point to a local jasmine gem in order to run tests locally. Do not push this version of the Gemfile.
3. NOTE: You will likely need to push a new jasmine gem with a dependent version right after this release.
   ... (truncated)

Commits

• 557fb4e proper links in release notes
• ee52023 Bump version to 3.1
• 91296a4 Remove Safari 7 from Travis matrix
• 1923461 Ignore more browser fields when formatting Errors
• 71116d3 don't lock to 2.99 in dev
• 63cc7ca Use Jasmine's arrayContains, instead of includes for better support
• fdecf02 Merge branch 'print_exception_properties' of https://github.com/jbunton-atlas...
• 11f4d89 Merge branch 'node-load-errors'
• 1149d4e Use j$.pp instead of JSON.stringify() for pretty printing
• 9ee85c3 Remove duplicate ignored property
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

If you'd like to skip this version, you can just close this PR. If you have any feedback just mention @dependabot in the comments below.

---

Note: This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit.

You can always request more updates by clicking Bump now in your Dependabot dashboard.