Skip to content

Update vue-i18n package version (#934)#935

Merged
carlsims merged 1 commit into
csg-org:developmentfrom
InspiringApps:frontend/vue-i18n-upgrade
Jul 17, 2025
Merged

Update vue-i18n package version (#934)#935
carlsims merged 1 commit into
csg-org:developmentfrom
InspiringApps:frontend/vue-i18n-upgrade

Conversation

@rmolinares

@rmolinares rmolinares commented Jul 16, 2025

Copy link
Copy Markdown
Collaborator

Requirements List

  • Remove webroot/node_modules
  • From webroot: yarn install --ignore-engines

Description List

  • Update vue-i18n package to patched version due to vulnerability (moderate) discovered during package audit when running locally

Testing List

  • yarn test:unit:all should run without errors or warnings
  • yarn serve should run without errors or warnings
  • yarn build should run without errors or warnings
  • Code review
  • Testing:
    • Smoke test app, specifically concentrating on the copy throughout each page (including form inputs / dropdowns) and confirm everything looks / behaves as expected from that standpoint

Closes #934

Summary by CodeRabbit

  • Chores
    • Updated the "vue-i18n" library to version 10.0.8 for improved stability and compatibility.

@coderabbitai

coderabbitai Bot commented Jul 16, 2025

Copy link
Copy Markdown
Contributor

Walkthrough

The version of the "vue-i18n" dependency in the package.json file was updated from 10.0.6 to 10.0.8. No other files or configurations were modified.

Changes

Files Change Summary
webroot/package.json Updated "vue-i18n" version from 10.0.6 to 10.0.8

Assessment against linked issues

Objective Addressed Explanation
Upgrade vue-i18n to 10.0.8 (#934)

Poem

A hop and a skip, a version anew,
Vue-i18n now shines in 10.0.8’s hue!
With a twitch of my nose and a wiggle of glee,
The package is fresh as a carrot can be.
🥕✨ Hooray for upgrades, from this happy bunny—
Code grows stronger, swift as the sunny!


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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
webroot/package.json (1)

37-37: Confirm lock-file regeneration & optionally force‐pin via resolutions

The dependency bump to vue-i18n@10.0.8 is the right move for the CVE, but make sure:

  1. yarn.lock was deleted/re-generated and committed after the change; otherwise CI may still install the vulnerable 10.0.6.
  2. No other direct or transitive packages re-introduce 10.0.6. To guarantee this you can add a top-level resolution:
   "resolutions": {
+    "vue-i18n": "10.0.8",
     "stylelint-config-rational-order/**/trim": "^0.0.3",
  1. Verify that @intlify/unplugin-vue-i18n@0.6.2 declares compatibility with 10.0.8 (it usually does, but worth a quick peer-dep check).

Please rerun yarn install && yarn audit:dependencies && yarn test:unit:all locally and ensure the lockfile diff is included before merging.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7c06598 and f21a3ea.

⛔ Files ignored due to path filters (1)
  • webroot/yarn.lock is excluded by !**/yarn.lock, !**/*.lock
📒 Files selected for processing (1)
  • webroot/package.json (1 hunks)
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: jsandoval81
PR: csg-org/CompactConnect#873
File: webroot/src/styles.common/_inputs.less:115-118
Timestamp: 2025-06-24T00:17:31.188Z
Learning: The team intentionally uses broad CSS selectors like `.dp__input_wrap div { position: static; }` to fix styling issues with the Vue Date-Picker library. They have experience with these styles working well, keep the library version pinned in yarn.lock, and have established processes to re-test everything when updating the library version. This approach is acceptable given their testing discipline and version control.
webroot/package.json (1)
Learnt from: jsandoval81
PR: csg-org/CompactConnect#873
File: webroot/src/styles.common/_inputs.less:115-118
Timestamp: 2025-06-24T00:17:31.188Z
Learning: The team intentionally uses broad CSS selectors like `.dp__input_wrap div { position: static; }` to fix styling issues with the Vue Date-Picker library. They have experience with these styles working well, keep the library version pinned in yarn.lock, and have established processes to re-test everything when updating the library version. This approach is acceptable given their testing discipline and version control.

@rmolinares
rmolinares requested a review from jlkravitz July 16, 2025 22:10
@rmolinares

Copy link
Copy Markdown
Collaborator Author

@jlkravitz This is ready for your review.

FYI: This is a dependency vulnerability fix that may block other frontend PRs from being merged until this is merged.
Those other approved frontend PRs are currently: #926 and #932 .

@jlkravitz jlkravitz left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

@isabeleliassen good to merge

@jsandoval81

Copy link
Copy Markdown
Collaborator

@carlsims Would you have time to merge this today? It's a blocker to some other PRs we'd like to merge.

@carlsims
carlsims merged commit 580807e into csg-org:development Jul 17, 2025
2 checks passed
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.

Upgrade vue-i18n to 10.0.8

4 participants