8000 chore: release main by github-actions[bot] · Pull Request #510 · KarinJS/Karin · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

chore: release main #510

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 14, 2025
Merged

chore: release main #510

merged 1 commit into from
Jul 14, 2025

Conversation

github-actions[bot]
Copy link
Contributor
@github-actions github-actions bot commented Jul 14, 2025

🤖 I have created a release beep boop

core: 1.10.19

1.10.19 (2025-07-14)

🐛 Bug Fixes

  • 修复lagrange环境下 调用getHistoryMsg只使用getGroupMsgHistory的问题 (#509) (225cc58)

This PR was generated with Release Please. See documentation.

好的,这是翻译成中文的 pull request 总结:

Sourcery 总结

发布核心包 v1.10.19,包含一个重要的 bug 修复。

Bug 修复:

  • 修复了在 Lagrange 环境中 getHistoryMsg 只使用 getGroupMsgHistory 的问题。

构建:

  • 核心包版本升级至 1.10.19。

文档:

  • 增加版本 1.10.19 的更新日志条目。
Original summary in English

Summary by Sourcery

Publish core package v1.10.19 with a critical bug fix.

Bug Fixes:

  • Fix getHistoryMsg only using getGroupMsgHistory in the Lagrange environment.

Build:

  • Bump core package version to 1.10.19.

Documentation:

  • Add changelog entry for version 1.10.19.

Copy link
Contributor
sourcery-ai bot commented Jul 14, 2025
## 审查者指南

此 PR 利用 Release Please 通过将新的错误修复条目添加到变更日志、更新包版本和更新发布清单来准备 1.10.19 版本。

### 文件级别变更

| 变更 | 详情 | 文件 |
| ------ | ------- | ----- |
| 添加 1.10.19 变更日志条目 | <ul><li>插入包含发布日期的新章节</li><li>记录 lagrange 环境中已修复的 getHistoryMsg 行为</li></ul> | `packages/core/CHANGELOG.md` |
| 将包版本提升至 1.10.19 | <ul><li>将 version 字段从 1.10.18 更新为 1.10.19</li></ul> | `packages/core/package.json` |
| 更新 release-please 清单 | <ul><li>在 .release-please-manifest.json 中反映新的 core 版本</li></ul> | `.release-please-manifest.json` |

---

<details>
<summary>提示和命令</summary>

#### 与 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` 以触发新的审查!

#### 自定义您的体验

访问您的 [仪表板](https://app.sourcery.ai) 以:
- 启用或禁用审查功能,例如 Sourcery 生成的 pull request 摘要、审查者指南等。
- 更改审查语言。
- 添加、删除或编辑自定义审查说明。
- 调整其他审查设置。

#### 获取帮助

- [联系我们的支持团队](mailto:support@sourcery.ai) 提出问题或反馈。
- 访问我们的 [文档](https://docs.sourcery.ai) 获取详细的指南和信息。
- 通过在 [X/Twitter](https://x.com/SourceryAI)、[LinkedIn](https://www.linkedin.com/company/sourcery-ai/) 或 [GitHub](https://github.com/sourcery-ai) 上关注我们,与 Sourcery 团队保持联系。

</details>
Original review guide in English

Reviewer's Guide

This PR leverages Release Please to prepare the 1.10.19 release by adding the new bug-fix entry to the changelog, bumping the package version, and updating the release manifest.

File-Level Changes

Change Details Files
Add 1.10.19 changelog entry
  • Insert new section with release date
  • Document the fixed getHistoryMsg behavior in lagrange environment
packages/core/CHANGELOG.md
Bump package version to 1.10.19
  • Update version field from 1.10.18 to 1.10.19
packages/core/package.json
Update release-please manifest
  • Reflect the new core version in .release-please-manifest.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

@sj817 sj817 merged commit 7596a12 into main Jul 14, 2025
@sj817 sj817 deleted the release-please--branches--main branch July 14, 2025 23:12
Copy link
Contributor Author

🤖 Created releases:

🌻

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.

1 participant
0