Permalink
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
- 13 commits
- 12 files changed
- 4 contributors
Commits on Jul 28, 2023
Commits on Jul 29, 2023
Commits on Jul 30, 2023
-
-
minor #51165 Remove 6.2 from the list of potential branch targets (fa…
…bpot) This PR was merged into the 5.4 branch. Discussion ---------- Remove 6.2 from the list of potential branch targets | Q | A | ------------- | --- | Branch? | 5.4 | Bug fix? | no | New feature? | no <!-- please update src/**/CHANGELOG.md files --> | Deprecations? | no <!-- please update UPGRADE-*.md and src/**/CHANGELOG.md files --> | Tickets | n/a | License | MIT | Doc PR | n/a 6.2 is not maintained anymore. Commits ------- 640d65d Remove 6.2 from the list of potential branch targets
-
minor #51151 [5.4] Fix symfony/deprecation-contracts require (fancyweb)
This PR was merged into the 5.4 branch. Discussion ---------- [5.4] Fix symfony/deprecation-contracts require | Q | A | ------------- | --- | Branch? | 5.4 | Bug fix? | yes | New feature? | no | Deprecations? | no | Tickets | - | License | MIT | Doc PR | - Require `symfony/deprecation-contracts` in package that use `trigger_deprecation` without requiring the dependency 🙈 . Commits ------- f6581f7 Fix symfony/deprecation-contracts require
Commits on Jul 31, 2023
-
-
minor #51175 CI: Disable Psalm's
findUnusedBaselineEntryfeature (d……errabus) This PR was merged into the 5.4 branch. Discussion ---------- CI: Disable Psalm's `findUnusedBaselineEntry` feature | Q | A | ------------- | --- | Branch? | 5.4 | Bug fix? | no | New feature? | no | Deprecations? | no | Tickets | N/A | License | MIT | Doc PR | N/A Psalm has introduced a feature for detecting unused entries in the error baseline. This is useful for a baseline that is maintained along with the code because it tells the developer when the baseline starts to smell and needs to be regenerated. However, we use the baseline differently: We generate the baseline on the fly in order to check if a PR introduces new errors. Failing on baseline entries that can be purged is not what we want in that case because a contributor cannot fix those errors. Example for a Psalm run that failed because of unused baseline entries: https://github.com/symfony/symfony/actions/runs/5706412328/job/15462071408 Commits ------- 9ffbb53 CI: Disable Psalm's findUnusedBaselineEntry feature
-
bug #51178 [Finder] Revert "Fix children condition in ExcludeDirector…
…yFilterIterator" (derrabus) This PR was merged into the 5.4 branch. Discussion ---------- [Finder] Revert "Fix children condition in ExcludeDirectoryFilterIterator" | Q | A | ------------- | --- | Branch? | 5.4 | Bug fix? | yes | New feature? | no | Deprecations? | no | Tickets | Fix #51162, revert #50885 | License | MIT | Doc PR | not needed This PR reverts #50885 because it did not fix a bug and instead introduced a regression described in #51162. Commits ------- 2fd4453 Revert "minor #50885 [Finder] Fix children condition in ExcludeDirectoryFilterIterator (mvorisek)"
-
-
-
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v5.4.26...v5.4.27