Permalink
Commits on Aug 4, 2017
  1. Build with Node.js 8 on Travis CI.

    bigeasy committed Aug 4, 2017
  2. Upgrade `proof` to 3.0.x.

    bigeasy committed Aug 4, 2017
  3. Do not build with Node.js 7 on Travis CI.

    bigeasy committed Aug 4, 2017
Commits on Mar 2, 2017
  1. Do build with Node.js 7 on Travis CI.

    bigeasy committed Mar 2, 2017
  2. Do not build with Node.js 5 on Travis CI.

    bigeasy committed Mar 2, 2017
Commits on Feb 28, 2017
  1. Add Wiseguy to `.gitignore`.

    bigeasy committed Feb 28, 2017
  2. Add Wiseguy to `.gitignore`.

    bigeasy committed Feb 28, 2017
  3. Plain text `README`.

    bigeasy committed Feb 28, 2017
  4. Update `LICENSE` for 2017.

    bigeasy committed Feb 28, 2017
Commits on Oct 1, 2016
  1. Upgrade Proof to 1.2.x.

    bigeasy committed Oct 1, 2016
Commits on Sep 17, 2016
  1. Upgrade to Proof Redux.

    bigeasy committed Sep 17, 2016
Commits on Aug 10, 2016
  1. Build with latest Node.js 6 on Travis CI.

    bigeasy committed Aug 10, 2016
  2. Pin dependencies to minor version.

    bigeasy committed Aug 10, 2016
Commits on Aug 7, 2016
  1. Tidy `package.json`.

    bigeasy committed Aug 7, 2016
  2. Remove test sub-directory.

    bigeasy committed Aug 7, 2016
  3. Indent `package.json`.

    bigeasy committed Aug 7, 2016
Commits on Feb 2, 2016
  1. Release 1.0.0.

    bigeasy committed Feb 2, 2016
    Closes #57.
Commits on Feb 1, 2016
  1. Tidy `.travis.yml`.

    bigeasy committed Feb 1, 2016
  2. Update `LICENSE` for 2016.

    bigeasy committed Feb 1, 2016
  3. Tidy `package.json`.

    bigeasy committed Feb 1, 2016
  4. Upgrade Cadence to 1.x.

    bigeasy committed Feb 1, 2016
  5. Upgrade Advance to 1.x.

    bigeasy committed Feb 1, 2016
  6. Upgrade Proof to 1.x.

    bigeasy committed Feb 1, 2016
Commits on Nov 28, 2015
  1. Build on Travis without shipping to web server.

    bigeasy committed Nov 28, 2015
    No longer shipping artifiacts to my own personal web server. Instead I'm
    simply reporting the coverage to the command line. All I need to do is
    indicate whether or not it is at 100%. I'm not going to want to go back
    and audit it line by line.
    
    Why do I need this when I'm submitting to Coveralls? Because Coveralls
    only tracks line coverage, not branch coverage.
Commits on Nov 17, 2015
  1. Release 0.0.14.

    bigeasy committed Nov 17, 2015
    Closes #56.
  2. Upgrade Advance to 0.0.16.

    bigeasy committed Nov 17, 2015
  3. Upgrade Cadence to 0.4.1.

    bigeasy committed Nov 17, 2015
  4. Upgrade Proof to 0.0.56.

    bigeasy committed Nov 17, 2015
  5. Upgrade Proof to 0.0.56.

    bigeasy committed Nov 17, 2015
  6. Remove `release.ft`.

    bigeasy committed Nov 17, 2015