jasmine-core
Advanced tools
Comparing version 3.6.0 to 3.7.0
@@ -104,3 +104,3 @@ # Developing for Jasmine Core | ||
$ node ci.js | ||
$ node spec/support/ci.js | ||
@@ -107,0 +107,0 @@ You can also set the `JASMINE_BROWSER` environment variable to specify which browser should be used. |
/* | ||
Copyright (c) 2008-2020 Pivotal Labs | ||
Copyright (c) 2008-2021 Pivotal Labs | ||
@@ -4,0 +4,0 @@ Permission is hereby granted, free of charge, to any person obtaining |
/* | ||
Copyright (c) 2008-2020 Pivotal Labs | ||
Copyright (c) 2008-2021 Pivotal Labs | ||
@@ -135,3 +135,3 @@ Permission is hereby granted, free of charge, to any person obtaining | ||
} | ||
addDeprecationWarnings(result); | ||
addDeprecationWarnings(result, 'suite'); | ||
}; | ||
@@ -172,3 +172,3 @@ | ||
addDeprecationWarnings(result); | ||
addDeprecationWarnings(result, 'spec'); | ||
}; | ||
@@ -312,10 +312,23 @@ | ||
var warningBarClassName = 'jasmine-bar jasmine-warning'; | ||
for (i = 0; i < deprecationWarnings.length; i++) { | ||
var warning = deprecationWarnings[i]; | ||
var context; | ||
switch (deprecationWarnings[i].runnableType) { | ||
case 'spec': | ||
context = '(in spec: ' + deprecationWarnings[i].runnableName + ')'; | ||
break; | ||
case 'suite': | ||
context = '(in suite: ' + deprecationWarnings[i].runnableName + ')'; | ||
break; | ||
default: | ||
context = ''; | ||
} | ||
alert.appendChild( | ||
createDom( | ||
'span', | ||
{ className: warningBarClassName }, | ||
'DEPRECATION: ' + warning | ||
{ className: 'jasmine-bar jasmine-warning' }, | ||
'DEPRECATION: ' + deprecationWarnings[i].message, | ||
createDom('br'), | ||
context | ||
) | ||
@@ -631,3 +644,3 @@ ); | ||
function addDeprecationWarnings(result) { | ||
function addDeprecationWarnings(result, runnableType) { | ||
if (result && result.deprecationWarnings) { | ||
@@ -637,3 +650,7 @@ for (var i = 0; i < result.deprecationWarnings.length; i++) { | ||
if (!j$.util.arrayContains(warning)) { | ||
deprecationWarnings.push(warning); | ||
deprecationWarnings.push({ | ||
message: warning, | ||
runnableName: result.fullName, | ||
runnableType: runnableType | ||
}); | ||
} | ||
@@ -640,0 +657,0 @@ } |
/* | ||
Copyright (c) 2008-2020 Pivotal Labs | ||
Copyright (c) 2008-2021 Pivotal Labs | ||
@@ -4,0 +4,0 @@ Permission is hereby granted, free of charge, to any person obtaining |
{ | ||
"name": "jasmine-core", | ||
"license": "MIT", | ||
"version": "3.6.0", | ||
"version": "3.7.0", | ||
"repository": { | ||
@@ -16,5 +16,5 @@ "type": "git", | ||
"scripts": { | ||
"posttest": "eslint \"src/**/*.js\" \"spec/**/*.js\" && prettier --check src/**/*.js spec/**/*.js", | ||
"posttest": "eslint \"src/**/*.js\" \"spec/**/*.js\" && prettier --check \"src/**/*.js\" \"spec/**/*.js\"", | ||
"test": "grunt --stack execSpecsInNode", | ||
"cleanup": "prettier --write src/**/*.js spec/**/*.js", | ||
"cleanup": "prettier --write \"src/**/*.js\" \"spec/**/*.js\"", | ||
"build": "grunt buildDistribution", | ||
@@ -44,3 +44,3 @@ "serve": "node spec/support/localJasmineBrowser.js", | ||
"jasmine": "^3.4.0", | ||
"jasmine-browser-runner": "github:jasmine/jasmine-browser", | ||
"jasmine-browser-runner": "^0.4.0", | ||
"jsdom": "^15.0.0", | ||
@@ -47,0 +47,0 @@ "load-grunt-tasks": "^4.0.0", |
<a name="README">[<img src="https://rawgithub.com/jasmine/jasmine/main/images/jasmine-horizontal.svg" width="400px" />](http://jasmine.github.io)</a> | ||
[![Build Status](https://travis-ci.org/jasmine/jasmine.svg?branch=main)](https://travis-ci.org/jasmine/jasmine) | ||
[![Build Status](https://travis-ci.com/jasmine/jasmine.svg?branch=main)](https://travis-ci.com/jasmine/jasmine) | ||
[![Open Source Helpers](https://www.codetriage.com/jasmine/jasmine/badges/users.svg)](https://www.codetriage.com/jasmine/jasmine) | ||
@@ -45,8 +45,8 @@ [![FOSSA Status](https://app.fossa.io/api/projects/git%2Bgithub.com%2Fjasmine%2Fjasmine.svg?type=shield)](https://app.fossa.io/projects/git%2Bgithub.com%2Fjasmine%2Fjasmine?ref=badge_shield) | ||
```html | ||
<link rel="shortcut icon" type="image/png" href="jasmine/lib/jasmine-{#.#.#}/jasmine_favicon.png"> | ||
<link rel="stylesheet" type="text/css" href="jasmine/lib/jasmine-{#.#.#}/jasmine.css"> | ||
<link rel="shortcut icon" type="image/png" href="lib/jasmine-{#.#.#}/jasmine_favicon.png"> | ||
<link rel="stylesheet" type="text/css" href="lib/jasmine-{#.#.#}/jasmine.css"> | ||
<script type="text/javascript" src="jasmine/lib/jasmine-{#.#.#}/jasmine.js"></script> | ||
<script type="text/javascript" src="jasmine/lib/jasmine-{#.#.#}/jasmine-html.js"></script> | ||
<script type="text/javascript" src="jasmine/lib/jasmine-{#.#.#}/boot.js"></script> | ||
<script type="text/javascript" src="lib/jasmine-{#.#.#}/jasmine.js"></script> | ||
<script type="text/javascript" src="lib/jasmine-{#.#.#}/jasmine-html.js"></script> | ||
<script type="text/javascript" src="lib/jasmine-{#.#.#}/boot.js"></script> | ||
``` | ||
@@ -60,3 +60,3 @@ | ||
|-------------------|--------------------| | ||
| Node | 8, 10, 12 | | ||
| Node | 10, 12, 14 | | ||
| Safari | 8-13 | | ||
@@ -63,0 +63,0 @@ | Chrome | Evergreen | |
@@ -32,5 +32,11 @@ # How to work on a Jasmine Release | ||
1. Update the release notes in `release_notes` - use the Anchorman gem to generate the markdown file and edit accordingly | ||
1. Update the version in `package.json` to a release candidate | ||
1. Update any links or top-level landing page for the Github Pages | ||
1. Update the version in `package.json` | ||
1. Copy version to the Ruby gem with `grunt build:copyVersionToGem` | ||
### Commit and push core changes | ||
1. Commit release notes and version changes (jasmine.js, version.rb, package.json) | ||
1. Push | ||
1. Wait for Travis to go green | ||
### Build standalone distribution | ||
@@ -40,4 +46,9 @@ | ||
### Release the Python egg | ||
### Release the core Ruby gem | ||
1. __NOTE__: You will likely need to push a new jasmine gem with a dependent version right after this release. See below. | ||
1. `rake release` - tags the repo with the version, builds the `jasmine-core` gem, pushes the gem to Rubygems.org. In order to release you will have to ensure you have rubygems creds locally. | ||
### Release the core Python egg | ||
Install [twine](https://github.com/pypa/twine) | ||
@@ -48,12 +59,4 @@ | ||
### Release the Ruby gem | ||
### Release the core NPM module | ||
1. Copy version to the Ruby gem with `grunt build:copyVersionToGem` | ||
1. __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. | ||
1. __NOTE__: You will likely need to push a new jasmine gem with a dependent version right after this release. | ||
1. Push these changes to GitHub and verify that this SHA is green | ||
1. `rake release` - tags the repo with the version, builds the `jasmine-core` gem, pushes the gem to Rubygems.org. In order to release you will have to ensure you have rubygems creds locally. | ||
### Release the NPM | ||
1. `npm adduser` to save your credentials locally | ||
@@ -66,13 +69,33 @@ 1. `npm publish .` to publish what's in `package.json` | ||
1. `cp -R edge ${version}` to copy the current edge docs to the new version | ||
1. Add a link to the new version in `index.html` | ||
1. `rake update_edge_jasmine` | ||
1. `npm run jsdoc` | ||
1. `rake release[${version}]` to copy the current edge docs to the new version | ||
1. Commit and push. | ||
### Finally | ||
### Release the binding libraries | ||
1. Visit the [Releases page for Jasmine](https://github.com/jasmine/jasmine/releases), find the tag just pushed. | ||
1. Paste in a link to the correct release notes for this release. The link should reference the blob and tag correctly, and the markdown file for the notes. | ||
1. If it is a pre-release, mark it as such. | ||
1. Attach the standalone zipfile | ||
#### NPM | ||
1. Create release notes using Anchorman as above | ||
1. In `package.json`, update both the package version and the jasmine-core dependency version | ||
1. Commit and push. | ||
1. Wait for Travis to go green again. | ||
1. `grunt release ` | ||
1. `npm publish .` | ||
There should be a post to Pivotal Labs blog and a tweet to that link. | ||
#### Gem | ||
1. Create release notes using Anchorman as above | ||
1. Update the version number in `lib/jasmine/version.rb`. | ||
1. Update the jasmine-core dependency version in `jasmine.gemspec`. | ||
1. Commit and push. | ||
1. Wait for Travis to go green again. | ||
1. `rake release` | ||
### Finally | ||
For each of the above GitHub repos: | ||
1. Visit the releases page and find the tag just published. | ||
1. Paste in a link to the correct release notes for this release. The link should reference the blob and tag correctly, and the markdown file for the notes. | ||
1. If it is a pre-release, mark it as such. | ||
1. For core, attach the standalone zipfile. |
Sorry, the diff of this file is too big to display
New author
Supply chain riskA new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.
Found 1 instance in 1 package
379616
9882
0
32