Skip to content

chore(release): align Viewer 5.21.10 product SHA - #141

Merged
Shuang-su merged 1 commit into
mainfrom
codex/mf-139-release-record
Oct 10, 2026
Merged

Shuang-su merged 1 commit into
mainfrom
codex/mf-139-release-record

Conversation

@Shuang-su

@Shuang-su Shuang-su commented Oct 10, 2026 •

Copy link
Copy Markdown
Owner

回填 PR #140 正常 squash 后的实际产品 SHA,保持 metadata/public Version History、index.release 与 Ledger 一致。产品代码、100 项资源对象与 Editor/Director 不变。

Validation: 160 单测、版本镜像、release contract 和 diff 检查;产品精确 HEAD CI 38037012781 全通过。正式 tag/build 和 Netlify 候选、生产回读及 15 分钟观察完成后追加。

Refs #139


Note

Low Risk
Documentation and JSON release pointers only; no viewer, resource, or runtime code changes.

Overview
Updates Viewer 5.21.10 release metadata to the squash-merged product commit 92958b569259e9cf1918efe0c006071b4fef2458 (PR #140), replacing the prior candidate SHA e72cff4d everywhere it was recorded.

data/index.json release.gitRef, data/version-history.json and metadata/version-history.json (documentedThrough, current.gitRef, and the 5.21.10 entry) now point at the same product SHA. Display version 5.21.10 and functional release notes are unchanged; this is bookkeeping only.

docs/changes/139-viewer-safari-loading/verification.md adds a 最终产品合并 section (squash SHA, CI 38037012781, production still on 5.21.9). docs/metaflow-viewer-change-ledger.md adds a matching product ledger line for the merged SHA.

Reviewed by Cursor Bugbot for commit 53ef3df. Bugbot is set up for automated code reviews on this repo. Configure here.

Copilot AI balanced review requested due to automatic review settings October 10, 2026 08:15

Copilot AI 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.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 10, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-10T08:25:11.111740Z 53ef3df PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@cursor

cursor Bot commented Oct 10, 2026

Copy link
Copy Markdown

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: 0167fee5-3223-4939-8a2a-3daec5db31f5)

@Shuang-su
Shuang-su merged commit 7188544 into main Oct 10, 2026
13 checks passed
@Shuang-su
Shuang-su deleted the codex/mf-139-release-record branch October 10, 2026 08:20

@chatgpt-codex-connector chatgpt-codex-connector 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.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 53ef3dfd4f

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

"scope": "viewer",
"date": "2026-10-10",
"gitRef": "e72cff4d3f3042db10fccf495dec2148c6a7d8c0",
"gitRef": "92958b569259e9cf1918efe0c006071b4fef2458",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Preserve candidate refs before replacing the release entry

Replacing the 5.21.10 entry’s gitRef removes e72cff4d... from the canonical Version History, while the newly documented final candidate 7328de7b... is also absent from maintenanceCommits; consequently, the machine-readable provenance no longer contains either candidate even though the Ledger says the candidate chain is preserved. Append those candidate refs to the history before pointing the current/product entry at the squash SHA, as was done for 5.21.9, rather than losing historical records during this update.

AGENTS.md reference: AGENTS.md:L67-L67

Useful? React with 👍 / 👎.

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