Skip to content

IBX-12594: Bumped ibexa/jms-translation-bundle to ^3.0 - #829

Merged
ViniTou merged 1 commit into
6.0from
ibx-12594-jms-translation-bundle-3
Sep 21, 2026
Merged

ViniTou merged 1 commit into
6.0from
ibx-12594-jms-translation-bundle-3

Conversation

@ViniTou

@ViniTou ViniTou commented Sep 15, 2026

Copy link
Copy Markdown
Contributor

Why

ibexa/jms-translation-bundle 3.0.0 is the Symfony 8 compatible major. Symfony 8.0 removed the XML DI configuration format that the bundle relied on, so the 2.x line cannot boot on Symfony 8 at all — this bump is a prerequisite for the wider Symfony 8 upgrade (IBX-12046).

3.0.0 also drops the replace: {"jms/translation-bundle": "..."} entry, which is why the sibling PRs in admin-ui, user and taxonomy switch to requiring the fork by name. This repo already required it by name, so only the constraint changes here.

Merge order

Blocked until ibexa/jms-translation-bundle 3.0.0 is tagged. Until then ^3.0 will not resolve and CI here will fail on dependency resolution — that is expected, not a defect in this PR.

Bundle PR: ibexa/jms-translation-bundle#10

Risk

The bundle's container shape is unchanged across 2.x → 3.0: service ids, aliases, tags and visibility flags were verified byte-for-byte identical, and the parent:/tag/decorates extension points this repo relies on resolve identically. No service definitions in this repo need to change.

Picks up the Symfony 8 compatible major.
@ViniTou
ViniTou force-pushed the ibx-12594-jms-translation-bundle-3 branch from d203f28 to 3afb916 Compare September 21, 2026 12:35
@sonarqubecloud

Copy link
Copy Markdown

@ViniTou
ViniTou merged commit 51f6698 into 6.0 Sep 21, 2026
15 of 20 checks passed
@ViniTou
ViniTou deleted the ibx-12594-jms-translation-bundle-3 branch September 21, 2026 14:17
ViniTou added a commit to ibexa/translations that referenced this pull request Sep 21, 2026
ibexa/core#829 is merged, so 6.0.x-dev requires ibexa/jms-translation-bundle
^3.0 itself and the pinned branch no longer exists.
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.

5 participants