This PR has been generated automatically.
For more details see
[upmerge_pr.yaml](/Sylius/Sylius/blob/1.13/.github/workflows/upmerge_pr.yaml).
**Remember!** The upmerge should always be merged with using `Merge pull
request` button.
In case of conflicts, please resolve them manually with usign the
following commands:
```
git fetch upstream
gh pr checkout <this-pr-number>
git merge upstream/2.0 -m "Resolve conflicts between 1.13 and 2.0"
```
If you use other name for the upstream remote, please replace `upstream`
with the name of your remote pointing to the `Sylius/Sylius` repository.
Once the conflicts are resolved, please run `git merge --continue` and
push the changes to this PR.
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.13 |
| Bug fix? | yes |
| New feature? | no |
| BC breaks? | no |
| Deprecations? | no |
| Related tickets | fixes #X, partially #Y, mentioned in #Z |
| License | MIT |
<!--
- Bug fixes must be submitted against the 1.12 branch
- Features and deprecations must be submitted against the 1.13 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
-->
This PR has been generated automatically.
For more details see
[upmerge_pr.yaml](/Sylius/Sylius/blob/1.13/.github/workflows/upmerge_pr.yaml).
**Remember!** The upmerge should always be merged with using `Merge pull
request` button.
In case of conflicts, please resolve them manually with usign the
following commands:
```
git fetch upstream
gh pr checkout <this-pr-number>
git merge upstream/2.0 -m "Resolve conflicts between 1.13 and 2.0"
```
If you use other name for the upstream remote, please replace `upstream`
with the name of your remote pointing to the `Sylius/Sylius` repository.
Once the conflicts are resolved, please run `git merge --continue` and
push the changes to this PR.
This PR was merged into the 1.13 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.13
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Related tickets | #16100
| License | MIT
Commits
-------
f0de556f17 [Maintenance] Update upgrade file
This PR has been generated automatically.
For more details see
[upmerge_pr.yaml](/Sylius/Sylius/blob/1.13/.github/workflows/upmerge_pr.yaml).
**Remember!** The upmerge should always be merged with using `Merge pull
request` button.
In case of conflicts, please resolve them manually with usign the
following commands:
```
git fetch upstream
gh pr checkout <this-pr-number>
git merge upstream/2.0 -m "Resolve conflicts between 1.13 and 2.0"
```
If you use other name for the upstream remote, please replace `upstream`
with the name of your remote pointing to the `Sylius/Sylius` repository.
Once the conflicts are resolved, please run `git merge --continue` and
push the changes to this PR.
This PR was merged into the 1.13 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.13 |
| Bug fix? | no |
| New feature? | no |
| BC breaks? | no |
| Deprecations? | yes |
| Related tickets | - |
| License | MIT |
It's not used anywhere 🤷
Commits
-------
[Maintenance] Deprecate `SyliusLocaleEvents`
This PR has been generated automatically.
For more details see
[upmerge_pr.yaml](/Sylius/Sylius/blob/1.13/.github/workflows/upmerge_pr.yaml).
**Remember!** The upmerge should always be merged with using `Merge pull
request` button.
In case of conflicts, please resolve them manually with usign the
following commands:
```
git fetch upstream
gh pr checkout <this-pr-number>
git merge upstream/1.13 -m "Resolve conflicts between 1.12 and 1.13"
```
If you use other name for the upstream remote, please replace `upstream`
with the name of your remote pointing to the `Sylius/Sylius` repository.
Once the conflicts are resolved, please run `git merge --continue` and
push the changes to this PR.
This PR has been generated automatically.
For more details see
[upmerge_pr.yaml](/Sylius/Sylius/blob/1.13/.github/workflows/upmerge_pr.yaml).
**Remember!** The upmerge should always be merged with using `Merge pull
request` button.
In case of conflicts, please resolve them manually with usign the
following commands:
```
git fetch upstream
gh pr checkout <this-pr-number>
git merge upstream/2.0 -m "Resolve conflicts between 1.13 and 2.0"
```
If you use other name for the upstream remote, please replace `upstream`
with the name of your remote pointing to the `Sylius/Sylius` repository.
Once the conflicts are resolved, please run `git merge --continue` and
push the changes to this PR.
This PR was merged into the 1.13 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.13
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Related tickets | N/A
| License | MIT
[Optimize firewall configuration](https://symfony.com/bundles/LiipImagineBundle/current/basic-usage.html#optimize-firewall-configuration)
Commits
-------
[Maintenance] Add image firewall
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 | fixes#16068, |
| License | MIT |
<!--
- Bug fixes must be submitted against the 1.12 branch
- Features and deprecations must be submitted against the 1.13 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
-->
Its the same behavior as in: #16031
Commits
-------
BUGFIX: [ShopBundle] #16068 wrap long text in product description
This PR was merged into the 1.13 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.13
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Related tickets | N/A
| License | MIT
Commits
-------
3491859b3d [Maintenance] Change tex to tax
96c85e565a [Maintenance] Change names of tests
This PR was merged into the 1.13 branch.
Discussion
----------
This PR has been generated automatically.
For more details see [refactor.yaml](/Sylius/Sylius/blob/1.12/.github/workflows/refactor.yaml).
Commits
-------
b74deac766 [CS][DX] Refactor
This PR was merged into the 1.13 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.13
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Related tickets | N/A
| License | MIT
Commits
-------
[API][Maintenance] Remove unnecessary enabled option
This PR was merged into the 1.12 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.12. <!-- see the comment below --> |
| Bug fix? | yes. |
| New feature? | no. |
| BC breaks? | no. |
| Deprecations? | no. <!-- don't forget to update the UPGRADE-*.md file --> |
| Related tickets | fixes#16031 |
| License | MIT |
<!--
- Bug fixes must be submitted against the 1.12 branch
- Features and deprecations must be submitted against the 1.13 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
-->
As already described in #16031
When you have a long text in the notes info without any spaces and new lines, the text doesent wrap and therefore it breaks out of the container.
So i added a `word-break: break-word;` to the ID: `sylius-order-notes` in the `_ui.scss` file.
### Result
Commits
-------
BUGFIX: [AdminBundle] #16031 wrap long text in notes section
* 1.13:
[API][Test] Minor updating of functions name
[API][Test] Add common response for different databases
[API] Add respons for order item unit test
Add nullable to phpstan type
[Api][Shop] Improve orders tests
[Api][Shop] Add Checkout/CompletionTest
[Api][Shop] Add Checkout/PaymentMethodTest
[Api][Shop] Add Checkout/ShippingMethodTest
[Api][Shop] Add Checkout/CartTest
[Api][Shop] Add paymentNotFound validation to ChosenPaymentMethodEligibility class
This PR was merged into the 1.13 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.13
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Related tickets | N/A
| License | MIT
Based on #16063
Commits
-------
ede8121c8e [Api][Shop] Add paymentNotFound validation to ChosenPaymentMethodEligibility class
ad53e3d569 [Api][Shop] Add Checkout/CartTest
1663553482 [Api][Shop] Add Checkout/ShippingMethodTest
279156675c [Api][Shop] Add Checkout/PaymentMethodTest
1313080304 [Api][Shop] Add Checkout/CompletionTest
833ac87af3 [Api][Shop] Improve orders tests
3b4f5eba2a Add nullable to phpstan type
da70b88f70 [API] Add respons for order item unit test
9f07f0c3d1 [API][Test] Add common response for different databases
324f4300da [API][Test] Minor updating of functions name
* 1.13:
[Inventory] Fix deprecation note of sylius_inventory.checker configuration
[Inventory] Add deprecation for sylius_inventory.checker config
Add note to the UPGRADE file about changing the service argument
Using the service name for the availibilty checker
[API][Test] Minor updating of functions name
[Payum] Move validation groups configuration to PayumBundle
Move config to Core, SyliusPaymentBundle do not requires SyliusPayumBundle
[Api][Admin] Add ChannelNotFoundException to OrderAddressRequirementValidator
[Api][Admin] Change validation message of address requirement
[Api][Admin] Fix get channels test
[Api][Checkout] Add validation for required address
[Maintenance][API] Secure and cleanup openapi documentation modifiers
This PR was merged into the 1.13 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.13|
| Bug fix? | yes |
| New feature? | no |
| BC breaks? | nox |
| Deprecations? | yes <!-- don't forget to update the UPGRADE-*.md file --> |
| Related tickets | after https://github.com/Sylius/Sylius/pull/16062|
| License | MIT |
<!--
- Bug fixes must be submitted against the 1.12 branch
- Features and deprecations must be submitted against the 1.13 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
-------
[Inventory] Fix deprecation note of sylius_inventory.checker configuration
This PR was merged into the 1.13 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.12 |
| Bug fix? | yes (for plus users) |
| New feature? | no |
| BC breaks? | no |
| Deprecations? | no |
| Related tickets | - |
| License | MIT |
## The problem
With Sylius plus the `sylius.availability_checker` service is overwritten with a more complicated logic. Using the autowireable interface will always default to the Sylius core implemenation.
## The solution
Use the service name.
In the long run maybe deprecate the service name and only overwrite the interface in Sylius Plus.
Commits
-------
Using the service name for the availibilty checker
Add note to the UPGRADE file about changing the service argument
[Inventory] Add deprecation for sylius_inventory.checker config
