Skip to content

chore(release): prepare v1.21.1 - #11

Merged
Sekai6 merged 2 commits into
mainfrom
release/v1.21.1
Aug 12, 2026
Merged

chore(release): prepare v1.21.1#11
Sekai6 merged 2 commits into
mainfrom
release/v1.21.1

Conversation

@Artistkisa

@Artistkisa Artistkisa commented Aug 12, 2026

Copy link
Copy Markdown
Collaborator

Release metadata

  • Bump application and lockfile version to v1.21.1.
  • Update the README documentation stamp for the formal v1.21.1 release.
  • Verified locally with npm run build, including the built SEO check.

This release publishes the merged Full-Spectrum Blackout combat orchestration fixes from PR #10.

Summary by Sourcery

Prepare the v1.21.1 release by updating version metadata and documentation.

Build:

  • Bump application version and lockfile metadata from v1.21.0 to v1.21.1.

Documentation:

  • Update README release stamp to reflect the v1.21.1 formal release date.

@sourcery-ai

sourcery-ai Bot commented Aug 12, 2026

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Release housekeeping for v1.21.1: bumps the project version and lockfile, and updates the README’s release metadata stamp to match the new formal release version and date.

File-Level Changes

Change Details Files
Update documentation metadata to reflect the v1.21.1 formal release.
  • Change the README data stamp version from v1.21.0 (development branch) to v1.21.1 (formal release).
  • Update the associated release date in the README data stamp from 2026-08-05 to 2026-08-12.
README.md
Bump application and lockfile versions to v1.21.1 for the new release.
  • Update the package manifest version field from 1.21.0 to 1.21.1.
  • Update the package lockfile version metadata from 1.21.0 to 1.21.1 to keep dependency resolution in sync with the manifest.
package.json
package-lock.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

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

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.

@kisara-ghost-review-checks

kisara-ghost-review-checks Bot commented Aug 12, 2026

Copy link
Copy Markdown

👻 GHOST Review

🔍 PR Summary

本次 PR 是纯发布元数据提交,将 README.md 中的版本戳从 v1.20.0 升级为 v1.21.1,并将导航栏中固定指向 v1.20.0 Release 的链接替换为指向最新 Release 的动态链接(/releases/latest)。变更范围极窄,仅涉及两处文档文字修改,无代码逻辑变更。npm-audit 报告了 nanoid(high)和 postcss(low)两个依赖漏洞,但均不在本次 diff 新增行中引入;这两个依赖在 package-lock.json 中已存在,本次 PR 未触碰该文件,因此不构成本次 PR 引入的新问题,不予列入 issues。总体风险极低,变更内容与 PR 描述完全吻合。


由 GHOST Review 自动生成

@kisara-ghost-review-checks

kisara-ghost-review-checks Bot commented Aug 12, 2026

Copy link
Copy Markdown

👻 GHOST Review

风险等级:low

关键变更

  • 将 README.md 导航栏中的固定版本链接 V1.20 Release 替换为动态最新版本链接 Latest Release,避免未来发布后链接过时
  • 将项目状态区块中的版本字符串从 v1.20.0 / V1.20 更新为 v1.21.1 / V1.21.1,与本次发布版本号保持一致

