Skip to content

Releases: Roave/BackwardCompatibilityCheck

4.0.0

17 Jul 17:44
4.0.0
4d3cac1
Compare
Choose a tag to compare

Build Status

This release excludes @internal marked symbols from BC checks.

Dependencies have been updated, and testing/static-analysis have been hugely improved.

Complex types such as @var Foo<T1, T2> also no longer cause the tool to crash during inspection.

Total issues resolved: 20

3.0.0

23 Apr 12:50
3.0.0
3af8bc4
Compare
Choose a tag to compare

2.1.0

11 Feb 14:26
2.1.0
aefb49b
Compare
Choose a tag to compare

Build Status

This release fixes an issue with pre-releases (alpha/beta/rc) being considered for
stability checks, and introduces documentation for the github actions provided by @Nyholm.

Total issues resolved: 4

2.0.0

23 Aug 21:17
2.0.0
347c99d
Compare
Choose a tag to compare

Build Status

This new major release due to some backwards-incompatible changes
in some signatures and parameters of the CLI tooling. This release:

  • introduces auto-discovery of source directory based on your project's composer.json
  • removes the sources-path CLI argument
  • changes the constructor signature of Roave\BackwardCompatibility\Command\AssertBackwardsCompatible
  • deprecates Roave\BackwardCompatibility\Factory\DirectoryReflectorFactory

This is the full list of statically detected BC breaks:

[BC] CHANGED: The parameter $reflectorFactory of Roave\BackwardCompatibility\Command\AssertBackwardsCompatible#__construct() changed from Roave\BackwardCompatibility\Factory\DirectoryReflectorFactory to a non-contravariant Roave\BackwardCompatibility\Factory\ComposerInstallationReflectorFactory

Total issues resolved: 2

1.1.1

22 Aug 06:19
1.1.1
85028e0
Compare
Choose a tag to compare

Build Status

This release fixes an issue in which removed classes were not detected as such, but rather detected as
classes that were changed to interfaces due to internall fallback symbol stubbing mechanisms.

Total issues resolved: 3

1.1.0

21 Aug 11:14
1.1.0
34f627b
Compare
Choose a tag to compare

Build Status

This release improves the reliability of the library by marking crashes as "SKIPPED"
BC checks. Skipped checks still count as backwards-incompatible changes for now, so
the tool will exit with a non-zero status code in case a crash occurred.

Starting from this release, a PHAR distribution of the package will be available for
each new release under https://github.com/Roave/BackwardCompatibilityCheck/releases.

We also improved the autoloading of the library, with the clear pre-condition that it
must either be installed via composer require or as an application via composer create-project
or git clone + `composer install.

The test automation has also been hardened by introducing both PSALM
and PHPStan static analysis checks.

Total issues resolved: 9

1.0.3

04 Jun 16:09
1.0.3
95b5c0d
Compare
Choose a tag to compare

This release fixes a few mistakes in the handling of --from. Specifically:

  • omitting --from will now lead to --from to default to the lowest latest minor release
  • specifying --from is now permitted again (bug introduced in 1.0.2)

Total issues resolved: 1

1.0.2

27 May 15:01
1.0.2
9e95a60
Compare
Choose a tag to compare

This release fixes the omission of the --from flag in the CLI interface,
which was defaulting to the incorrect '' (empty string).

Also, classes that were previously not found are now stubbed out as
interfaces without inheritance nor methods, which allows scanning for
BC breaks in packages with optional dependencies.

Total issues resolved: 5

1.0.1

27 May 11:17
1.0.1
81b816e
Compare
Choose a tag to compare

This release fixes an autoloading issue when the project is required as a
composer dependency rather than being installed standalone.

Total issues resolved: 3

1.0.0

26 May 14:44
1.0.0
Compare
Choose a tag to compare

This is the first public release of roave/backward-compatibility-check.

From this release on, this library follows strict semantic versioning, with
each release that introduces a new backwards compatibility break (BC)
being a new major version.

Total issues resolved: 40