Releases: ipfs/pinning-services-api-spec
Releases · ipfs/pinning-services-api-spec
v1.0.0
This release includes only documentation improvements.
There is no functional change, nor need to re-generate any code.
- chore: v1.0.0
- this is a formal version bump to signify that a client for this API shipped with go-ipfs 0.8.0
- going forward this API spec will follow https://semver.org
- we don't expect to make any breaking changes, as the stability of
pin remotecommands in go-ipfs is our priority
- docs: readme (d3ecd73)
- docs: clarify use of provider hints (#72)
- docs: code generation (#67)
v0.1.2
v0.1.1
3847396
This commit was signed with the committer’s verified signature.
The key has expired.
lidel
Marcin Rataj
- style: rename object returned with error (#65)
- this does not change structures sent over the wire, only renames
Errorresponse scheme toFailure, which means that code generated with openapi-generator have better ergonomics
- this does not change structures sent over the wire, only renames
- chore: updated version to v0.1.1
v0.1.0
46f23fd
This commit was signed with the committer’s verified signature.
The key has expired.
lidel
Marcin Rataj
This release includes improved documentation, new error responses and one field name change.
The 📣 indicates BREAKING CHANGES which require client/server regeneration for interop to work.
Changes since last release:
- 📣 feat: improved error responses (#59)
- 📣 refactor: rename PinStatus id → requestid (#63)
- fix: adjust cid filter limits (#62)
- improved documentation
👉 FYSA v1.0.0 will be tagged when go-ipfs 0.8.x ships with a built-in client for this API.
We are committed to no breaking changes from that point.
Latest docs: https://ipfs.github.io/pinning-services-api-spec/