Skip to content

Versioning of packages doesn't follow the semantic versioning specification #166

@gkarat

Description

@gkarat

Hello, I recently worked with one of the API client - @redhat-cloud-services/host-inventory-client and the Inventory application (which is a consumer of this client). While I was upgrading the client dependency version from 1.0.96 to 1.0.109, I found out that the application has got broken. Debugging the problem, I realized that the HostsApi's apiHostGetHostList function parameters were modified (specifically, the order has changed, and the wrong parameters were sent by the consumer app).

I managed to fix this and this is OK to have client interface changes, however, I would love to see such breaking changes documented and reflected with the help of versioning of the package. Just incrementing the patch version is not correct, because I would expect the increment of the major version if a broken change introduced to the interface.

Just for evidence and illustration, this is the commit that changed the function parameters: b9b6839#diff-a9f2cff91e34cf8e2a01709fba111c82cc0e22f1f5f3782607c7f789beb189aeR1907.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions