Skip to content

Merge:'ci(fix)/chorebasci'| 修复和维护仓库Ci,消除运作告警.更新动作与重构。#301

Open
sunyink wants to merge 5 commits into
mainfrom
ci(fix)/chorebasci
Open

Merge:'ci(fix)/chorebasci'| 修复和维护仓库Ci,消除运作告警.更新动作与重构。#301
sunyink wants to merge 5 commits into
mainfrom
ci(fix)/chorebasci

Conversation

@sunyink
Copy link
Copy Markdown
Owner

@sunyink sunyink commented Jun 5, 2026

Summary by Sourcery

更新 CI 工作流和变更日志生成方式,以适配更新的 GitHub Actions 运行时,并改进发布说明的处理。

增强功能:

  • 调整变更日志的历史版本处理逻辑,在分析前截断发布内容,并在截断后的内容上运行高亮检测,以避免历史章节带来的噪音。

CI:

  • 在多个工作流中设置 FORCE_JAVASCRIPT_ACTIONS_TO_NODE24,以确保与最新的基于 Node 的 GitHub Actions 运行时兼容。
  • 在安装和发布工作流中,将 actions/checkoutactions/setup-pythonactions/upload-artifactactions/download-artifact 升级到其最新的主版本。
  • 将 Windows CI 任务切换为使用 windows-2025-vs2026 runner,并在 macOS 构建中禁用 Python 缓存,以避免反序列化警告。
Original summary in English

Summary by Sourcery

Update CI workflows and changelog generation to align with newer GitHub Actions runtimes and improve release note handling.

Enhancements:

  • Adjust changelog historical version processing to truncate release bodies before analysis and run highlight detection on the truncated content to avoid noise from historical sections.

CI:

  • Set FORCE_JAVASCRIPT_ACTIONS_TO_NODE24 across multiple workflows to ensure compatibility with the latest Node-based GitHub Actions runtime.
  • Upgrade actions/checkout, actions/setup-python, actions/upload-artifact, and actions/download-artifact to their latest major versions in install and release workflows.
  • Switch Windows CI jobs to use the windows-2025-vs2026 runner and disable Python cache on macOS builds to avoid deserialization warnings.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jun 5, 2026

Warning

Review limit reached

@sunyink, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 27 minutes and 25 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 33bc0d35-03b5-4b48-ad6d-9a9b19f0fe6d

📥 Commits

Reviewing files that changed from the base of the PR and between f127c7b and 7750749.

⛔ Files ignored due to path filters (1)
  • scripts/changelog_generator.py is excluded by none and included by none
📒 Files selected for processing (7)
  • .github/workflows/NotePush_Iss&Pr_Scheduled.yml
  • .github/workflows/NotePush_Issues_Real-time.yml
  • .github/workflows/NotePush_PullRequest_Real-time.yml
  • .github/workflows/ai-review.yml
  • .github/workflows/deepseek-review.yml
  • .github/workflows/install.yml
  • .github/workflows/sync_schema_files.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch ci(fix)/chorebasci

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

Comment @coderabbitai help to get the list of available commands and usage tips.

@sourcery-ai
Copy link
Copy Markdown

sourcery-ai Bot commented Jun 5, 2026

🧙 Sourcery 已完成对你的拉取请求的审查!


提示与命令

与 Sourcery 交互

  • 触发新的审查: 在拉取请求中评论 @sourcery-ai review
  • 继续讨论: 直接回复 Sourcery 的审查评论。
  • 从审查评论生成 GitHub issue: 通过回复某条审查评论,要求 Sourcery 从该评论创建一个 issue。你也可以在审查评论下回复 @sourcery-ai issue 来从中创建 issue。
  • 生成拉取请求标题: 在拉取请求标题中的任意位置写入 @sourcery-ai,即可在任意时间生成标题。你也可以在拉取请求中评论 @sourcery-ai title 来(重新)生成标题。
  • 生成拉取请求摘要: 在拉取请求正文中的任意位置写入 @sourcery-ai summary,即可在任意时间、你想要的位置生成 PR 摘要。你也可以在拉取请求中评论 @sourcery-ai summary 来(重新)生成摘要。
  • 生成审查者指南: 在拉取请求中评论 @sourcery-ai guide,即可在任意时间(重新)生成审查者指南。
  • 解决所有 Sourcery 评论: 在拉取请求中评论 @sourcery-ai resolve,即可将所有 Sourcery 评论标记为已解决。如果你已经处理了所有评论且不想再看到它们,这会很有用。
  • 撤销所有 Sourcery 审查: 在拉取请求中评论 @sourcery-ai dismiss,即可撤销所有现有的 Sourcery 审查。如果你想从头开始一次新的审查,这尤其有用——别忘了再评论 @sourcery-ai review 来触发新的审查!

