🐳 chore: 支持自动修改版本号

[AkashiCoin]

Summary by Sourcery

引入一个 GitHub Actions 工作流，以在打开或同步拉取请求时，自动更新特定路径中 'version' 文件的版本号。

CI:

• 添加一个 GitHub Actions 工作流，以在 'main' 或 'dev' 分支上打开或同步拉取请求时，自动更新 'version' 文件中的版本号。

Original summary in English

Summary by Sourcery

Introduce a GitHub Actions workflow to automate the version number update process in the 'version' file for specific paths when a pull request is opened or synchronized.

CI:

• Add a GitHub Actions workflow to automatically update the version number in the 'version' file when a pull request is opened or synchronized on the 'main' or 'dev' branches.

[sourcery-ai]

审核指南由 Sourcery 提供

此拉取请求引入了一个新的 GitHub Actions 工作流，当存储库中特定路径发生更改时，自动更新 version 文件中的版本号。该工作流在对 main 和 dev 分支的拉取请求时触发。

文件级更改

更改	详情	文件
实现 GitHub Actions 工作流以自动更新版本	创建一个新的 GitHub Actions 工作流文件 定义拉取请求的工作流触发条件 设置在 ubuntu-latest 上运行的作业 实现步骤以检出存储库、读取当前版本并检查版本文件更改 添加逻辑以使用新版本号更新版本文件 配置 git 用户并将更改推送回拉取请求分支	.github/workflows/update_version.yml

---

提示

• 通过在拉取请求中评论 @sourcery-ai review 来触发新的 Sourcery 审核。
• 通过直接回复审核评论继续与 Sourcery 的讨论。
• 您可以随时通过访问您的仪表板更改审核设置：
  • 启用或禁用 Sourcery 生成的拉取请求摘要或审核指南；
  • 更改审核语言；
• 如果您有任何问题或反馈，您可以随时联系我们。

Original review guide in English

Reviewer's Guide by Sourcery

This pull request introduces a new GitHub Actions workflow to automatically update the version number in the version file when changes are made to specific paths in the repository. The workflow is triggered on pull requests to the main and dev branches.

File-Level Changes

Change	Details	Files
Implement GitHub Actions workflow for automatic version updates	Create a new GitHub Actions workflow file Define workflow trigger conditions for pull requests Set up job to run on ubuntu-latest Implement steps to checkout repository, read current version, and check for version file changes Add logic to update version file with new version number Configure git user and push changes back to the pull request branch	.github/workflows/update_version.yml

---

Tips

• Trigger a new Sourcery review by commenting @sourcery-ai review on the pull request.
• Continue your discussion with Sourcery by replying directly to review comments.
• You can change your review settings at any time by accessing your dashboard:
  • Enable or disable the Sourcery-generated pull request summary or reviewer's guide;
  • Change the review language;
• You can always contact us if you have any questions or feedback.

[sourcery-ai]

嘿 @AkashiCoin - 我已经审查了你的更改 - 这里有一些反馈：

总体评论：

• 考虑使用 pull_request 而不是 pull_request_target 以提高安全性，除非你特别需要在此工作流中访问机密。
• 当前的实现可能会导致许多小的提交用于版本更新。考虑在发布过程中更新版本，以保持提交历史的整洁。

这是我在审查期间查看的内容

• 🟡 一般问题：发现1个问题
• 🟢 安全性：一切看起来都很好
• 🟢 测试：一切看起来都很好
• 🟢 复杂性：一切看起来都很好
• 🟢 文档：一切看起来都很好

---

Sourcery 对开源项目免费 - 如果你喜欢我们的评论，请考虑分享它们 ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{帮助我变得更有用！请点击 👍 或 👎 在每条评论上告诉我它是否有帮助。}

Original comment in English

Hey @AkashiCoin - I've reviewed your changes - here's some feedback:

Overall Comments:

• Consider using pull_request instead of pull_request_target for better security, unless you specifically need access to secrets in this workflow.
• The current implementation may lead to many small commits for version updates. Consider updating the version as part of the release process instead, to keep the commit history cleaner.

Here's what I looked at during the review

• 🟡 General issues: 1 issue found
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment to tell me if it was helpful.}

[sourcery-ai]

建议： 使用更强大的版本解析方法

考虑使用专用的版本库或更精确的正则表达式进行版本解析。这将使脚本更能抵御意外的版本字符串格式。

Suggested change

	version=$(echo $version_line | sed -E 's/__version__:\s*v([0-9]+\.[0-9]+\.[0-9]+)(-.+)?/\1/')
	version=$(python -c "import re; m = re.search(r'__version__:\s*v(\d+\.\d+\.\d+)', '$version_line'); print(m.group(1) if m else '')")

Original comment in English

suggestion: Use more robust version parsing methods

Consider using a dedicated versioning library or a more precise regex for version parsing. This would make the script more resilient to unexpected version string formats.

Suggested change

	version=$(echo $version_line | sed -E 's/__version__:\s*v([0-9]+\.[0-9]+\.[0-9]+)(-.+)?/\1/')
	version=$(python -c "import re; m = re.search(r'__version__:\s*v(\d+\.\d+\.\d+)', '$version_line'); print(m.group(1) if m else '')")