Repository navigation
[UPMERGE] 5.1 -> 2026.x - #3293
Merged
Merged
Conversation
Both packages use typed class constants, which need PHP 8.3, but still declared "php": "^8.0". PHPStan derives the minimum PHP version from it and rejects every typed constant. The root package and 5.1 already require ^8.3.
[Composer] require PHP 8.3 for the Payment and PayumPayment components (5.0)
[CI] Add a stable required-check gate to the package and license workflows (5.0)
[CI] Add a stable required-check gate to the package and license workflows (5.1)
[UPMERGE] 5.0 -> 5.1
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Manual upmerge: it carries workflow changes (#3287, #3288), which the upmerge workflow cannot push with
GITHUB_TOKEN.Brings #3288, #3292 (with #3287 and #3290 from 5.0) into 2026.x. Conflicts in
license-check.yaml,packages_bundles.ymlandpackages_components.ymlwere resolved in favour of 2026.x, which already has the gates since #3284. The resulting tree is identical to 2026.x; only the history is merged.Remember! The upmerge should always be merged with using
Merge pull requestbutton.