IBX-11778: Updated GitHub Actions workflows to org standard - #22
Merged
Merged
Conversation
- Bumped actions/checkout to v7 and actions/setup-node to v7 across backend-ci.yaml and frontend-ci.yaml. - Replaced direct ramsey/composer-install steps in backend-ci.yaml with ibexa/gh-workflows/actions/composer-install@main using the standard secrets inputs. - Pinned smoench/deptrac-action to tag 1.0.2 instead of the master branch (violation fix). - Renamed the backend workflow to "Backend CI" and added a bare workflow_dispatch trigger. - Added a set -euo pipefail guard to the check-cs | cs2pr step so check-cs failures are no longer masked by the pipe. - Standardized all runners to ubuntu-26.04 (replaced ubuntu-latest, ubuntu-22.04 and ubuntu-24.04). - Dropped the stale "main" branch from push triggers in backend-ci.yaml, browser-tests.yaml and frontend-ci.yaml. - Replaced the legacy zendesk-based release workflow with the skeleton release.yaml calling the reusable release_bundle workflow. - Deleted the obsolete pr-assign.yaml workflow. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The implicit matrix.php fallback inside the action is kept only for backwards compatibility (IBX-11907, gh-workflows#115); callers should state the version.
ibexa/gh-workflows/actions/composer-install@main runs shivammathur/setup-php itself, passing php-version, coverage, extensions and tools: cs2pr, so a job that also declares its own setup-php step configures PHP twice over. Removed 2 such step(s). Each one set exactly what the action already applies, so nothing had to move.
mikadamczyk
approved these changes
Sep 9, 2026
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related PRs:
Description:
Part of the fleet-wide GHA workflow standardization (wave 1; sample: ibexa/taxonomy#444). Changes:
Backend CIand added a bareworkflow_dispatchtrigger (IBX-12062, per the admin-ui#1999 PoC — without Slack notification parts).ubuntu-26.04.mainbranch from push triggers.pr-assign.yamlworkflow.ramsey/composer-installusage with the sharedibexa/gh-workflows/actions/composer-install@main(brings composer-audit-ignore handling).zendesk/action-create-release@v1,actions/checkout@master) with the standardrelease.yamlcallingrelease_bundle.yml.smoench/deptrac-action@masterbranch pin to the1.0.2tag.set -euo pipefailsocheck-csfailures are no longer masked (canonical fix from IBX-11853 / bundle-generator#45).ramsey/composer-installsteps carrieddependency-versions: "highest"(and in some jobscomposer-options), which the shared composer-install action does not support — those inputs were dropped, so the jobs now install like the rest of the fleet.For QA:
Verify CI is green. Backend CI can now also be run manually via workflow dispatch.
Documentation:
No documentation required.
🤖 Generated with Claude Code