0.11.0
This version solves a few problems with the superseding schema feature. Also, it disallows non-sequential versions.
The changes on superseding schema feature
Recently, we've added the superseding schema feature to Iglu Server. More information about it can be found here.
However, we've realized that superseding version information can't be propagated from one server to another such as dev server to prod server because Iglu Server only returns $supersededBy field. Therefore, starting with this version, Iglu Server returns $supersedes field as well. $supersedes field's value will be the exact value given to the schema during upload. With this way, if multiple sequential schemas are transferred from one Iglu Server to another, superseding version information will be transferred exactly as well. Keep in mind that this change requires a new field in the iglu_schemas table. However, it will be added automatically. You don't have to do anything manually. More information about this change can be found in this issue.
Also, in this version, we've fixed a bug that causes to update the superseding version information of different vendors/names if their superseding schema versions are same.
Disallow non-sequential versions
Starting with this version, schemas with a non-sequential version won't be allowed. As an example, if iglu server already holds versions 1-0-0 and 1-1-0 of a schema, then it will reject an attempt to publish schema version 1-0-1.