Skip to content

Commit

Permalink
chore: update buildgoggles dep for node 12 and update version for rel…
Browse files Browse the repository at this point in the history
…ease (#5)

* chore: update buildgoggles dep for node 12 and update version for release

* chore(release): 1.6.4

* chore: forgot to add node 12 commit for ci

* chore: add the package-lock.json file

* fix: broken tests due to error differences on node 8 vs node 12
  • Loading branch information
owenniblock committed Jun 10, 2020
1 parent a90b340 commit d4f1211
Show file tree
Hide file tree
Showing 6 changed files with 5,426 additions and 5 deletions.
1 change: 0 additions & 1 deletion .gitignore
Original file line number Diff line number Diff line change
@@ -1,6 +1,5 @@
coverage/
node_modules/
.nyc_output/
package-lock.json
.buildinfo.json
soec/.buildinfo.json
2 changes: 1 addition & 1 deletion .travis.yml
Original file line number Diff line number Diff line change
Expand Up @@ -7,5 +7,5 @@ script:
- nyc npm test && nyc report --reporter=text-lcov | coveralls

node_js:
- "6"
- "8"
- "12"
10 changes: 10 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,16 @@

All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.

<a name="1.6.4"></a>
## [1.6.4](https://github.com/npm-wharf/shipwright/compare/v1.6.2...v1.6.4) (2020-06-10)


### Bug Fixes

* render whale character correctly in javascript -- needs a code point escape for hex unicode numbers ([c522dd7](https://github.com/npm-wharf/shipwright/commit/c522dd7)), closes [/dmitripavlutin.com/what-every-javascript-developer-should-know-about-unicode/#3](https://github.com//dmitripavlutin.com/what-every-javascript-developer-should-know-about-unicode//issues/3)



<a name="1.6.3"></a>
## [1.6.3](https://github.com/npm-wharf/shipwright/compare/v1.6.2...v1.6.3) (2019-11-18)

Expand Down
Loading

0 comments on commit d4f1211

Please sign in to comment.