Releases: sprain/php-swiss-qr-bill
v4.5
- Added stricter css rules to
HtmlOutput
to make sure qr bill designs are not overwritten by other styles within the document (#201)
Good to know
- While this could be considered to be just a bugfix, a new minor version is released based on library policy because it is a visible change of the payment part for some invoice setups.
v4.4
- Re-introduced output of country code for Liechtenstein on payment parts, as expected by the specifications (see #199)
Good to know
- While this could be considered to be just a bugfix, a new minor version is released based on library policy because it is a visible change of the payment part for some invoice setups.
Kudos!
- Thanks to @markus-ksg for noticing this issue and describing the needed fix.
v4.3
- Added functionality to handle long addresses on the receipt of the payment part by omitting some address lines when needed (#190)
Kudos!
- Thanks to @merlincom for reporting the issue and to @kohlerdominik for providing feedback in the decision process.
v4.2
- Fixed ISO 3661-1 country code for Liechtenstein (#189)
Good to know
- While this could be considered to be just a bugfix, a new minor version is released based on library policy because it is a visible change of the payment part for some invoice setups.
Kudos!
- Thanks to @auerswald for noticing this bug and providing the fix for it!
v4.1.1
v4.1
v4.0
While there are BC breaks, no changes are required if the library was used as intended.
- Added support for
endroid/qr-code
v4 (#151) - Dropped support for
endroid/qr-code
v3 (#151) Sprain\SwissQrBill\QrCode\QrCode
no longer extendsEndroid\QrCode\QrCode
(#151)
Kudos!
- Thanks a lot to @dominikschnieper for your help in fixing a blocking issue for this release, and to @endroid for always being very flexible and quick when it comes to merging pull requests for bugfixes.
v3.3
- Added support for PHP 8.1 (#159)
- Dropped support for PHP 7.4 (#157)
- Added support for Symfony 6 dependencies (#157)
- Dropped support for Symfony 3 dependencies (#157)
Kudos!
- Thanks to @kohlerdominik for preparing the PHP 8.1 compatibility and for providing feedback on those changes.
Good to know
-
Isn't dropping support for a PHP version a BC break and should cause a major version update?
No. Why not? The Doctrine project explains it nicely:A BC break happens when there is an incompatible change that your package manager can't handle. For example, changing a method signature in a minor version is a no-go, since the composer version constraints mentioned above assume any minor upgrade can safely be used. However, when we drop support for an older version of PHP, composer will not consider the new version if the PHP version requirement is no longer fulfilled. Thus, you won't end up with a fatal error due to a wrong method signature, you just won't get the new version.
v3.2
- Adjusted behaviour of field
StrdBkgInf
to match specifications v2.2 (#146)
Good to know
- While this could be considered to be just a bugfix, a new minor version is released based on library policy because it is a visible change of the qr code for some invoice setups.