From 2dd28c7035a06b358acbf4c9c3450c700934f89a Mon Sep 17 00:00:00 2001
From: Piotr Lewandowski
Date: Wed, 2 Sep 2026 08:07:03 +0200
Subject: [PATCH] chore: relicense under MIT and prepare the 1.0.0 release
Relicensed from EUPL-1.2 to MIT. Integrating this plugin means subclassing its
models and applying its ProductTrait to your own Product, which made the EUPL's
reciprocity terms a real question for a commercial shop - a question the plugin
has no reason to ask. The LICENSE file also now carries the copyright notice it
previously lacked. Every commit in this repository is by the sole copyright
holder, so there is no third-party consent to gather.
Release preparation:
- CHANGELOG: the accumulated [Unreleased] entries become [1.0.0], restructured
into single Changed/Added/Fixed sections rather than the two half-merged sets
the readiness work left behind. Link reference definitions added, so the
version headings stop rendering as literal brackets.
- README: the release-candidate banner becomes a stable-release one, and the
install line drops the @RC stability flag.
- composer.json: package homepage and a support block (issues, source, docs),
which Packagist otherwise has to guess at, plus two more keywords.
The upgrade note in the changelog is the one thing worth reading before tagging:
anyone already running an RC has DoctrineMigrations\Version20260807090000
recorded in sylius_migrations, and the migration is now namespaced
Madcoders\SyliusBrandPlugin\Migrations. They must rename the recorded version
rather than let the migration re-run, which would fail on CREATE TABLE.
Verified on PHP 8.4 against MySQL 8.4: composer validate --strict, PHPStan
(level max), ECS, Rector, 48 unit tests, 17 non-unit tests, 26 Behat scenarios.
---
CHANGELOG.md | 150 ++++++++++++------------
LICENSE | 308 ++++----------------------------------------------
README.md | 11 +-
composer.json | 12 +-
4 files changed, 116 insertions(+), 365 deletions(-)
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 30e22fa..2bebc1a 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -7,31 +7,25 @@ adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
## [Unreleased]
-### Added
+## [1.0.0] - 2026-09-02
-- **The brand logo is shown next to the brand name on product tiles as well as on the product
- page.** The product-page badge already carried it; product tiles were deliberately text-only, on
- the argument that a second image competes with the product photo. At 20px it does not - it reads
- as a mark beside the name - so the tile hook now sets `show_logo: true`. A brand with no logo
- still renders as its name alone, so a catalogue with mixed data stays tidy.
-- The logo is sizeable from hook configuration: `logo_height` (default 32), `logo_width` (default
- 96) and `logo_filter` (default `madcoders_sylius_brand_logo_thumbnail`). The plugin's own tile
- hook uses 20 by 60.
-- Brand fixtures can carry a logo. `BrandExampleFactory` accepts an `image` option - an absolute
- path or `@Bundle/...` notation - and uploads it through Sylius' image uploader. The upload is
- explicit because a fixture persists through the object manager, so the plugin's image-upload
- listener never fires for it. Three of the five demo brands now ship a logo and two do not, which
- is what a real catalogue looks like.
-- Compile-time configuration, where there was none: `madcoders_sylius_brand.products_per_page`
- (default 12) and `homepage_brands_limit` (default 12). Page sizes are a decision about the theme
- rather than about the shop, so they belong here rather than in the admin settings - and the brand
- page size was previously a private constant on a `final` controller, unreachable without
- replacing the service. Both are validated at container build time.
-- `BrandRepositoryInterface::findDisplayedOnByIds()`, the bounded counterpart to
- `findAllDisplayedOn()`.
+First stable release. The API - service ids, settings paths, table names and configuration keys -
+is frozen for the 1.x line.
+
+Everything here is the delta from 1.0.0-RC.2: a licence change, and the outcome of a production
+readiness review of the whole plugin.
### Changed
+- **The plugin is now MIT licensed**, replacing EUPL-1.2. Integrating the plugin means subclassing
+ its models and applying its `ProductTrait` to your own `Product`, which made the copyleft terms a
+ real question for commercial shops. MIT removes the question. The licence text now also carries
+ the copyright notice it previously lacked.
+- **The brand logo is shown next to the brand name on product tiles, as well as on the product
+ page.** The product-page badge already carried it; tiles were deliberately text-only, on the
+ argument that a second image competes with the product photo. At 20px it does not - it reads as a
+ mark beside the name. A brand with no logo still renders as its name alone, so a catalogue with
+ mixed data stays tidy.
- **The demo brand fixtures are no longer added to Sylius' `default` suite.** They live in their own
`madcoders_brand` suite, and `config/fixtures.yaml` is no longer imported by the plugin's
`config.yaml`. Importing the plugin means asking for the brand feature, not for five brands the
@@ -46,23 +40,45 @@ adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
- `Configuration.php` is analysed by PHPStan again; the `excludePaths` entry that skipped it is
gone, so the plugin's configuration contract is covered at `level: max`.
-### Fixed
-
-- `madcoders:brand:resync-products` no longer lazy-loads attribute values one product at a time. Each
- page is now two bounded queries - the ids, then those products with their attribute values
- fetch-joined - instead of one query per row. The join has to be a second query because a `LIMIT`
- applies to SQL rows, so a fetch-joined to-many association cannot be paged directly.
-- The same command pages by keyset (`id > :lastId`) rather than by offset. `setFirstResult()` makes
- the database walk and discard every row before the window, so a full pass over a large catalogue
- was quadratic.
-- The migration guards the column it adds to `sylius_product`. A shop that already carries a
- `brand_id` - hand-rolled, or from another brand plugin - would previously abort the whole
- migration with `ColumnAlreadyExists` and take the three brand tables down with it. `down()` mirrors
- the guard, so it never drops a column this plugin did not add. The product table name is a named
- constant rather than three inline literals.
+### Added
-Production-readiness fixes ahead of 1.0.0. The migration namespace change is the reason this has to
-land before the stable tag rather than after it.
+- Compile-time configuration, where there was none: `madcoders_sylius_brand.products_per_page`
+ (default 12) and `homepage_brands_limit` (default 12). Page sizes are a decision about the theme
+ rather than about the shop, so they belong here rather than in the admin settings - and the brand
+ page size was previously a private constant on a `final` controller, unreachable without replacing
+ the service. Both are validated at container build time.
+- The logo is sizeable from hook configuration: `logo_height` (default 32), `logo_width` (default
+ 96) and `logo_filter` (default `madcoders_sylius_brand_logo_thumbnail`). The plugin's own tile
+ hook uses 20 by 60.
+- Brand fixtures can carry a logo. `BrandExampleFactory` accepts an `image` option - an absolute
+ path or `@Bundle/...` notation - and uploads it through Sylius' image uploader. The upload is
+ explicit because a fixture persists through the object manager, so the plugin's image-upload
+ listener never fires for it. Three of the five demo brands ship a logo and two do not, which is
+ what a real catalogue looks like.
+- `BrandRepositoryInterface::findDisplayedOnByIds()`, the bounded counterpart to
+ `findAllDisplayedOn()`.
+- `docs/` ships in the installed package. It was `export-ignore`d, so `composer require` produced a
+ `vendor/` copy whose only installation instruction was a dead relative link to
+ `docs/INSTALLATION.md` - no bundle registration, no routing, no mention that three entity classes
+ are mandatory. Only `docs/PLAN.md` is excluded.
+- `ResyncProductBrandsCommand` accepts an optional `LockFactory`, wired to `lock.default.factory`
+ with `on-invalid="null"`. Hosts that have configured `framework.lock` with a shared store get a
+ real distributed lock; hosts that have not keep the previous local behaviour.
+- Functional coverage for `madcoders:brand:resync-products`, which had none: exit codes, that
+ `--dry-run` really writes nothing, that a run exits without work while another holds the lock, and
+ that an invalid `--batch-size` degrades to a working run.
+- Behat coverage for brand-page pagination, asserting the status code directly. Out-of-range pages
+ are converted to 404 by `babdev/pagerfanta-bundle` (a hard Sylius dependency); the behaviour was
+ correct but rested on a transitive dependency and was untested.
+- Integration coverage for the logo: that it renders when the brand has one, that its size is
+ configurable, and that a brand without one renders its name with no `
`. Plus a unit test for
+ the configuration tree.
+- CI runs PHP 8.4 on the newest supported stack. `composer.json` declares `^8.3` and the matrix only
+ covered 8.3, so the upper half of the declared range shipped untested - and the dependency graph
+ genuinely differs there, since `doctrine/instantiator 2.1.0` requires `^8.4`.
+- CI has a `lowest` job running `composer update --prefer-lowest --prefer-stable`, so the declared
+ floors - notably `monsieurbiz/sylius-settings-plugin ^2.0`, the plugin's tightest coupling - are
+ tested facts rather than assertions.
### Fixed
@@ -72,14 +88,18 @@ land before the stable tag rather than after it.
that the stock Symfony Flex recipe uses for the application's own migrations meant one of the two
paths silently won and the other's migrations never ran - the brand tables were never created, or
the application's own migrations were skipped, with no error at migrate time. CI never saw it
- because the Sylius test application uses `App\Migrations`. **This must be applied before any
- install has run the old migration**: the version is recorded in `sylius_migrations` under its
- namespace, so an install that already ran `DoctrineMigrations\Version20260807090000` will try to
- run the renamed class again and fail on `CREATE TABLE`.
+ because the Sylius test application uses `App\Migrations`.
+ **Anyone upgrading from an RC must be aware of this**: the version is recorded in
+ `sylius_migrations` under its namespace, so an install that already ran
+ `DoctrineMigrations\Version20260807090000` will try to run the renamed class again and fail on
+ `CREATE TABLE`. Rename the recorded version rather than re-running the migration.
- `symfony/lock` is now `^6.4 || ^7.0` instead of `^6.4 || ^7.4`. The old constraint excluded
Symfony 7.0 to 7.3, and Flex pins every `symfony/*` package to the application's own Symfony
- version, so the plugin was simply uninstallable on a shop pinned to any of them. The only use is
- `LockableTrait`, which is unchanged across the whole range.
+ version, so the plugin was simply uninstallable on a shop pinned to any of them.
+- The lock guard on `madcoders:brand:resync-products` works on Symfony 6.4. `LockableTrait` only
+ accepts an injected `LockFactory` from 7.1 onwards; on 6.4 assigning its `$lockFactory` silently
+ creates a dynamic property the trait never reads, so it fell back to a host-local store. The
+ command now holds the lock itself, so behaviour is identical across the supported range.
- The documented admin routing (and the test application's) uses
`prefix: '/%sylius_admin.path_name%'` rather than a hardcoded `/admin`. A shop that renamed its
admin path - a routine hardening step - mounted the brand CRUD at `/admin`, outside
@@ -87,33 +107,18 @@ land before the stable tag rather than after it.
- Brand listings no longer select translations with a null or empty slug. The column is nullable and
non-form writes (fixtures, imports, an auto-created empty translation) can leave one behind;
`path()` throws on a null route parameter, so such a row would have 500'd a public page. The shared
- `shop/brand/_link.html.twig` partial guards the same case for hosts that render it with a brand of
- their own.
-
-### Added
-
-- `docs/` ships in the installed package. It was `export-ignore`d, so `composer require` produced a
- `vendor/` copy whose only installation instruction was a dead relative link to
- `docs/INSTALLATION.md` - no bundle registration, no routing, no mention that three entity classes
- are mandatory. Only `docs/PLAN.md` is still excluded.
-- `ResyncProductBrandsCommand` accepts an optional `LockFactory`, wired to `lock.default.factory`
- with `on-invalid="null"`. `LockableTrait` otherwise builds its own over `SemaphoreStore` /
- `FlockStore`, both host-local, so on a multi-pod deployment a cron on one node and a deploy hook on
- another each took their own lock and walked the catalogue at the same time. Hosts that have
- configured `framework.lock` with a shared store now get a real distributed lock; hosts that have
- not keep the previous local behaviour.
-- Functional coverage for `madcoders:brand:resync-products`, which had none: exit codes, that
- `--dry-run` really writes nothing, that a run exits without work while another holds the lock, and
- that an invalid `--batch-size` degrades to a working run.
-- Behat coverage for brand-page pagination, asserting the status code directly. Out-of-range pages
- are converted to 404 by `babdev/pagerfanta-bundle` (a hard Sylius dependency); the behaviour was
- correct but rested on a transitive dependency and was untested.
-- CI runs PHP 8.4 on the newest supported stack. `composer.json` declares `^8.3` and the matrix only
- covered 8.3, so the upper half of the declared range shipped untested - and the dependency graph
- genuinely differs there, since `doctrine/instantiator 2.1.0` requires `^8.4`.
-- CI has a `lowest` job running `composer update --prefer-lowest --prefer-stable`. Without it the
- declared floors - notably `monsieurbiz/sylius-settings-plugin ^2.0`, the plugin's tightest
- coupling - were assertions rather than tested facts.
+ `shop/brand/_link.html.twig` partial guards the same case.
+- `madcoders:brand:resync-products` no longer lazy-loads attribute values one product at a time.
+ Each page is two bounded queries - the ids, then those products with their attribute values
+ fetch-joined - instead of one query per row. The join has to be a second query because a `LIMIT`
+ applies to SQL rows, so a fetch-joined to-many association cannot be paged directly.
+- The same command pages by keyset (`id > :lastId`) rather than by offset. `setFirstResult()` makes
+ the database walk and discard every row before the window, so a full pass over a large catalogue
+ was quadratic.
+- The migration guards the column it adds to `sylius_product`. A shop that already carries a
+ `brand_id` - hand-rolled, or from another brand plugin - would previously abort the whole
+ migration with `ColumnAlreadyExists` and take the three brand tables down with it. `down()`
+ mirrors the guard, so it never drops a column this plugin did not add.
## [1.0.0-RC.2] - 2026-08-25
@@ -233,3 +238,8 @@ First release candidate. Verified on PHP 8.3 across Sylius ~2.0, ~2.1 and ~2.2,
A channel-scoped value is ignored.
- Turning the feature off hides brands in the shop but does not stop products resolving, so no
resync is needed when switching it back on.
+
+[Unreleased]: https://github.com/mad-coders/sylius-brand-plugin/compare/v1.0.0...1.0
+[1.0.0]: https://github.com/mad-coders/sylius-brand-plugin/compare/v1.0.0-RC.2...v1.0.0
+[1.0.0-RC.2]: https://github.com/mad-coders/sylius-brand-plugin/compare/v1.0.0-RC.1...v1.0.0-RC.2
+[1.0.0-RC.1]: https://github.com/mad-coders/sylius-brand-plugin/releases/tag/v1.0.0-RC.1
diff --git a/LICENSE b/LICENSE
index 4153cd3..d432c62 100644
--- a/LICENSE
+++ b/LICENSE
@@ -1,287 +1,21 @@
- EUROPEAN UNION PUBLIC LICENCE v. 1.2
- EUPL © the European Union 2007, 2016
-
-This European Union Public Licence (the ‘EUPL’) applies to the Work (as defined
-below) which is provided under the terms of this Licence. Any use of the Work,
-other than as authorised under this Licence is prohibited (to the extent such
-use is covered by a right of the copyright holder of the Work).
-
-The Work is provided under the terms of this Licence when the Licensor (as
-defined below) has placed the following notice immediately following the
-copyright notice for the Work:
-
- Licensed under the EUPL
-
-or has expressed by any other means his willingness to license under the EUPL.
-
-1. Definitions
-
-In this Licence, the following terms have the following meaning:
-
-- ‘The Licence’: this Licence.
-
-- ‘The Original Work’: the work or software distributed or communicated by the
- Licensor under this Licence, available as Source Code and also as Executable
- Code as the case may be.
-
-- ‘Derivative Works’: the works or software that could be created by the
- Licensee, based upon the Original Work or modifications thereof. This Licence
- does not define the extent of modification or dependence on the Original Work
- required in order to classify a work as a Derivative Work; this extent is
- determined by copyright law applicable in the country mentioned in Article 15.
-
-- ‘The Work’: the Original Work or its Derivative Works.
-
-- ‘The Source Code’: the human-readable form of the Work which is the most
- convenient for people to study and modify.
-
-- ‘The Executable Code’: any code which has generally been compiled and which is
- meant to be interpreted by a computer as a program.
-
-- ‘The Licensor’: the natural or legal person that distributes or communicates
- the Work under the Licence.
-
-- ‘Contributor(s)’: any natural or legal person who modifies the Work under the
- Licence, or otherwise contributes to the creation of a Derivative Work.
-
-- ‘The Licensee’ or ‘You’: any natural or legal person who makes any usage of
- the Work under the terms of the Licence.
-
-- ‘Distribution’ or ‘Communication’: any act of selling, giving, lending,
- renting, distributing, communicating, transmitting, or otherwise making
- available, online or offline, copies of the Work or providing access to its
- essential functionalities at the disposal of any other natural or legal
- person.
-
-2. Scope of the rights granted by the Licence
-
-The Licensor hereby grants You a worldwide, royalty-free, non-exclusive,
-sublicensable licence to do the following, for the duration of copyright vested
-in the Original Work:
-
-- use the Work in any circumstance and for all usage,
-- reproduce the Work,
-- modify the Work, and make Derivative Works based upon the Work,
-- communicate to the public, including the right to make available or display
- the Work or copies thereof to the public and perform publicly, as the case may
- be, the Work,
-- distribute the Work or copies thereof,
-- lend and rent the Work or copies thereof,
-- sublicense rights in the Work or copies thereof.
-
-Those rights can be exercised on any media, supports and formats, whether now
-known or later invented, as far as the applicable law permits so.
-
-In the countries where moral rights apply, the Licensor waives his right to
-exercise his moral right to the extent allowed by law in order to make effective
-the licence of the economic rights here above listed.
-
-The Licensor grants to the Licensee royalty-free, non-exclusive usage rights to
-any patents held by the Licensor, to the extent necessary to make use of the
-rights granted on the Work under this Licence.
-
-3. Communication of the Source Code
-
-The Licensor may provide the Work either in its Source Code form, or as
-Executable Code. If the Work is provided as Executable Code, the Licensor
-provides in addition a machine-readable copy of the Source Code of the Work
-along with each copy of the Work that the Licensor distributes or indicates, in
-a notice following the copyright notice attached to the Work, a repository where
-the Source Code is easily and freely accessible for as long as the Licensor
-continues to distribute or communicate the Work.
-
-4. Limitations on copyright
-
-Nothing in this Licence is intended to deprive the Licensee of the benefits from
-any exception or limitation to the exclusive rights of the rights owners in the
-Work, of the exhaustion of those rights or of other applicable limitations
-thereto.
-
-5. Obligations of the Licensee
-
-The grant of the rights mentioned above is subject to some restrictions and
-obligations imposed on the Licensee. Those obligations are the following:
-
-Attribution right: The Licensee shall keep intact all copyright, patent or
-trademarks notices and all notices that refer to the Licence and to the
-disclaimer of warranties. The Licensee must include a copy of such notices and a
-copy of the Licence with every copy of the Work he/she distributes or
-communicates. The Licensee must cause any Derivative Work to carry prominent
-notices stating that the Work has been modified and the date of modification.
-
-Copyleft clause: If the Licensee distributes or communicates copies of the
-Original Works or Derivative Works, this Distribution or Communication will be
-done under the terms of this Licence or of a later version of this Licence
-unless the Original Work is expressly distributed only under this version of the
-Licence — for example by communicating ‘EUPL v. 1.2 only’. The Licensee
-(becoming Licensor) cannot offer or impose any additional terms or conditions on
-the Work or Derivative Work that alter or restrict the terms of the Licence.
-
-Compatibility clause: If the Licensee Distributes or Communicates Derivative
-Works or copies thereof based upon both the Work and another work licensed under
-a Compatible Licence, this Distribution or Communication can be done under the
-terms of this Compatible Licence. For the sake of this clause, ‘Compatible
-Licence’ refers to the licences listed in the appendix attached to this Licence.
-Should the Licensee's obligations under the Compatible Licence conflict with
-his/her obligations under this Licence, the obligations of the Compatible
-Licence shall prevail.
-
-Provision of Source Code: When distributing or communicating copies of the Work,
-the Licensee will provide a machine-readable copy of the Source Code or indicate
-a repository where this Source will be easily and freely available for as long
-as the Licensee continues to distribute or communicate the Work.
-
-Legal Protection: This Licence does not grant permission to use the trade names,
-trademarks, service marks, or names of the Licensor, except as required for
-reasonable and customary use in describing the origin of the Work and
-reproducing the content of the copyright notice.
-
-6. Chain of Authorship
-
-The original Licensor warrants that the copyright in the Original Work granted
-hereunder is owned by him/her or licensed to him/her and that he/she has the
-power and authority to grant the Licence.
-
-Each Contributor warrants that the copyright in the modifications he/she brings
-to the Work are owned by him/her or licensed to him/her and that he/she has the
-power and authority to grant the Licence.
-
-Each time You accept the Licence, the original Licensor and subsequent
-Contributors grant You a licence to their contributions to the Work, under the
-terms of this Licence.
-
-7. Disclaimer of Warranty
-
-The Work is a work in progress, which is continuously improved by numerous
-Contributors. It is not a finished work and may therefore contain defects or
-‘bugs’ inherent to this type of development.
-
-For the above reason, the Work is provided under the Licence on an ‘as is’ basis
-and without warranties of any kind concerning the Work, including without
-limitation merchantability, fitness for a particular purpose, absence of defects
-or errors, accuracy, non-infringement of intellectual property rights other than
-copyright as stated in Article 6 of this Licence.
-
-This disclaimer of warranty is an essential part of the Licence and a condition
-for the grant of any rights to the Work.
-
-8. Disclaimer of Liability
-
-Except in the cases of wilful misconduct or damages directly caused to natural
-persons, the Licensor will in no event be liable for any direct or indirect,
-material or moral, damages of any kind, arising out of the Licence or of the use
-of the Work, including without limitation, damages for loss of goodwill, work
-stoppage, computer failure or malfunction, loss of data or any commercial
-damage, even if the Licensor has been advised of the possibility of such damage.
-However, the Licensor will be liable under statutory product liability laws as
-far such laws apply to the Work.
-
-9. Additional agreements
-
-While distributing the Work, You may choose to conclude an additional agreement,
-defining obligations or services consistent with this Licence. However, if
-accepting obligations, You may act only on your own behalf and on your sole
-responsibility, not on behalf of the original Licensor or any other Contributor,
-and only if You agree to indemnify, defend, and hold each Contributor harmless
-for any liability incurred by, or claims asserted against such Contributor by
-the fact You have accepted any warranty or additional liability.
-
-10. Acceptance of the Licence
-
-The provisions of this Licence can be accepted by clicking on an icon ‘I agree’
-placed under the bottom of a window displaying the text of this Licence or by
-affirming consent in any other similar way, in accordance with the rules of
-applicable law. Clicking on that icon indicates your clear and irrevocable
-acceptance of this Licence and all of its terms and conditions.
-
-Similarly, you irrevocably accept this Licence and all of its terms and
-conditions by exercising any rights granted to You by Article 2 of this Licence,
-such as the use of the Work, the creation by You of a Derivative Work or the
-Distribution or Communication by You of the Work or copies thereof.
-
-11. Information to the public
-
-In case of any Distribution or Communication of the Work by means of electronic
-communication by You (for example, by offering to download the Work from a
-remote location) the distribution channel or media (for example, a website) must
-at least provide to the public the information requested by the applicable law
-regarding the Licensor, the Licence and the way it may be accessible, concluded,
-stored and reproduced by the Licensee.
-
-12. Termination of the Licence
-
-The Licence and the rights granted hereunder will terminate automatically upon
-any breach by the Licensee of the terms of the Licence.
-
-Such a termination will not terminate the licences of any person who has
-received the Work from the Licensee under the Licence, provided such persons
-remain in full compliance with the Licence.
-
-13. Miscellaneous
-
-Without prejudice of Article 9 above, the Licence represents the complete
-agreement between the Parties as to the Work.
-
-If any provision of the Licence is invalid or unenforceable under applicable
-law, this will not affect the validity or enforceability of the Licence as a
-whole. Such provision will be construed or reformed so as necessary to make it
-valid and enforceable.
-
-The European Commission may publish other linguistic versions or new versions of
-this Licence or updated versions of the Appendix, so far this is required and
-reasonable, without reducing the scope of the rights granted by the Licence. New
-versions of the Licence will be published with a unique version number.
-
-All linguistic versions of this Licence, approved by the European Commission,
-have identical value. Parties can take advantage of the linguistic version of
-their choice.
-
-14. Jurisdiction
-
-Without prejudice to specific agreement between parties,
-
-- any litigation resulting from the interpretation of this License, arising
- between the European Union institutions, bodies, offices or agencies, as a
- Licensor, and any Licensee, will be subject to the jurisdiction of the Court
- of Justice of the European Union, as laid down in article 272 of the Treaty on
- the Functioning of the European Union,
-
-- any litigation arising between other parties and resulting from the
- interpretation of this License, will be subject to the exclusive jurisdiction
- of the competent court where the Licensor resides or conducts its primary
- business.
-
-15. Applicable Law
-
-Without prejudice to specific agreement between parties,
-
-- this Licence shall be governed by the law of the European Union Member State
- where the Licensor has his seat, resides or has his registered office,
-
-- this licence shall be governed by Belgian law if the Licensor has no seat,
- residence or registered office inside a European Union Member State.
-
-Appendix
-
-‘Compatible Licences’ according to Article 5 EUPL are:
-
-- GNU General Public License (GPL) v. 2, v. 3
-- GNU Affero General Public License (AGPL) v. 3
-- Open Software License (OSL) v. 2.1, v. 3.0
-- Eclipse Public License (EPL) v. 1.0
-- CeCILL v. 2.0, v. 2.1
-- Mozilla Public Licence (MPL) v. 2
-- GNU Lesser General Public Licence (LGPL) v. 2.1, v. 3
-- Creative Commons Attribution-ShareAlike v. 3.0 Unported (CC BY-SA 3.0) for
- works other than software
-- European Union Public Licence (EUPL) v. 1.1, v. 1.2
-- Québec Free and Open-Source Licence — Reciprocity (LiLiQ-R) or Strong
- Reciprocity (LiLiQ-R+).
-
-The European Commission may update this Appendix to later versions of the above
-licences without producing a new version of the EUPL, as long as they provide
-the rights granted in Article 2 of this Licence and protect the covered Source
-Code from exclusive appropriation.
-
-All other changes or additions to this Appendix require the production of a new
-EUPL version.
+MIT License
+
+Copyright (c) 2026 Piotr Lewandowski, Madcoders
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
diff --git a/README.md b/README.md
index 5988e89..c7f59b9 100644
--- a/README.md
+++ b/README.md
@@ -5,15 +5,14 @@ badges on the product page and product tiles - driven by a product attribute you
-
+
-> **Status: 1.0 release candidate.** Functionally complete and green across the supported
-> Sylius/Symfony/database matrix. The API - service ids, settings paths, table names - is frozen for
-> 1.0; what it still wants is real-world use. Please report anything you hit.
+> **Status: stable.** 1.0.0 is released and the API - service ids, settings paths, table names,
+> configuration keys - is frozen for the 1.x line. Please report anything you hit.
>
> ```bash
-> composer require madcoders/sylius-brand-plugin:^1.0@RC
+> composer require madcoders/sylius-brand-plugin
> ```
>
> The brand hookable is reusable on your own product grids - see
@@ -214,4 +213,4 @@ Built and maintained by [Madcoders](https://www.madcoders.co).
## License
-[EUPL-1.2](LICENSE).
+[MIT](LICENSE). Copyright (c) 2026 Piotr Lewandowski, Madcoders.
diff --git a/composer.json b/composer.json
index 8692f32..ad3fa60 100644
--- a/composer.json
+++ b/composer.json
@@ -2,7 +2,7 @@
"name": "madcoders/sylius-brand-plugin",
"type": "sylius-plugin",
"description": "Brand plugin for Sylius 2.x - manage brands in the admin, resolve them from a product attribute, and show a brand overview, brand product listings and brand badges in the shop.",
- "license": "EUPL-1.2",
+ "license": "MIT",
"authors": [
{
"name": "Piotr Lewandowski",
@@ -11,11 +11,19 @@
"role": "Architect & Developer"
}
],
+ "homepage": "https://github.com/mad-coders/sylius-brand-plugin",
+ "support": {
+ "issues": "https://github.com/mad-coders/sylius-brand-plugin/issues",
+ "source": "https://github.com/mad-coders/sylius-brand-plugin",
+ "docs": "https://github.com/mad-coders/sylius-brand-plugin/blob/1.0/docs/INSTALLATION.md"
+ },
"keywords": [
"sylius",
"sylius-plugin",
+ "sylius2",
"brand",
- "manufacturer"
+ "manufacturer",
+ "ecommerce"
],
"require": {
"php": "^8.3",