IBX-11778,IBX-12358,IBX-12530: Merged branch '4.6' into 5.0

[Steveb-p]

Caution

This is a merge pull request

🎫 Issue	IBX-11778,IBX-12358,IBX-12530

Related PRs:

• IBX-11778: Updated GitHub Actions workflows to org standard #142
• IBX-12530: Built integration test schema through SchemaBuilderEvent #146

[Steveb-p]

Conflict resolution note — composer.json.

Resolved by keeping 5.0's own tier pins and pulling in only the genuinely new dependency: ibexa/test-core, added by IBX-12358 on 4.6 and absent from 5.0's require-dev, translated to ~5.0.x-dev.

The other three keys 4.6 has that 5.0 lacks — ibexa/ci-scripts, friendsofphp/php-cs-fixer, symfony/proxy-manager-bridge — are pre-existing 4.6-only entries that 5.0 dropped deliberately, so they were not reintroduced.

[Steveb-p]

The failing User login providers tests / browser-tests check is an artifact of the temporary dependencies.json commit, not of the merge itself.

Evidence:

1. Comparing the full package sets installed by this PR's browser-test job against a currently-passing 5.0 PR (IBX-10894: Moved throw error when invitation not found in database to gateway #136), the only difference is one added package: ibexa/test-core (dev-merge/4.6-to-5.0). Every other package resolves to an identical version.
2. Upstream drift is ruled out — I re-ran IBX-10894: Moved throw error when invitation not found in database to gateway #136's browser job today and it still passes, so nothing that moved on 5.0 in the meantime is responsible.
3. This merge-up's own content cannot reach the browser suite: the diff is four files, all of them composer.json (one require-dev line), dependencies.json, tests/bootstrap.php and tests/integration/IbexaTestKernel.php. The features/browser/ tree is untouched.

The mechanism is that dependencies.json force-installs ibexa/test-core into the application the browser tests build. As an ibexa-bundle, it then gets registered app-wide rather than staying a test-only dependency, which perturbs this suite specifically. Six sibling merge-ups carrying the identical pin pass their browser tests, because their suites don't exercise the affected area.

This clears itself: the pin exists only until ibexa/test-core#48 lands, and must be removed before merging — at which point this check should go green. I'll re-run it as part of dropping the temporary commit.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud