chore: update build files and add changelog

Only publish rc if last commit was not part of a release

.travis.yml

@@ -147,7 +147,8 @@ jobs:
         - git fetch --unshallow
         - echo "//registry.npmjs.org/:_authToken=\${NPM_TOKEN}" > .npmrc
         - echo "$DOCKER_PASSWORD" | docker login -u "$DOCKER_USERNAME" --password-stdin
-        - npm run release:rc -- --yes
+        # only run if the last commit was not part of a release
+        - if [[ ! `git log -n 1 -q` =~ publish|housekeeping ]]; then npm run release:rc -- --yes ; fi
 
     - stage: test-external
       # only run on changes to master

CHANGELOG.md

@@ -0,0 +1,12 @@
+# Change Log
+
+Please see the individual package changelogs for what's new:
+
+* [`/packages/interface-ipfs-core/CHANGELOG.md`](./packages/interface-ipfs-core/CHANGELOG.md)
+* [`/packages/ipfs/CHANGELOG.md`](./packages/ipfs/CHANGELOG.md)
+* [`/packages/ipfs-core-utils/CHANGELOG.md`](./packages/ipfs-core-utils/CHANGELOG.md)
+* [`/packages/ipfs-http-client/CHANGELOG.md`](./packages/ipfs-http-client/CHANGELOG.md)
+* [`/packages/ipfs-message-port-client/CHANGELOG.md`](./packages/ipfs-http-client/CHANGELOG.md)
+* [`/packages/ipfs-message-port-client/CHANGELOG.md`](./packages/ipfs-message-port-client/CHANGELOG.md)
+* [`/packages/ipfs-message-port-protocol/CHANGELOG.md`](./packages/ipfs-message-port-protocol/CHANGELOG.md)
+* [`/packages/ipfs-message-port-server/CHANGELOG.md`](./packages/ipfs-message-port-server/CHANGELOG.md)

README.md

@@ -55,10 +55,14 @@ We've come a long way, but this project is still in Alpha, lots of development i
 
 This project is broken into several modules, their purposes are:
 
-* [`/packages/ipfs`](./packages/ipfs) The core implementation
-* [`/packages/ipfs-http-client`](./packages/ipfs-http-client) A client for the RPC-over-HTTP API presented by both js-ipfs and go-ipfs
 * [`/packages/interface-ipfs-core`](./packages/interface-ipfs-core) Tests to ensure adherence of an implementation to the spec
+* [`/packages/ipfs`](./packages/ipfs) The core implementation
 * [`/packages/ipfs-core-utils`](./packages/ipfs-core-utils) Helpers and utilities common to core and the HTTP RPC API client
+* [`/packages/ipfs-http-client`](./packages/ipfs-http-client) A client for the RPC-over-HTTP API presented by both js-ipfs and go-ipfs
+* [`/packages/ipfs-message-port-client`](./packages/ipfs-http-client) A client for the RPC-over-HTTP API presented by both js-ipfs and go-ipfs
+* [`/packages/ipfs-message-port-client`](./packages/ipfs-message-port-client) A client for the RPC-over-message-port API presented by js-ipfs running in a shared worker
+* [`/packages/ipfs-message-port-protocol`](./packages/ipfs-message-port-protocol) Code shared by the message port client & server
+* [`/packages/ipfs-message-port-server`](./packages/ipfs-message-port-server) The server that receives requests from ipfs-message-port-client
 
 ## Want to hack on IPFS?
 

package.json

@@ -40,7 +40,7 @@
     "docker:release:push-version": "docker push ipfs/js-ipfs:v`npm show ipfs@latest version -q`",
     "release:post:remove-hoisted-modules": "json -I -f ./lerna.json -e \"delete this.command.bootstrap.nohoist\"",
     "release:post:remove-examples": "json -I -f ./lerna.json -e \"this.packages = this.packages.filter(p => !p.includes('examples'))\"",
-    "release:pre:revert-files": "git add lerna.json && git commit -m 'chore: post-release housekeeping'",
+    "release:post:revert-files": "git add lerna.json && git commit -m 'chore: post-release housekeeping'",
     "release:rc": "run-s release:pre:* release:canary docker:rc release:post:*",
     "release:canary": "lerna publish --canary --preid rc --dist-tag next",
     "docker:rc": "run-s run docker:rc:*",

packages/ipfs-http-client/README.md

@@ -391,6 +391,7 @@ The js-ipfs-http-client is a work in progress. As such, there's a few things you
 
 This module started as a direct mapping from the go-ipfs cli to a JavaScript implementation, although this was useful and familiar to a lot of developers that were coming to IPFS for the first time, it also created some confusion on how to operate the core of IPFS and have access to the full capacity of the protocol. After much consideration, we decided to create `interface-ipfs-core` with the goal of standardizing the interface of a core implementation of IPFS, and keep the utility functions the IPFS community learned to use and love, such as reading files from disk and storing them directly to IPFS.
 
+
 ## License
 
 [MIT](LICENSE)