Skip to content

Please respect semantic versioning to prevent unexpected breakage #160

@vazaha-nl

Description

@vazaha-nl

I did a composer update from version v1.21.4 to v1.22.2 and this upgrade broke my code because of breaking public api changes (modified function signature) in src/Invoice.php. Please do not do that. In minor version upgrades, there should be no breaking changes.

Looking at the changelog for version 2, I even see breaking changes in a patch update: https://github.com/num-num/ubl-invoice/releases/tag/v2.0.1. That is even worse.

From https://semver.org/:

Given a version number MAJOR.MINOR.PATCH, increment the:

    MAJOR version when you make incompatible API changes
    MINOR version when you add functionality in a backward compatible manner
    PATCH version when you make backward compatible bug fixes

I like this library and I am grateful for your work. But for my own (and my client's) peace of mind, I will be pinning this library to the previous version and will not upgrade it anymore, I cannot risk any more unexpected breakage.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions