Skip to content

Breaking changes should not be introduced in minor releases #120

@itkfm

Description

@itkfm

Describe the bug
Breaking changes like 86f28b6 should not occur in minor releases.
This breaks code without any notice!

In case one would release a new major version (as required semantic versioning), there wouldn’t be any problem.
Composer won’t install an incompatible version, when you specify a suitable version selector (e.g. ^2.2 -> any v2 that’s at least v2.2.0)

Code to Reproduce

"webklex/php-imap": "^2.2"
rm composer.lock
composer install

-> boom!, here you go…

Expected behavior
Do not BREAK code in minor updates.

Desktop / Server (please complete the following information):

  • OS: any
  • PHP: any
  • Version ^2.2

Additional context
https://semver.org/

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions