docs(devlog): record the 2.57.0 release and its registry propagation state - #4832
Conversation
…state Evidence for every step of the train, the two judgment calls (red dev, CodeQL new-alert count), and the pending registry read that must not become a republish.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
✅ Deterministic PR hygiene checks passed. |
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe pull request adds a release-train record for version 2.57.0. It documents promotion evidence, CI and CodeQL decisions, and the observed npm registry propagation delay. ChangesRelease train documentation
Estimated code review effort: 1 (Trivial) | ~3 minutes Change: Other ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
github-actions
Bot
added
the
documentation
|
Maintainer integration into |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f9b0a16774
ℹ️ 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".
|
|
||
| | Step | What happened | Evidence | | ||
| | --- | --- | --- | | ||
| | Freeze the candidate | `1831193294` on `dev`, `package.json` 2.57.0 | Cross-platform CI push run `35131181996`: success across the full matrix, all six Windows shards included. First green `dev` run since `35091966777`. | |
There was a problem hiding this comment.
This records 1831193294 as the frozen candidate, but 010_dev_green.md:38-39 still identifies 2b19983bfd as the release candidate and explicitly claims that this file contains its successful exact-SHA rerun. Because 1831193294 is two commits later and includes the timeout adjustment from #4830, the release audit now makes contradictory candidate and CI-evidence claims; update wp2 to document the supersession and its final SHA/run.
Useful? React with 👍 / 👎.
리뷰 · 우선순위 76 / 80설명이 PR은 2.57.0 릴리스 트레인의 닫는 문서다. 지금 문서 본문은 세 덩어리다. 첫째, 후보 freeze( 현재 라인 수준의 제품 버그는 없다. 남는 건 문서 정확도·유지 비용·다음 컷에 남길 메모 정도다.
경로 메인테이너의 판단이 필요한 지점
너의 추천 이 댓글은 grok-bot이 작성했습니다 |
1 participant
What this is
The closing document of the 2.57.0 release train: every step with its SHA, run id and conclusion,
the two judgment calls the cut required, and the registry state as it stands.
Documentation only — no product code, no tests, no workflows.
Why the last section matters
npm publishsucceeded with a signed provenance statement, and the workflow's ownPost-publish registry smokestep then failed to confirm the version in six bounded reads andrecorded
verification=pending. Its summary says to inspect the registry before announcingavailability and not to republish. This document records that state explicitly so the next person
reading it does not mistake a propagation delay for a failed release and cut 2.57.1.
Validation
No local suite, typecheck, build or install was run. Every claim names a run id, a job id, a SHA,
or a URL.
Summary by CodeRabbit