CHI-3998: Flex v2.18.0

[stephenhand]

Description

Checklist

• Corresponding issue has been opened
• New tests added
• Feature flags added
• Strings are localized
• Tested for chat contacts
• Tested for call contacts

Other Related Issues

None

Verification steps

AFTER YOU MERGE

1. Cut a release tag using the Github workflow. Wait for it to complete and notify in the #aselo-deploys Slack channel.
2. Comment on the ticket with the release tag version AND any additional instructions required to configure an environment to test the changes.
3. Only then move the ticket into the QA column in JIRA

You are responsible for ensuring the above steps are completed. If you move a ticket into QA without advising what version to test, the QA team will assume the latest tag has the changes. If it does not, the following confusion is on you! :-P

[Copilot]

🟡 Changes recommended

The local plugin manifest files still require Flex UI v1 (^1.11.2), which appears inconsistent with the Flex v2.18.0 upgrade and should be updated to avoid version/loader mismatches.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

Updates the plugin-hrm-form plugin’s Twilio Flex UI dependency to align with Flex v2.18.0, refreshing the npm lockfile accordingly.

Changes:

• Bump @twilio/flex-ui devDependency from 2.16.0 to ^2.18.0 in plugin-hrm-form.
• Regenerate package-lock.json to resolve @twilio/flex-ui@2.18.0 and updated transitive dependencies.

File summaries

File	Description
plugin-hrm-form/package.json	Updates the declared Flex UI devDependency version range.
plugin-hrm-form/package-lock.json	Lockfile refresh reflecting Flex UI 2.18.0 and new transitive packages.

Review details

Files not reviewed (1)

• plugin-hrm-form/package-lock.json: Generated file

• Files reviewed: 1/2 changed files
• Comments generated: 2
• Review effort level: Lite

---

💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.