自定义你的体验

打开你的 仪表板 以:

  • 启用或禁用审查功能,例如 Sourcery 生成的拉取请求摘要、审查者指南等。
  • 更改审查语言。
  • 添加、删除或编辑自定义审查指令。
  • 调整其他审查设置。

获取帮助

Original review guide in English

🧙 Sourcery has finished reviewing your pull request!


Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link
Copy Markdown

@sourcery-ai sourcery-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - 我在这里提供了一些整体性的反馈:

  • 你在多个 workflow 中设置了 FORCE_JAVASCRIPT_ACTIONS_TO_NODE24;可以考虑通过可复用的 workflow 或共享的 workflow 级策略来进行集中管理,以避免重复设置,并将未来的更改集中在一个地方。
  • 硬编码的 windows-2025-vs2026 runner 标签看起来非常特定;将其改为可配置(例如通过 matrix 或输入参数)可能会更安全,这样在更新 runner 镜像时就不需要在多个 workflow 中进行修改。
  • add_historical_versions 中,与其为 analyze_version_highlights 构造一个新的字典 {'body': truncated_body},不如考虑重构该函数,使其直接接受已经截断的 body,从而避免数据结构不匹配,并简化数据流。
给 AI 代理(Agent)的提示
Please address the comments from this code review:

## Overall Comments
- You are setting `FORCE_JAVASCRIPT_ACTIONS_TO_NODE24` in multiple workflows; consider centralizing this via a reusable workflow or a shared workflow-level strategy to avoid duplication and keep future changes in one place.
- The hard-coded `windows-2025-vs2026` runner label looks quite specific; it may be safer to make this configurable (e.g., via a matrix or input) so that updates to runner images don’t require multiple workflow edits.
- In `add_historical_versions`, instead of constructing a new dict `{'body': truncated_body}` for `analyze_version_highlights`, consider refactoring that function to accept the already-truncated body directly to avoid shape mismatches and simplify the data flow.

Sourcery 对开源项目是免费的——如果你喜欢我们的审查,请考虑分享给他人 ✨
帮我变得更有用!请在每条评论上点击 👍 或 👎,我会根据你的反馈改进后续的代码审查。
Original comment in English

Hey - I've left some high level feedback:

  • You are setting FORCE_JAVASCRIPT_ACTIONS_TO_NODE24 in multiple workflows; consider centralizing this via a reusable workflow or a shared workflow-level strategy to avoid duplication and keep future changes in one place.
  • The hard-coded windows-2025-vs2026 runner label looks quite specific; it may be safer to make this configurable (e.g., via a matrix or input) so that updates to runner images don’t require multiple workflow edits.
  • In add_historical_versions, instead of constructing a new dict {'body': truncated_body} for analyze_version_highlights, consider refactoring that function to accept the already-truncated body directly to avoid shape mismatches and simplify the data flow.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- You are setting `FORCE_JAVASCRIPT_ACTIONS_TO_NODE24` in multiple workflows; consider centralizing this via a reusable workflow or a shared workflow-level strategy to avoid duplication and keep future changes in one place.
- The hard-coded `windows-2025-vs2026` runner label looks quite specific; it may be safer to make this configurable (e.g., via a matrix or input) so that updates to runner images don’t require multiple workflow edits.
- In `add_historical_versions`, instead of constructing a new dict `{'body': truncated_body}` for `analyze_version_highlights`, consider refactoring that function to accept the already-truncated body directly to avoid shape mismatches and simplify the data flow.

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant