Skip to content

Conversation

@gabriellsh
Copy link
Member

@gabriellsh gabriellsh commented Nov 18, 2025

Proposed changes (including videos or screenshots)

The mismatched version makes the useTranslation hook from react-i18next unable to get the i18next instance from the TranslationProvider that is rendered by the apps/meteor app. This issue happens only on develop due to the dependency being a devDependency only, so up until now no workspace should have been impacted.

Issue(s)

Steps to test or reproduce

Further comments

Summary by CodeRabbit

  • New Features
    • Enabled internationalization support to facilitate multi-language localization capabilities across the UI kit.

@dionisio-bot
Copy link
Contributor

dionisio-bot bot commented Nov 18, 2025

Looks like this PR is ready to merge! 🎉
If you have any trouble, please check the PR guidelines

@changeset-bot
Copy link

changeset-bot bot commented Nov 18, 2025

⚠️ No Changeset found

Latest commit: 7e46afa

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Nov 18, 2025

Walkthrough

The i18next devDependency in fuselage-ui-kit is downgraded from ^23.10.1 to ~23.4.9. i18next and react-i18next are added to dependencies and peerDependencies with wildcard versions, restructuring the package's internationalization dependency declarations.

Changes

Cohort / File(s) Summary
Internationalization dependencies restructuring
packages/fuselage-ui-kit/package.json
i18next devDependency downgraded to ~23.4.9; i18next and react-i18next added to dependencies (); i18next and react-i18next added to peerDependencies ()

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

  • Verify version constraint compatibility: downgrade from ^23.10.1 to ~23.4.9 may affect functionality or introduce breaking changes
  • Confirm that wildcard versions (*) for dependencies and peerDependencies align with project versioning strategy and compatibility requirements
  • Check if this restructuring aligns with how other packages in the monorepo declare i18n dependencies

Poem

🐰 Hops through dependencies with glee,
From devDep to dep, wild and free,
i18next makes translations flow,
Peer or plain, watch it grow! 🌍✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check ✅ Passed The title clearly and specifically describes the main change: fixing an i18next version mismatch in fuselage-ui-kit that breaks app translations locally.
✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch fix/i18nextVersion

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (1)
packages/fuselage-ui-kit/package.json (1)

42-114: Verify the fix resolves translations locally without breaking tests.

The PR description lacks critical details: no explanation of the version mismatch, no test results, no reproduction steps, and no linked issues. Before merging, please confirm:

  1. The fix has been tested locally and translations now work correctly.
  2. All existing tests pass with these version changes.
  3. No regressions are introduced in other parts of the codebase.
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

  • Jira integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 9f77c72 and 3f55f79.

⛔ Files ignored due to path filters (1)
  • yarn.lock is excluded by !**/yarn.lock, !**/*.lock
📒 Files selected for processing (1)
  • packages/fuselage-ui-kit/package.json (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
  • GitHub Check: 📦 Build Packages
  • GitHub Check: CodeQL-Build
  • GitHub Check: CodeQL-Build
🔇 Additional comments (1)
packages/fuselage-ui-kit/package.json (1)

111-114: Clarify the actual changes and address the wildcard version concern.

Your review contains an incorrect claim: i18next and react-i18next were not added to the dependencies section—they were added to peerDependencies with wildcard versions. The dependencies section remains unchanged with only internal @rocket.chat/* packages. However, your concern about wildcard versions is valid and worth addressing:

  • In devDependencies: i18next was downgraded from ^23.10.1 to ~23.4.9
  • In peerDependencies: i18next was added as * (allows any version)

This creates a contradictory constraint: the PR tightens the version in devDependencies but loosens it to any version in peerDependencies, which could reintroduce the mismatch you mention. Verify whether the wildcard versions are intentional for library compatibility or if they should be pinned to match the devDependencies versions.

Likely an incorrect or invalid review comment.

@github-actions
Copy link
Contributor

github-actions bot commented Nov 18, 2025

📦 Docker Image Size Report

📈 Changes

Service Current Baseline Change Percent
sum of all images 1.2GiB 1.2GiB +12MiB
rocketchat 359MiB 347MiB +12MiB
omnichannel-transcript-service 132MiB 132MiB -9B
queue-worker-service 132MiB 132MiB +398B
ddp-streamer-service 126MiB 126MiB -297B
account-service 113MiB 113MiB +768B
stream-hub-service 111MiB 111MiB +1.5KiB
authorization-service 111MiB 111MiB +141B
presence-service 111MiB 111MiB +6B

📊 Historical Trend

---
config:
  theme: "dark"
  xyChart:
    width: 900
    height: 400
---
xychart
  title "Image Size Evolution by Service (Last 30 Days + This PR)"
  x-axis ["11/15 22:28", "11/16 01:28", "11/17 23:50", "11/18 22:53", "11/19 23:02", "11/21 16:49", "11/24 17:34", "11/27 22:32", "11/28 19:05", "12/01 23:01", "12/02 21:57", "12/03 21:00", "12/04 18:17", "12/05 21:56", "12/08 18:25", "12/08 19:07 (PR)"]
  y-axis "Size (GB)" 0 --> 0.5
  line "account-service" [0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11]
  line "authorization-service" [0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11]
  line "ddp-streamer-service" [0.12, 0.12, 0.12, 0.12, 0.12, 0.12, 0.12, 0.12, 0.12, 0.12, 0.12, 0.12, 0.12, 0.12, 0.12, 0.12]
  line "omnichannel-transcript-service" [0.14, 0.14, 0.14, 0.14, 0.14, 0.13, 0.13, 0.13, 0.13, 0.13, 0.13, 0.13, 0.13, 0.13, 0.13, 0.13]
  line "presence-service" [0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11]
  line "queue-worker-service" [0.14, 0.14, 0.14, 0.14, 0.14, 0.13, 0.13, 0.13, 0.13, 0.13, 0.13, 0.13, 0.13, 0.13, 0.13, 0.13]
  line "rocketchat" [0.36, 0.36, 0.35, 0.35, 0.35, 0.34, 0.34, 0.34, 0.34, 0.34, 0.34, 0.34, 0.34, 0.34, 0.34, 0.35]
  line "stream-hub-service" [0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11, 0.11]
Loading

Statistics (last 15 days):

  • 📊 Average: 1.5GiB
  • ⬇️ Minimum: 1.2GiB
  • ⬆️ Maximum: 1.6GiB
  • 🎯 Current PR: 1.2GiB
ℹ️ About this report

This report compares Docker image sizes from this build against the develop baseline.

  • Tag: pr-37549
  • Baseline: develop
  • Timestamp: 2025-12-08 19:07:14 UTC
  • Historical data points: 15

Updated: Mon, 08 Dec 2025 19:07:15 GMT

@gabriellsh gabriellsh changed the title fix: fuselage-ui-kit i18next version mismatch breaking app translations locally fix: fuselage-ui-kit i18next version mismatch breaking apps translations locally Nov 18, 2025
@codecov
Copy link

codecov bot commented Dec 8, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 67.80%. Comparing base (27e4252) to head (7e46afa).
⚠️ Report is 1 commits behind head on develop.

Additional details and impacted files

Impacted file tree graph

@@             Coverage Diff             @@
##           develop   #37549      +/-   ##
===========================================
- Coverage    67.88%   67.80%   -0.08%     
===========================================
  Files         3450     3450              
  Lines       113976   113976              
  Branches     20955    20955              
===========================================
- Hits         77374    77286      -88     
- Misses       34473    34574     +101     
+ Partials      2129     2116      -13     
Flag Coverage Δ
e2e 57.33% <ø> (-0.01%) ⬇️
e2e-api 42.21% <ø> (-0.91%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@tassoevan tassoevan added this to the 7.14.0 milestone Dec 8, 2025
@tassoevan tassoevan added the stat: QA assured Means it has been tested and approved by a company insider label Dec 8, 2025
@dionisio-bot dionisio-bot bot added the stat: ready to merge PR tested and approved waiting for merge label Dec 8, 2025
@kodiakhq kodiakhq bot merged commit 455506a into develop Dec 8, 2025
50 checks passed
@kodiakhq kodiakhq bot deleted the fix/i18nextVersion branch December 8, 2025 19:31
@dougfabris dougfabris modified the milestones: 7.14.0, 8.0.0 Jan 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

stat: QA assured Means it has been tested and approved by a company insider stat: ready to merge PR tested and approved waiting for merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants