[Snyk] Upgrade @onflow/types from 1.4.1 to 1.4.2

[soham2008xyz]

Snyk has created this PR to upgrade @onflow/types from 1.4.1 to 1.4.2.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 1 version ahead of your current version.

• The recommended version was released 22 days ago.

Release notes

Package name: @onflow/types

• 1.4.2 - 2025-09-08
• 1.4.1 - 2024-11-27

from @onflow/types GitHub release notes

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• 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 upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[gemini-code-assist]

Summary of Changes

Hello @soham2008xyz, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on maintaining the project's dependency health by performing a minor version upgrade of the @onflow/types package. This automated update ensures that the project benefits from the latest stability and security improvements without introducing breaking changes. The change also includes an update to a related utility package, @onflow/util-logger, further solidifying the dependency chain.

Highlights

• Dependency Upgrade: The @onflow/types package has been upgraded from version 1.4.1 to 1.4.2.
• Sub-dependency Update: As part of the @onflow/types upgrade, its internal dependency @onflow/util-logger was also updated from 1.3.3 to 1.3.4.
• Automated Update: This pull request was automatically generated by Snyk to keep project dependencies up-to-date and enhance security.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request, automatically generated by Snyk, upgrades the @onflow/types package from version 1.4.1 to 1.4.2. While this is a patch update and generally safe, the change introduces a second version of @onflow/types into the dependency tree. Several other @onflow/* packages in the project remain pinned to version 1.4.1. I've added a comment with suggestions on how to resolve this to ensure a single, consistent version is used across the project, which will help prevent potential bugs and reduce the final bundle size.

[gemini-code-assist]

This pull request introduces a second version of the @onflow/types package into the project's dependencies.

While the root dependency is updated to 1.4.2, other packages like @onflow/fcl, @onflow/fcl-core, and @onflow/sdk still depend on version 1.4.1. This can be seen in the package-lock.json changes, where 1.4.1 is being added as a nested dependency.

Having multiple versions of the same package can lead to:

• Increased bundle size.
• Potential subtle bugs if the different versions are not fully compatible or if the package relies on singletons.

To resolve this, I recommend one of the following approaches:

1. Update related @onflow packages: Check if newer versions of @onflow/fcl, @onflow/fcl-core, and @onflow/sdk are available that depend on @onflow/types@^1.4.2. This is the cleanest solution.
2. Use overrides: If you are using npm v8+ or Yarn, you can use overrides (npm) or resolutions (Yarn) in your package.json to enforce a single version of @onflow/types. For example (for npm):

   "overrides": {
     "@onflow/types": "1.4.2"
   }

   If you are on an older npm version, you might need to use a tool like npm-force-resolutions.

This will ensure that only one version of @onflow/types is used throughout the project, leading to a more stable and smaller build.