Skip to content

Update dependency karma-jasmine to v4 #33

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

mend-for-github-com[bot]
Copy link
Contributor

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
karma-jasmine ~1.1.2 -> ~4.0.0 age adoption passing confidence

Release Notes

karma-runner/karma-jasmine

v4.0.1

Compare Source

Bug Fixes

v4.0.0

Compare Source

chore
BREAKING CHANGES
  • Drop support for node 8 (add support for node 14)

3.3.1 (2020-05-28)

Bug Fixes

v3.3.1

Compare Source

Bug Fixes

v3.3.0

Compare Source

Features
  • reporter: emit info events for suiteStarted/suiteDone (#​269) (7b73ce0)

v3.2.0

Compare Source

Features
  • results: forward passedExpectations and properties (#​268) (ad1d7dd)

3.1.1 (2020-02-11)

Bug Fixes

v3.1.1

Compare Source

Bug Fixes

v3.1.0

Compare Source

Features

3.0.3 (2020-01-08)

Bug Fixes

3.0.2 (2020-01-08)

3.0.1 (2020-01-06)

Bug Fixes
Chores
Features
BREAKING CHANGES
  • drop support for node v6

  • Also update travis config to drop v6 andd v10

  • stopOnFailure, which was previously documented in karma-jasmine's README, is
    not configuration option for jasmine. Use oneFailurePerSpec instead.

Requires peerDependency Jasmine@^3.3.0

  • deps: Drop support for node 4.x

v3.0.3

Compare Source

Bug Fixes

v3.0.1

Compare Source

Bug Fixes
Chores
Features
BREAKING CHANGES
  • drop support for node v6

  • Also update travis config to drop v6 andd v10

  • stopOnFailure, which was previously documented in karma-jasmine's README, is
    not configuration option for jasmine. Use oneFailurePerSpec instead.

Requires peerDependency Jasmine@^3.3.0

  • deps: Drop support for node 4.x

v3.0.0

Compare Source

Bug Fixes
  • build: run eslint on npm test (#​237) (a12024d)
  • stack: On error in beforeAll/afterAll relevant information to debug are miss… (#​232) (cd6f060)
  • travis: use new syntax for xenial and pin to it. (#​236) (cb99ef8)
Features
  • adapter: log when Jasmine fails because no expect() were run (#​238) (646796e)
  • reporter: On no-single-run and failure, emit a debug URL (#​235) (76f092a)
BREAKING CHANGES
  • drop support for node v6

  • Also update travis config to drop v6 andd v10

2.0.1 (2018-11-17)

Bug Fixes
  • dep: Depend upon the jasmine-core version we test (#​229) (c4dfef5)

v2.0.1

Compare Source

Bug Fixes
  • dep: Depend upon the jasmine-core version we test (#​229) (c4dfef5)

v2.0.0

Compare Source

Bug Fixes
Chores
Features
  • Propagate errors thrown in afterAll blocks (f3fa264), closes #​161
  • update the version to 2.0.0 and restrict node version available to 4.0 (c84316e)
BREAKING CHANGES
  • stopOnFailure, which was previously documented in karma-jasmine's README, is
    not configuration option for jasmine. Use oneFailurePerSpec instead.

Requires peerDependency Jasmine@^3.3.0

  • deps: Drop support for node 4.x

1.1.2 (2018-05-02)

Bug Fixes
Features
  • Propagate errors thrown in afterAll blocks (f3fa264), closes #​161
  • update the version to 2.0.0 and restrict node version available to 4.0 (c84316e)

1.1.1 (2017-12-01)

Features
  • Propagate errors thrown in afterAll blocks (f3fa264), closes #​161

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants