sprain/swiss-qr-bill

• Fixed an issue where qr bills with amounts equal to or larger than CHF/EUR 1000 invalidly contained a space as a thousands separator within the qr code (#292) – thanks to @macadamiaz for reporting.

• Got rid of deprecation notice by avoiding implicit nullable parameter (#269) – thanks to @finpension-aless

• Added official Romansh translations (#293) – thanks to @gion-andri

⚠️ Warning: This version creates invalid QR codes for amounts >= CHF/EUR 1000. Use v5.2.1 or higher instead.

• Added support for Symfony v8 dependencies (#291)
• Dropped support for Symfony v4 and v5 dependencies (#285) – thanks to @JohnyRicio

⚠️ Warning: This version creates invalid QR codes for amounts >= CHF/EUR 1000. Use v5.2.1 or higher instead.

• Added support for PHP 8.5 (e2ad167)

• This release removes deprecated methods and functionality. Most importantly, the CombinedAddress is no longer available. With v2.3 of the qr bill specification, since November 2025, only the StructuredAddress is allowed. (#288)
• Also based on v2.3 of the qr bill specification, a wider set of characters is now allowed in qr bill contents. (#280)

• Added export-ignore rules in .gitattributes to reduce file size of package download (#281) – thanks to @iquito

• Improved scissors symbol in TcPdfOutput (#268) – thanks to @tafel
• Added validation to make sure the QrPaymentReference does not consist exclusively of zeros (#279)
• Updated test suite to use PhpUnit 10 (#271) – thanks to @kohlerdominik

• Deprecated CombinedAddress as it will no longer be supported by v2.3 of the QR bill specification, valid from 21. November 2025 (#278)
• More minor deprecations (bf317d5)

• Dropped support for PHP 8.0 (#265)
• Added support for PHP 8.4 (#265)

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.