-
Notifications
You must be signed in to change notification settings - Fork 298
Add a changelog #143
Comments
I think the most important thing is clear commit messages, also I see there is a little amount of commits between releases, so I don't think generating a changelog is very useful |
I've encountered a necessity of a changelog. Today I am not sure why version 4.0.0 is a major version (in other words, what are the backwards-incompatible changes in it). |
It were changes on the Object API that now follows the spec defined on https://github.com/ipfs/interface-ipfs-core#object, you should be able to use almost as you were using, with the different that you now have to call on the return object (the dagNode), .toJSON() to get a JSON format of the results (which will bring more info than sometimes just the Hash) Agree on having a changelog 👍 |
I've encountered a necessity of a changelog. Once again. This time it took the form of |
Apologies @Mithgol, didn't want to cause any pain migrating. We created a (probably too small) entry on https://github.com/ipfs/js-ipfs-api/releases/tag/v5.0.0. However, I'm surprised that What version are you running? |
We will be doing this together with ipfs/aegir#30 |
In addition to the (soon to be) changelog, we now have: And are working towards making this experience less painful on: https://github.com/ipfs/http-api-spec/issues/116 |
We have changelogs now :D https://github.com/ipfs/js-ipfs-api/releases \o/ |
Excellent. Thanks. |
We should add a changelog (and auto generated if possible on releases, though this depends on us having a decent commit message convention and enforcing it)
https://github.com/ajoslin/conventional-changelog
Discuss :)
The text was updated successfully, but these errors were encountered: