[Snyk] Security upgrade viem from 2.50.4 to 2.54.2

[hongtao023]

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• sdk/ts/examples/app_sessions/package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Asymmetric Resource Consumption (Amplification) SNYK-JS-WS-17344547	710

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[hongtao023]

This upgrade to viem includes breaking changes introduced in version 2.54.0 that affect ERC-20 token actions and the experimental viem/tempo module.

Breaking Changes:

• ERC-20 Token Symbol Resolution: ERC-20 token actions (like readContract with a token symbol) no longer resolve symbols from a built-in token list. You must now pass a tokens array to your Client instance with the token definitions you intend to use. Code that relies on the previous automatic symbol resolution will fail.
• viem/tempo Module: If you use the viem/tempo entrypoint, there are significant breaking changes:
  • Token balance and allowance read actions now return Amount objects instead of primitive types.
  • Token .call helpers now require the client instance as the first argument.

Recommendation:
Before merging, review all usages of ERC-20 token actions to ensure a tokens array is configured on your viem Client. If you are using viem/tempo, you must refactor your code to accommodate the new return types and function signatures.

Source: GitHub Releases

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

[coderabbitai]

Important

Review skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 2e592c56-d235-442a-a418-c4f9681b46b9

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch snyk-fix-7f4c1a4bc99710b7b0a8be5f94e69e3f

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}