chore(release): 修复工作流

[Alexzjt]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @Alexzjt, 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!

此拉取请求主要是一个维护性的“chore”任务，旨在通过一系列代码格式化和风格统一的更改来修复工作流。这些更改不涉及任何功能性变动，而是专注于提升代码库的整洁性、一致性和可读性，从而简化未来的维护工作。

Highlights

• 代码格式化: 统一了 JSON 配置文件中数组的格式，使其更紧凑，并优化了 TypeScript 文件中多行字符串的拼接和函数参数的换行。
• 字符串引用统一: 将 TypeScript 文件中的所有字符串引用从双引号统一为单引号，以提高代码风格的一致性。

Ignored Files

• Ignored by pattern: .github/workflows/** (2)
  • .github/workflows/auto-release.yml
  • .github/workflows/build.yml

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

本次 PR 主要进行了一些代码格式化和风格统一的工作，例如将多行数组改为单行，以及将字符串的双引号统一为单引号。这些改动有助于提升代码库的一致性和可读性。

我在代码中发现了一些可以改进的地方，主要集中在 TypeScript 的类型安全和异步代码的最佳实践方面。具体的建议请见各文件的评论。总的来说，代码质量不错，这些小调整能让它更上一层楼。

[gemini-code-assist]

在 filter 和 map 回调中对 item 使用 any 类型会禁用 TypeScript 的类型检查。为了在 map 中获得正确的类型推断，您可以在 filter 中使用类型谓词（type predicate）作为返回类型。这会告诉 TypeScript，filter 之后的数组只包含特定类型的元素，从而增强类型安全。

通过将 filter 的回调返回类型声明为 item is { type: 'text'; text: string }，TypeScript 就知道 map 接收的 item 具有 text 属性，且类型为 string。

Suggested change

	.filter((item: any) => item.type === 'text')
	.map((item: any) => item.text)
	.filter((item: any): item is { type: 'text'; text: string } => item.type === 'text')
	.map((item) => item.text)

[gemini-code-assist]

建议使用模板字符串（template literals）来构建错误信息，以提高代码的可读性。同时，将变量直接拼接到错误信息中可能存在风险，虽然此处 answer 似乎是文档内容，但在其他情况下可能导致敏感信息泄露到日志中。

Suggested change

	throw new Error('DeepWiki return Empty/Error Answer, Answer = ' + answer);
	throw new Error(`DeepWiki returned an empty or error answer. Answer: ${answer}`);