This PR was merged into the 1.12 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.12 <!-- see the comment below --> |
| Bug fix? | no |
| New feature? | no |
| BC breaks? | no |
| Deprecations? | no<!-- don't forget to update the UPGRADE-*.md file --> |
| Related tickets | https://github.com/Sylius/Sylius/pull/14382 |
| License | MIT |
A complementary PR for this: https://github.com/Sylius/Sylius/pull/14505
Commits
-------
38db9df646 [Maintenance] Outdated Symfony 6 conflicts removed
This PR was merged into the 1.12 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.12 |
| Bug fix? | yes |
| New feature? | no |
| BC breaks? | no |
| Deprecations? | no |
| Related tickets | |
| License | MIT |
<!--
- Bug fixes must be submitted against the 1.11 branch
- Features and deprecations must be submitted against the 1.12 branch
- Make sure that the correct base branch is set
To be sure you are not breaking any Backward Compatibilities, check the documentation:
https://docs.sylius.com/en/latest/book/organization/backward-compatibility-promise.html
-->
Commits
-------
6d353ec4a9 Fix password hasher version
This PR was merged into the 1.11 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.11 |
| Bug fix? | no|
| New feature? | no |
| BC breaks? | no |
| Deprecations? | no |
| Related tickets | |
| License | MIT |
Future is now 🔥
Commits
-------
2567730398 Include 1.13 branch in the PR template
This PR was merged into the 1.11 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.11 |
| Bug fix? | yes |
| New feature? | no |
| BC breaks? | no |
| Deprecations? | no |
| Related tickets | replacement of #14318 |
| License | MIT |
<!--
- Bug fixes must be submitted against the 1.11 branch
- Features and deprecations must be submitted against the 1.12 branch
- Make sure that the correct base branch is set
To be sure you are not breaking any Backward Compatibilities, check the documentation:
https://docs.sylius.com/en/latest/book/organization/backward-compatibility-promise.html
-->
Commits
-------
efcf21713c [Maintenance] Removal of direct unneeded dependency on proxy manager LTS #14318
This PR was merged into the 1.12 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.12 <!-- see the comment below --> |
| Bug fix? | no |
| New feature? | no |
| BC breaks? | no |
| Deprecations? | no<!-- don't forget to update the UPGRADE-*.md file --> |
| License | MIT |
I didn't find this option documented in the Symfony docs, just a little info here:
https://symfony.com/doc/current/setup/upgrade_major.html#2-update-to-the-new-major-version-via-composer
and some info quoted from Symfony Cast - upgrade Symfony tutorial:
"This is a performance optimization from Flex: it basically makes sure that Flex only considers Symfony packages that match this version".
It looks like it may save some time working with the `composer update` command
Commits
-------
85482f5049 [Maintenance] extra.symfony.require configuration introduced
This PR was merged into the 1.12 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.12 |
| Bug fix? | no |
| New feature? | no |
| BC breaks? | no |
| Deprecations? | no |
| Related tickets | |
| License | MIT |
To be sure the upcoming Symfony 6.2 version does not result in any **major** problems, let's test it already 💃 I've decided to add a separate job, to be able to simplify it a little bit. Also, I've added `continue-on-error: true` flag, as it does not have to pass fully (some minor tweaks could be needed after the 6.2 release - and it's **ok**), we just need to see if there are any very serious problems we need to address right now.
For some reason 🤷♂️ If run all together Behat scenarios were spectacularly failing after ~4k of them 💥 As a quick fix for this bug (that needs to be investigated for sure), I've split running Behat scenarios into multiple commands.
I believe we could keep this pipeline after the Symfony 6.2 release and test with it Symfony 6.3 already. Maybe it would make supporting newer Symfony versions easier 🖖
Commits
-------
04004748ec Separate pipeline for non-JS tests on unstable Symfony version
This PR was merged into the 1.12 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.12 |
| Bug fix? | no |
| New feature? | no |
| BC breaks? | no |
| Deprecations? | no |
| Related tickets | |
| License | MIT |
Stable >>>>>>> unstable 🐴
Commits
-------
79171259c9 Bump to stable Resource (1.10) and Grid (1.12)
b857309c40 Allow stable 1.8 of FixturesBundle
This PR was merged into the 1.11 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.11 |
| Bug fix? | yes |
| New feature? | no |
| BC breaks? | no |
| Deprecations? | no |
| Related tickets | |
| License | MIT |
As said during the keynote speech on SyliusCon, we want to move back to naming Sylius as framework
<!--
- Bug fixes must be submitted against the 1.11 branch
- Features and deprecations must be submitted against the 1.12 branch
- Make sure that the correct base branch is set
To be sure you are not breaking any Backward Compatibilities, check the documentation:
https://docs.sylius.com/en/latest/book/organization/backward-compatibility-promise.html
-->
Commits
-------
1390b99508 [README] Switch Sylius naming from platform to framework
This PR was merged into the 1.12 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.12 <!-- see the comment below --> |
| Bug fix? | no |
| New feature? | no |
| BC breaks? | no |
| Deprecations? | no<!-- don't forget to update the UPGRADE-*.md file --> |
| License | MIT |
We can remove the bundle registration as it is included in `MicroKernelTrait`
<!--
- Bug fixes must be submitted against the 1.11 branch
- Features and deprecations must be submitted against the 1.12 branch
- Make sure that the correct base branch is set
To be sure you are not breaking any Backward Compatibilities, check the documentation:
https://docs.sylius.com/en/latest/book/organization/backward-compatibility-promise.html
-->
Commits
-------
e4c4408722 Kernel cleanup
This PR was merged into the 1.11 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.11 |
| Bug fix? | yes |
| New feature? | no |
| BC breaks? | no |
| Deprecations? | no |
| Related tickets | Backporting and fixing #14481 |
| License | MIT |
<!--
- Bug fixes must be submitted against the 1.11 branch
- Features and deprecations must be submitted against the 1.12 branch
- Make sure that the correct base branch is set
To be sure you are not breaking any Backward Compatibilities, check the documentation:
https://docs.sylius.com/en/latest/book/organization/backward-compatibility-promise.html
-->
Commits
-------
eeeafbae88 Adding batching to the expired carts remover
5b4d7b305a Update src/Sylius/Bundle/OrderBundle/Remover/ExpiredCartsRemover.php
fa86a8c7ce [Order] Skip empty flush during expired carts removal
This PR was merged into the 1.12 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.11 |
| Bug fix? | no |
| New feature? | no |
| BC breaks? | no |
| Deprecations? | no |
| Related tickets | - |
| License | MIT |
When running the clear cart remover it breaks the database or the memory usage, whatever dies first. So in this we flush regularly to also deal with big datasets and lots of carts to remove.
Commits
-------
0889f172b8 Adding batching to the expired carts remover
9e917d7c58 Update src/Sylius/Bundle/OrderBundle/Remover/ExpiredCartsRemover.php
This PR was merged into the 1.12 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.12 |
| Bug fix? | no |
| New feature? | no |
| BC breaks? | no |
| Deprecations? | |
| Related tickets | |
| License | MIT |
Commits
-------
70d2229d85 [Docs] Add warning about restricting Symfony version before Sylius installation
This PR was merged into the 1.12 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.12 |
| Bug fix? | yes |
| New feature? | no |
| BC breaks? | no |
| Deprecations? | no |
| Related tickets | |
| License | MIT |
We removed this alias [here](https://github.com/Sylius/Sylius/pull/13969/files#diff-676a77498218f1c920ba118a53a9ee921be3cf82f1f35faa5e96a2f2e9aa1b9eL272). I believe it's a BC break and this alias should still be there (of course, when the base service is registered - which is only in Symfony 5) 🖖
Commits
-------
d57de23fb6 Bring back security.authentication_manager alias if needed
This PR was merged into the 1.11 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.11 |
| Bug fix? | no |
| New feature? | no |
| BC breaks? | no |
| Deprecations? | no |
| Related tickets | |
| License | MIT |
Just a little bit 💃 Ref: https://sylius-devs.slack.com/archives/C3E4BU0QH/p1666204293221989
Commits
-------
15c8724d68 Delay 1.12 release for a few days
This PR was merged into the 1.12 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.12 |
| Bug fix? | yes |
| New feature? | no |
| BC breaks? | no |
| Deprecations? | no |
| Related tickets | |
| License | MIT |
After the https://github.com/Sylius/Sylius/pull/14402 merge and the [removal of default normalization group](https://github.com/Sylius/Sylius/pull/14402/files#diff-5c42df62aeb90479125f3100616bad0954aef6c1137444db381398a7fc2acaf1L19-L24), some problems raised up in our contract tests. I fixed them by adding proper serialization groups, but I believe the main issue is the inconsistency between `shop:order:read` and `shop:cart:read` groups and their usage. We should take a look at it and think, how to improve it (maybe they even should be combined together 🤷♂️).
Commits
-------
b0baebbabd Fixes in Order serialization after changes on 1.11
This PR was merged into the 1.11 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.11 |
| Bug fix? | yes |
| New feature? | no |
| BC breaks? | no |
| Deprecations? | no |
| Related tickets | |
| License | MIT |
This PR is a follow-up of https://github.com/Sylius/Sylius/pull/14402, and attends to remove the "default" normalization context groups and specify for each operation the proper normalization/denormalization context groups.
Commits
-------
e8aa5be450 [Api] fixed normalization/denormalization resources groups
This PR was merged into the 1.11 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.11 |
| Bug fix? | yes |
| New feature? | no |
| BC breaks? | yes (but the API is exprimental) |
| Deprecations? | no |
| Related tickets | |
| License | MIT |
When requesting `POST /api/v2/shop/orders`, the applied normalization group is `admin:order:read` whereas it should be `shop:order:read`. This could lead to exposing unexpected data.
I think that we can remove the "default" normalization context groups and specify for each operation the proper normalization/denormalization context groups (which fixes the bug and prevent future forgets).
Commits
-------
6b0d0d13d4 [Api] fixed order normalization groups
