docs: record the post-release ecosystem verification and what it caught - #431
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
把 2026.8.15.2 / 2026.8.15.3 的沙箱与宿主机真实验证结果记进分析文档:六项判据的实测结果、验证抓到的「补救不成立」(openxlings/xlings#547),以及两次发布 GitCode 上传都撞 10 分钟步骤上限的运维记录 —— 含一条方法论:判据必须是 ranged GET 不是 HEAD,我第一次用
curl -I得到全部 401,险些据此判定 GitCode 一件都没上去。纯文档,无代码改动。