Skip to content

chore: update version to 7.12.8#748

Merged
idranme merged 2 commits intomainfrom
dev
Apr 28, 2026
Merged

chore: update version to 7.12.8#748
idranme merged 2 commits intomainfrom
dev

Conversation

@idranme
Copy link
Copy Markdown
Collaborator

@idranme idranme commented Apr 28, 2026

Summary by Sourcery

更新群组成员信息的日志记录方式,并提升项目版本。

Enhancements:

  • 记录完整的群组成员信息对象,而不仅仅是其中的 baseInfo 部分。

Chores:

  • 将项目版本常量提升到 7.12.8,并同步相关的发行元数据文件。
Original summary in English

Summary by Sourcery

Update logging of group member info and bump project version.

Enhancements:

  • Log full group member info object instead of only its baseInfo section.

Chores:

  • Bump project version constant to 7.12.8 and sync related distribution metadata files.

@sourcery-ai
Copy link
Copy Markdown
Contributor

sourcery-ai Bot commented Apr 28, 2026

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

审阅者指南

将项目版本更新为 7.12.8,并在群成员信息 action 中略微调整日志记录,同时包含相关文档/包元数据的变更。

按文件分类的变更

变更 详情 文件
在处理 GetGroupMemberInfo 时,记录完整的群成员信息对象,而不是只记录其简单/基础信息。
  • 修改日志记录调用,以输出整个 info 对象,便于在处理群成员数据时进行调试或检查
  • 保留从 info 对象中提取 sex、qq_level 和 age 字段的既有逻辑
src/onebot11/action/group/GetGroupMemberInfo.ts
将应用/包版本从 7.12.7 提升到 7.12.8,并相应对齐发布元数据/文档。
  • 将导出的版本常量从 7.12.7 更新为 7.12.8
  • 调整打包发布配置以反映新版本
  • 在 doc 目录下更新或移动一个文本文档,可能作为发布资产的一部分
src/version.ts
a/doc/淔战捧.txt
b/doc/淔战捧.txt
package-dist.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

Updates the project version to 7.12.8 and slightly adjusts logging in the group member info action while including associated doc/package metadata changes.

File-Level Changes

Change Details Files
Log the full group member info object instead of only its simple/base info when handling GetGroupMemberInfo.
  • Change logger call to output the entire info object for easier debugging or inspection while processing group member data
  • Preserve existing field extraction for sex, qq_level, and age from the info object
src/onebot11/action/group/GetGroupMemberInfo.ts
Bump application/package version from 7.12.7 to 7.12.8 and align distribution metadata/docs accordingly.
  • Update the exported version constant from 7.12.7 to 7.12.8
  • Adjust packaged distribution configuration to reflect the new version
  • Update or relocate a documentation text file under the doc directory, likely as part of distribution assets
src/version.ts
a/doc/淔战捧.txt
b/doc/淔战捧.txt
package-dist.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.

Hey - 我发现了 1 个问题,并给出了一些整体性的反馈:

  • 将整个 info 对象记录到日志中,而不是只记录 info.simpleInfo.baseInfo,可能会显著增加日志量,并暴露比预期更多的敏感字段;如果这只是用于调试,建议缩小日志中字段的范围。
给 AI Agent 的提示
Please address the comments from this code review:

## Overall Comments
- Logging the entire `info` object instead of `info.simpleInfo.baseInfo` may significantly increase log volume and expose more sensitive fields than intended; consider narrowing the logged fields if this was only for debugging.

## Individual Comments

### Comment 1
<location path="src/onebot11/action/group/GetGroupMemberInfo.ts" line_range="41" />
<code_context>
     }
     if (info) {
-      this.ctx.logger.info(info.simpleInfo.baseInfo)
+      this.ctx.logger.info(info)
       ret.sex = OB11Entities.sex(info.simpleInfo.baseInfo.sex)
       ret.qq_level = info.commonExt?.qqLevel && calcQQLevel(info.commonExt.qqLevel) || 0
</code_context>
<issue_to_address>
**🚨 suggestion (security):** Logging the full `info` object may be noisy and could include unnecessary or sensitive data; consider narrowing or changing the log level.

This change logs the entire `info` object instead of `info.simpleInfo.baseInfo`, which may increase log volume and expose additional fields (including possible identifiers/PII). Consider logging only the required subset or lowering this to debug/trace if the full object is needed for diagnostics.
</issue_to_address>

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

Hey - I've found 1 issue, and left some high level feedback:

  • Logging the entire info object instead of info.simpleInfo.baseInfo may significantly increase log volume and expose more sensitive fields than intended; consider narrowing the logged fields if this was only for debugging.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- Logging the entire `info` object instead of `info.simpleInfo.baseInfo` may significantly increase log volume and expose more sensitive fields than intended; consider narrowing the logged fields if this was only for debugging.

## Individual Comments

### Comment 1
<location path="src/onebot11/action/group/GetGroupMemberInfo.ts" line_range="41" />
<code_context>
     }
     if (info) {
-      this.ctx.logger.info(info.simpleInfo.baseInfo)
+      this.ctx.logger.info(info)
       ret.sex = OB11Entities.sex(info.simpleInfo.baseInfo.sex)
       ret.qq_level = info.commonExt?.qqLevel && calcQQLevel(info.commonExt.qqLevel) || 0
</code_context>
<issue_to_address>
**🚨 suggestion (security):** Logging the full `info` object may be noisy and could include unnecessary or sensitive data; consider narrowing or changing the log level.

This change logs the entire `info` object instead of `info.simpleInfo.baseInfo`, which may increase log volume and expose additional fields (including possible identifiers/PII). Consider logging only the required subset or lowering this to debug/trace if the full object is needed for diagnostics.
</issue_to_address>

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.

}
if (info) {
this.ctx.logger.info(info.simpleInfo.baseInfo)
this.ctx.logger.info(info)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🚨 suggestion (security): 将完整的 info 对象记录到日志中可能会产生大量噪声,并包含不必要或敏感的数据;建议缩小日志内容范围或调整日志级别。

这一改动会记录整个 info 对象,而不是 info.simpleInfo.baseInfo,这可能会增加日志体积并暴露额外字段(包括可能的标识符/个人隐私信息)。如果确实需要完整对象用于诊断,建议只记录必要的子集,或者将日志级别降为 debug/trace。

Original comment in English

🚨 suggestion (security): Logging the full info object may be noisy and could include unnecessary or sensitive data; consider narrowing or changing the log level.

This change logs the entire info object instead of info.simpleInfo.baseInfo, which may increase log volume and expose additional fields (including possible identifiers/PII). Consider logging only the required subset or lowering this to debug/trace if the full object is needed for diagnostics.

@github-actions
Copy link
Copy Markdown

Test Report

Job Status
unit-test ✅ success
e2e-test ✅ success

✅ All tests passed

@idranme idranme merged commit 99ba307 into main Apr 28, 2026
6 checks passed
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