Skip to content

chore: release main#640

Open
github-actions[bot] wants to merge 1 commit intomainfrom
release-please--branches--main
Open

chore: release main#640
github-actions[bot] wants to merge 1 commit intomainfrom
release-please--branches--main

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions bot commented Apr 1, 2026

🤖 I have created a release beep boop

core: 1.15.4

1.15.4 (2026-04-01)

🐛 Bug Fixes

  • getRkey returns undefined due to missing backward compatibility (#639) (87f1184)

This PR was generated with Release Please. See documentation.

Summary by Sourcery

发布新的 core 包版本 1.15.4,其中包含一个错误修复和更新后的元数据。

错误修复:

  • 更新文档,修复在使用向后兼容路径时,getRkey 返回 undefined 的问题说明。

构建:

  • 在清单文件中将 core 包版本从 1.15.3 提升到 1.15.4,以用于发布工具链。

文档:

  • 为 core v1.15.4 发布添加更新日志条目,包括此次记录的错误修复。
Original summary in English

Summary by Sourcery

Cut a new core package release 1.15.4 including a bugfix and updated metadata.

Bug Fixes:

  • Document fix for getRkey returning undefined when using backward compatibility paths.

Build:

  • Bump core package version from 1.15.3 to 1.15.4 in manifest files for release tooling.

Documentation:

  • Add changelog entry for core v1.15.4 release, including the recorded bugfix.

@sourcery-ai
Copy link
Copy Markdown
Contributor

sourcery-ai bot commented Apr 1, 2026

审阅者指南(在小型 PR 上折叠)

审阅者指南

将核心包的版本提升至 v1.15.4,更新元数据和变更日志,以记录修复 getRkey 向后兼容性问题的补丁。

文件级变更

变更 详情 文件
在变更日志中记录 1.15.4 核心版本及其 Bug 修复。
  • 新增 1.15.4 章节,包括发布日期和对比链接。
  • 记录描述 getRkey 向后兼容性问题的 Bug 修复条目,并附上对应的 issue 和提交链接。
packages/core/CHANGELOG.md
为此次发布将核心包版本提升到 1.15.4。
  • 在核心包元数据中将版本字段从 1.15.3 更新为 1.15.4。
  • 确保新版本号与变更日志条目和发布清单保持一致。
packages/core/package.json
.release-please-manifest.json

提示与命令

与 Sourcery 交互

  • 触发一次新的审阅: 在 Pull Request 中评论 @sourcery-ai review
  • 继续讨论: 直接回复 Sourcery 的审阅评论。
  • 从审阅评论生成 GitHub Issue: 在某条审阅评论下回复,请 Sourcery 根据该评论创建 issue。你也可以直接回复 @sourcery-ai issue,从该评论创建一个 issue。
  • 生成 Pull Request 标题: 在 Pull Request 标题的任意位置写上 @sourcery-ai,即可随时生成标题。你也可以在 Pull Request 中评论 @sourcery-ai title 来(重新)生成标题。
  • 生成 Pull Request 摘要: 在 Pull Request 正文的任意位置写上 @sourcery-ai summary,即可在指定位置生成 PR 摘要。你也可以在 Pull Request 中评论 @sourcery-ai summary 来(重新)生成摘要。
  • 生成审阅者指南: 在 Pull Request 中评论 @sourcery-ai guide,即可随时(重新)生成审阅者指南。
  • 一次性解决所有 Sourcery 评论: 在 Pull Request 中评论 @sourcery-ai resolve,即可解决所有 Sourcery 评论。当你已经处理完所有评论且不想再看到它们时非常有用。
  • 一次性忽略所有 Sourcery 审阅: 在 Pull Request 中评论 @sourcery-ai dismiss,即可忽略所有已有的 Sourcery 审阅。当你想从一次全新的审阅开始时尤其有用 —— 记得再评论 @sourcery-ai review 来触发新的审阅!

自定义使用体验

前往你的 控制面板 可以:

  • 启用或禁用审阅功能,例如 Sourcery 生成的 Pull Request 摘要、审阅者指南等。
  • 更改审阅语言。
  • 添加、移除或编辑自定义审阅说明。
  • 调整其他审阅设置。

获取帮助

Original review guide in English
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Release bump for the core package to v1.15.4, updating metadata and changelog to document a bug fix for getRkey backward compatibility.

File-Level Changes

Change Details Files
Documented the 1.15.4 core release and its bug fix in the changelog.
  • Added a new 1.15.4 section including release date and comparison link.
  • Recorded the bug fix entry describing the getRkey backward compatibility issue, with links to the issue and commit.
packages/core/CHANGELOG.md
Bumped the core package version to 1.15.4 for the release.
  • Updated the package version field from 1.15.3 to 1.15.4 in the core package metadata.
  • Ensured the new version aligns with the changelog entry and release manifest.
packages/core/package.json
.release-please-manifest.json

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
Contributor

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

嗨——我已经查看了你的修改,看起来很棒!


Sourcery 对开源项目是免费的——如果你觉得我们的评审有帮助,欢迎分享 ✨
帮我变得更有用!请在每条评论上点 👍 或 👎,我会根据你的反馈改进以后的评审。
Original comment in English

Hey - I've reviewed your changes and they look great!


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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants