Skip to content

[UPMERGE] 2.0 -> 2.1#423

Merged
NoResponseMate merged 4 commits into2.1from
upmerge/2.0_2.1
Jan 5, 2026
Merged

[UPMERGE] 2.0 -> 2.1#423
NoResponseMate merged 4 commits into2.1from
upmerge/2.0_2.1

Conversation

@SyliusBot
Copy link

This PR has been generated automatically.
For more details see 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.1 -m "Resolve conflicts between 2.0 and 2.1"

If you use other name for the upstream remote, please replace upstream with the name of your remote pointing to the Sylius/PayPalPlugin repository.

Once the conflicts are resolved, please run git merge --continue and push the changes to this PR.

NoResponseMate and others added 4 commits January 5, 2026 10:31
| Q               | A
| --------------- | -----
| Branch?         | 1.7
| Bug fix?        | kinda
| New feature?    | no
| Related tickets | related #412
This PR has been generated automatically.
For more details see
[upmerge_pr.yaml](/Sylius/PayPalPlugin/blob/1.7/.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.7 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/PayPalPlugin`
repository.

Once the conflicts are resolved, please run `git merge --continue` and
push the changes to this PR.
@NoResponseMate NoResponseMate merged commit bc23f2a into 2.1 Jan 5, 2026
44 checks passed
@NoResponseMate NoResponseMate deleted the upmerge/2.0_2.1 branch January 5, 2026 11:59
@SyliusBot SyliusBot restored the upmerge/2.0_2.1 branch January 6, 2026 02:40
@SyliusBot SyliusBot deleted the upmerge/2.0_2.1 branch January 7, 2026 02:41
@SyliusBot SyliusBot restored the upmerge/2.0_2.1 branch January 8, 2026 02:40
@SyliusBot SyliusBot deleted the upmerge/2.0_2.1 branch January 9, 2026 02:41
@SyliusBot SyliusBot restored the upmerge/2.0_2.1 branch January 10, 2026 02:37
@SyliusBot SyliusBot deleted the upmerge/2.0_2.1 branch January 11, 2026 02:48
@SyliusBot SyliusBot restored the upmerge/2.0_2.1 branch January 12, 2026 02:46
@SyliusBot SyliusBot deleted the upmerge/2.0_2.1 branch January 13, 2026 02:39
@SyliusBot SyliusBot restored the upmerge/2.0_2.1 branch January 14, 2026 02:45
@SyliusBot SyliusBot deleted the upmerge/2.0_2.1 branch January 15, 2026 02:41
@SyliusBot SyliusBot restored the upmerge/2.0_2.1 branch January 16, 2026 02:41
@SyliusBot SyliusBot deleted the upmerge/2.0_2.1 branch January 17, 2026 02:36
@SyliusBot SyliusBot restored the upmerge/2.0_2.1 branch January 18, 2026 02:47
@SyliusBot SyliusBot deleted the upmerge/2.0_2.1 branch January 19, 2026 02:46
@SyliusBot SyliusBot restored the upmerge/2.0_2.1 branch January 20, 2026 02:42
@SyliusBot SyliusBot deleted the upmerge/2.0_2.1 branch January 21, 2026 02:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants