Skip to content

IBX-11778: Merged branch '5.0' into 6.0 - #106

Merged
alongosz merged 4 commits into
6.0from
merge/5.0-to-6.0
Sep 19, 2026
Merged

alongosz merged 4 commits into
6.0from
merge/5.0-to-6.0

Conversation

@alongosz

Copy link
Copy Markdown
Member

Caution

This is a merge pull request

🎫 Issue IBX-11778

Related PRs:

🤖 Generated with Claude Code

alongosz and others added 4 commits September 13, 2026 19:52
For more details see https://ibexa.atlassian.net/browse/IBX-11778 and #103

Key changes:

* Renamed the CI workflow to "Backend CI" and added a bare workflow_dispatch trigger (IBX-12062)

* Bumped actions/checkout and actions/setup-node to v7

* Standardized all runner labels to ubuntu-26.04

* Dropped the non-existent main branch from the push triggers of backend-ci, browser-tests and frontend-ci

* Passed the PHP version to the shared composer-install action explicitly (IBX-11907)

* Guarded the code style check with set -euo pipefail so cs2pr no longer masks check-cs failures (IBX-11853)

* Removed the deprecated pr-assign.yaml workflow
# Conflicts:
#	.github/workflows/frontend-ci.yaml
Replaced the repository's own Rector job with a call to the shared
ibexa/gh-workflows rector.yml workflow, in the canonical form: an explicit
php-version, which the reusable workflow's input does not default
(gh-workflows#115), and the full secrets block, which the bare skeleton form
omits and which private packages need to avoid a 401.

The 4.6 sweep could not reach this job: Rector exists only on 5.0 and newer,
so there was nothing on the 4.6 side for git to report a conflict against.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@alongosz alongosz added the Fast-forward merge PR should be merged in a fast-forward way label Sep 18, 2026
@sonarqubecloud

Copy link
Copy Markdown

@alongosz
alongosz merged commit 0df8e44 into 6.0 Sep 19, 2026
14 checks passed
@alongosz
alongosz deleted the merge/5.0-to-6.0 branch September 19, 2026 17:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Fast-forward merge PR should be merged in a fast-forward way Ready for MERGE

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants