| Q | A
|-----------------|-----
| Branch? | 2.0
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Related tickets | #17362
| License | MIT
| Q | A
|-----------------|-----
| Branch? | 2.0
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Related tickets | #17269
| License | MIT
This PR was merged into the 2.0 branch.
Discussion
----------
| Q | A
|-----------------|-----
| Branch? | 2.0
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Related tickets | n/a
| License | MIT
<!--
- Bug fixes must be submitted against the 1.13 branch
- Features and deprecations must be submitted against the 1.14 branch
- Features, removing deprecations and BC breaks must be submitted against the 2.0 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
-------
[Security] Remove custom PasswordHasher
[Security] Remove UserLogin
[Security] Remove SecurityChecker decorator
[Security] Add user_checker firewall option
Fix security login argument
Remove AdvancedUserInterface
Add chain user_checker config to firewalls
Add priority to EnabledUserChecker tag
Remove unused properties from User Model
Fix spec
Fix mysql migration type
Minor improvements
Add note to UPGRADE file about security related changes in UserBundle
[UserBundle] Minor improvements after code review
* 2.0:
Change sort_by filter to sylius_sort_by
Fix note in the UPGRADE file
[Composer] Bump TwigExtra to the 0.4 version
[UiBundle] Deprecate classes and services moved to TwigExtra package
Update upgrade file
[UserBundle] Unification of service names
Update upgrade file
[TaxonomyBundle] Unification os service names
Add note to UPGRADE guide
Use Twig Extra package
Update upgrade file
[ShippingBundle] Unification of service name
Update upgrade file
[ReviewBundle] Unification of service names
[PromotionBundle] Unification of sylius.registry_promotion_action
Update upgrade file
[TaxationBundle] Unification of service names
This PR was merged into the payment-request branch.
Discussion
----------
| Q | A
|-----------------|-----
| Branch? | payment-request
| Bug fix? | no
| New feature? | no
| BC breaks? | yes
| Deprecations? | no<!-- don't forget to update the UPGRADE-*.md file -->
| Related tickets |
| License | MIT
<!--
- Bug fixes must be submitted against the 1.13 branch
- Features and deprecations must be submitted against the 1.14 branch
- Features, removing deprecations and BC breaks must be submitted against the 2.0 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
-------
[Composer] Remove dependency to payum/core in Core component
Move Payum-related exception to PayumBundle
[OrderPay] Move Payum-related providers to PayumBundle
Move Payum-related translations to PayumBundle
[API] Remove non existing exception from status mapping
[API] Fix GatewayConfig class in serialization
Decouple CoreBundle from PayumBundle
[Composer] Change dependency from Core component to CoreBundle in PayumBundle
[OrderPay] Refactor services files in ShopBundle
Bring back SyliusPayumBundle to Admin and Api bundles
Move Payum-related configs and routings from ShopBundle to PayumBundle
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/payment-request -m "Resolve conflicts between 2.0 and payment-request"
```
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/payment-request -m "Resolve conflicts between 2.0 and payment-request"
```
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? | payment-request
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Related tickets | n/a
| License | MIT
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/payment-request -m "Resolve conflicts between 2.0 and payment-request"
```
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.
