Skip to content

Conversation

@TomasVotruba
Copy link
Member

@TomasVotruba TomasVotruba commented Oct 9, 2025

Add compat test to run in CI right here.

Ref https://github.com/rectorphp/rector-compat-tests
Ref rectorphp/rector#9416

@TomasVotruba TomasVotruba changed the title [ci] merge linter to code analysis, as same topic [ci] Run PHPStan 12 and PHPStan compatibilty check Oct 9, 2025
@TomasVotruba TomasVotruba force-pushed the tv-ci-test-compat branch 3 times, most recently from cf90abe to a2e4d82 Compare October 9, 2025 22:09
@samsonasik
Copy link
Member

PR title need to be updated as "PHPUnit 12", not "PHPStan 12"

@TomasVotruba TomasVotruba changed the title [ci] Run PHPStan 12 and PHPStan compatibilty check [ci] Run PHPUnit 12 and PHPStan compatibilty check Oct 10, 2025
@TomasVotruba TomasVotruba merged commit 8e317cb into main Oct 10, 2025
51 checks passed
@TomasVotruba TomasVotruba deleted the tv-ci-test-compat branch October 10, 2025 14:59
@TomasVotruba
Copy link
Member Author

Let's ship this 👍

php-version: 8.2
coverage: none

- run: composer create-project "rector/rector-compat-tests:dev-main" .
Copy link
Member

@samsonasik samsonasik Oct 10, 2025

Choose a reason for hiding this comment

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

The rector/rector-compat-tests uses "rector/rector" dev-main, which new PR is different with existing downgraded "rector/rector" dev-main -> that require merged first and then we can see another verify in next another PR.

I think we need mechanism that it apply on each PR created:

  • downgrade rector-src into specific "folder" eg: "rector-scoped-testing"
  • use that rector-scoped-testing at rector/rector-compat-tests, eg: require rector-rector-src:dev-main#some-hash-PR

Copy link
Member Author

Choose a reason for hiding this comment

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

That's expected, as we only care about final product, downgraded and preloaded rector/rector.
The rector-src always worked, so it was not the issue

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