Browse files

Update README, version

  • Loading branch information...
1 parent 3f76fd7 commit f67f6e705c9483c20bb261322e0b88ced229befe @gotwarlost committed Dec 9, 2012
Showing with 2 additions and 1 deletion.
  1. +1 −0
  2. +1 −1 package.json
@@ -153,6 +153,7 @@ Changelog
+<tr><td>v0.1.24</td><td>Add lcov summaries. Fixes issue #20</td></tr>

csnover Dec 19, 2012

Could you maybe create git tags when you release a new version? That would be really useful. Thanks!


gotwarlost Dec 19, 2012


Is the use-case to be able to easily clone the source for a specific version? Making sure I understand what you are asking for.

<tr><td>v0.1.23</td><td>Add ability to save a baseline coverage file for the instrument command. Fixes issue #19</td></tr>
<tr><td>v0.1.22</td><td>Add signature attribute to cobertura method tags to fix NPE by the Hudson publisher</td></tr>
<tr><td>v0.1.21</td><td>Add cobertura XML report format; exprimental for now</td></tr>
@@ -1,6 +1,6 @@
"name": "istanbul",
- "version": "0.1.23",
+ "version": "0.1.24",
"description": "Yet another JS code coverage tool that computes statement, line, function and branch coverage with module loader hooks to transparently add coverage when running tests. Supports all JS coverage use cases including unit tests, server side functional tests and browser tests. Built for scale",
"keywords": [ "coverage", "code coverage", "JS code coverage", "JS coverage" ],
"author": "Krishnan Anantheswaran <>",

0 comments on commit f67f6e7

Please sign in to comment.