style: impove floating icon UI

[huhuanming]

Summary by CodeRabbit

• 新特性

  • 所有相关包的版本已更新至 2.2.3。

• 依赖项更新

  • 多个依赖项，包括 @onekeyfe/cross-inpage-provider-core、@onekeyfe/cross-inpage-provider-errors、@onekeyfe/cross-inpage-provider-types 和 @onekeyfe/extension-bridge-injected 的版本已更新至 2.2.3。

[coderabbitai]

Caution

Review failed

The pull request is closed.

概述

变更说明

此次更新是对多个包的版本进行了统一升级，从2.2.2版本更新到2.2.3版本。变更涉及跨平台提供者（cross-inpage-provider）生态系统中的几乎所有包，包括核心包、类型定义、错误处理、事件管理以及各种区块链提供者。

变更

文件路径	变更摘要
packages/*/package.json	版本从2.2.2升级到2.2.3
依赖包	同步更新相关依赖版本到2.2.3
packages/providers/inpage-providers-hub/src/floatingButton/index.tsx	修改了安全信息组件和浮动按钮的显示逻辑

详细变更

1. 版本升级范围：

   • 核心包
   • 类型定义包
   • 错误处理包
   • 事件管理包
   • 各种区块链提供者包（如Ethereum、Solana、Aptos等）

2. 代码变更：

   • 浮动按钮组件的安全信息展示逻辑有细微调整
   • 移除了showCloseDialog属性
   • 调整了组件定位和关闭对话框的方法

注意事项

这是一次全面但轻微的版本更新，主要目的是保持生态系统中各个包版本的一致性。没有引入重大功能变更或破坏性改动。

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between c8e8c48 and 3fb6134.

📒 Files selected for processing (33)

• packages/core/package.json (2 hunks)
• packages/desktop/desktop-bridge-injected/package.json (2 hunks)
• packages/empty/package.json (1 hunks)
• packages/errors/package.json (1 hunks)
• packages/events/package.json (1 hunks)
• packages/example/package.json (2 hunks)
• packages/extension/extension-bridge-hosted/package.json (2 hunks)
• packages/extension/extension-bridge-injected/package.json (2 hunks)
• packages/injected/package.json (2 hunks)
• packages/native/native-bridge-injected/package.json (2 hunks)
• packages/providers/inpage-providers-hub/package.json (2 hunks)
• packages/providers/inpage-providers-hub/src/floatingButton/index.tsx (5 hunks)
• packages/providers/onekey-algo-provider/package.json (2 hunks)
• packages/providers/onekey-alph-provider/package.json (2 hunks)
• packages/providers/onekey-aptos-provider/package.json (2 hunks)
• packages/providers/onekey-bfc-provider/package.json (2 hunks)
• packages/providers/onekey-btc-provider/package.json (2 hunks)
• packages/providers/onekey-cardano-provider/package.json (2 hunks)
• packages/providers/onekey-conflux-provider/package.json (2 hunks)
• packages/providers/onekey-cosmos-provider/package.json (2 hunks)
• packages/providers/onekey-eth-provider/package.json (2 hunks)
• packages/providers/onekey-near-provider/package.json (2 hunks)
• packages/providers/onekey-nostr-provider/package.json (2 hunks)
• packages/providers/onekey-polkadot-provider/package.json (2 hunks)
• packages/providers/onekey-private-provider/package.json (2 hunks)
• packages/providers/onekey-scdo-provider/package.json (2 hunks)
• packages/providers/onekey-solana-provider/package.json (2 hunks)
• packages/providers/onekey-sui-provider/package.json (2 hunks)
• packages/providers/onekey-ton-provider/package.json (2 hunks)
• packages/providers/onekey-tron-provider/package.json (2 hunks)
• packages/providers/onekey-webln-provider/package.json (2 hunks)
• packages/types/package.json (1 hunks)
• packages/webview/package.json (2 hunks)

---

🪧 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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 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 or 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.

[socket-security]

Report too large to display inline

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Critical CVE	npm/[email protected]	CVE: GHSA-hc6q-2mpp-qw7j Cross-realm object access in Webpack 5 (CRITICAL) Affected versions: >= 5.0.0, < 5.76.0 Patched version: 5.76.0	packages/injected/package.json packages/injected/yarn.lock	⚠︎
Critical CVE	npm/[email protected]	CVE: GHSA-76p3-8jx3-jpfq Prototype pollution in webpack loader-utils (CRITICAL) Affected versions: >= 2.0.0, < 2.0.3 Patched version: 2.0.3	packages/example/yarn.lock	⚠︎
Critical CVE	npm/@babel/[email protected]	CVE: GHSA-67hx-6x53-jw92 Babel vulnerable to arbitrary code execution when compiling specifically crafted malicious code (CRITICAL) Affected versions: < 7.23.2 Patched version: 7.23.2	packages/example/yarn.lock	⚠︎

View full report↗︎

Next steps

What is a critical CVE?

Contains a Critical Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/@babel/[email protected]