🧭 Review Guide

  1. README.md 第 18 行:确认 /releases/latest 链接目标(https://github.com/Sekai6/game-coldwar-intercept/releases/latest)在仓库中可访问,且 v1.21.1 tag 已在合并前或合并后立即推送;若 tag 尚未创建,/releases/latest 会指向旧版本,造成短暂文档不一致
  2. README.md 第 9 行(diff 外上下文):文档数据戳已硬编码为 'v1.21.1 正式版 · 2026-08-12',属于人工维护字段,无需 diff 修改但需人工核对日期是否与实际发布日期吻合

由 GHOST Review 自动生成

@kisara-ghost-review-checks

kisara-ghost-review-checks Bot commented Aug 12, 2026

Copy link
Copy Markdown

👻 GHOST Review

🔍 PR Summary

本次 PR 是纯发布元数据提交,将 README.md 中的版本戳从 v1.20.0 升级为 v1.21.1,并将导航栏中固定指向 v1.20.0 Release 的链接替换为指向最新 Release 的动态链接(/releases/latest)。变更范围极窄,仅涉及两处文档文字修改,无代码逻辑变更。npm-audit 报告了 nanoid(high)和 postcss(low)两个依赖漏洞,但均不在本次 diff 新增行中引入;这两个依赖在 package-lock.json 中已存在,本次 PR 未触碰该文件,因此不构成本次 PR 引入的新问题,不予列入 issues。总体风险极低,变更内容与 PR 描述完全吻合。

🗺️ 变更关系图

flowchart TD
    A["README v1.20.0"] -->|版本号替换| B["README v1.21.1"]
    A -->|固定标签链接 v1.20 Release| C["releases/tag/v1.20.0"]
    B -->|动态链接 Latest Release| D["releases/latest"]
Loading

由 GHOST Review 自动生成

@kisara-ghost-review-checks

Copy link
Copy Markdown

👻 GHOST Review 已准备好

💡 使用技巧与互动命令

与行内审查评论继续对话

直接回复 GHOST 的行内评论,并使用以下命令:

  • @ghost-review explain — 解释原审查问题的原因、触发条件和影响
  • @ghost-review why — 说明为什么值得修复,或纠正原评论误报
  • @ghost-review fix — 给出最小修复;可安全定位时提供 Suggested Change
  • @ghost-review alternative — 比较替代实现的复杂度、风险和适用条件
  • @ghost-review discuss — 用自然语言继续讨论代码边界与方案取舍

也可以带着 GHOST mention 直接提出自然语言问题,例如:

@ghost-review 混合场景下这个方案合理吗?

上述只读互动对外部贡献者开放;普通致谢和未 mention 的讨论不会触发模型。

PR 级协作者命令

以下命令仅限 OWNER、MEMBER 或 COLLABORATOR:

  • @ghost-review review — 重新进行完整代码审查
  • @ghost-review conflict — 重新检测冲突、深度分析,并在安全校验通过时展示建议解决代码(不写仓库)
  • @ghost-review fix-conflicts — 在安全边界内创建冲突修复分支和 Draft PR
  • @ghost-review summary — 生成或更新 PR 摘要
  • @ghost-review guide — 生成或更新 Review Guide
  • @ghost-review diagram — 生成或更新变更关系图
  • @ghost-review security — 进行安全专项审查
  • @ghost-review title — 建议 Conventional Commits 风格标题
  • @ghost-review resolve — 解决 GHOST 创建的 Review Threads
  • @ghost-review dismiss — 折叠 GHOST 的 Summary、Guide、Diagram 和帮助组件
  • @ghost-review clean — 清理旧组件和生命周期状态,然后重新审查
  • @ghost-review scan — 启动默认分支整仓安全扫描

在 GHOST 行内评论下还可使用:

  • @ghost-review issue — 把该行内问题转换成 GitHub Issue

帮助与自定义

  • @ghost-review help — 任何 PR 参与者都可以更新本指南
  • 仓库可通过 .ghost-review.yml 调整语言、严重度阈值、Summary、Guide、Diagram、自定义规则和自动标题。
  • 自动发布帮助:review.show_help: true
  • 可用 mention 别名:@kisara-ghost-review-checks, @kisara-ghost-review

GHOST Review · 回复 @ghost-review help 可再次查看本指南

@kisara-ghost-review-checks kisara-ghost-review-checks Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

本次增量审查发现新的行内问题。

Comment thread README.md

@Sekai6 Sekai6 left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

Release metadata and README version status are consistent. Build, SEO, domain verification, Sourcery, and GHOST checks completed.

@Sekai6
Sekai6 merged commit 9c2c5fd into main Aug 12, 2026
4 checks passed
@Sekai6
Sekai6 deleted the release/v1.21.1 branch August 12, 2026 05:43
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.

2 participants