Skip to content

Conversation

@GromNaN
Copy link
Member

@GromNaN GromNaN commented Dec 18, 2025

@codecov-commenter
Copy link

codecov-commenter commented Dec 18, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 87.83%. Comparing base (5c00cf5) to head (f9d74d5).
✅ All tests successful. No failed tests found.

Additional details and impacted files
@@            Coverage Diff            @@
##               v2.x    #1814   +/-   ##
=========================================
  Coverage     87.83%   87.83%           
  Complexity     3208     3208           
=========================================
  Files           428      428           
  Lines          6397     6397           
=========================================
  Hits           5619     5619           
  Misses          778      778           
Flag Coverage Δ
6.0-replica_set 86.63% <ø> (ø)
6.0-server 82.69% <ø> (ø)
6.0-sharded_cluster 86.41% <ø> (ø)
8.0-replica_set 87.69% <ø> (ø)
8.0-server 83.46% <ø> (ø)
8.0-sharded_cluster 87.52% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@github-advanced-security
Copy link

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

Comment on lines +430 to +229
<InvalidAttribute>
<code><![CDATA[NoDiscard]]></code>
<code><![CDATA[NoDiscard]]></code>
</InvalidAttribute>
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Psalm doesn't know this new attribute.

@GromNaN GromNaN force-pushed the PHPLIB-1752 branch 3 times, most recently from eb1f6b2 to 2d1895b Compare December 18, 2025 15:31
@GromNaN GromNaN marked this pull request as ready for review December 18, 2025 15:31
@GromNaN GromNaN requested a review from a team as a code owner December 18, 2025 15:31
@GromNaN GromNaN requested review from Copilot and jmikola December 18, 2025 15:31
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR upgrades the Psalm static analysis tool from version 6.5 to 6.14.2 and updates the PHP version used in CI workflows from 8.2 to 8.5.

Key changes:

  • Upgraded Psalm dependency and updated baseline file with new version-specific suppressions
  • Added @psalm-no-seal-properties annotations to Client and Database classes
  • Updated static analysis workflow to use PHP 8.5

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.

Show a summary per file
File Description
composer.json Updated Psalm version constraint from 6.5.* to ~6.14.2
psalm-baseline.xml Updated baseline with new Psalm version and added/removed issue suppressions
psalm.xml.dist Added suppressions for MissingOverrideAttribute and ClassMustBeFinal issues
src/Client.php Added @psalm-no-seal-properties annotation to prevent property sealing
src/Database.php Added @psalm-no-seal-properties annotation to prevent property sealing
.github/workflows/static-analysis.yml Updated PHP version from 8.2 to 8.5 for static analysis

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@GromNaN GromNaN force-pushed the PHPLIB-1752 branch 2 times, most recently from 7505ff7 to f425faf Compare January 6, 2026 15:51
@alcaeus
Copy link
Member

alcaeus commented Jan 19, 2026

Looks like we need to update PHP versions on Evergreen for this to work. I created PHPC-2663 to track this.

@GromNaN
Copy link
Member Author

GromNaN commented Jan 19, 2026

Looks like we need to update PHP versions on Evergreen for this to work. I created PHPC-2663 to track this.

Do we need to run psalm in evergreen?

@alcaeus
Copy link
Member

alcaeus commented Jan 20, 2026

Do we need to run psalm in evergreen?

We don't -- if you want to remove the psalm requirement before running composer install that would solve the issue as well.

Comment on lines +23 to +25
// Error with StaticCallOnNonStaticToInstanceCallRector
// https://github.com/rectorphp/rector/issues/9608
->withSkipPath(__DIR__ . '/tests/Builder/BuilderEncoderTest.php')
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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