Ready

mirendev/runtime#1429

This is ready to merge. It changes only the docs: one 11-line section added to docs/docs/changelog.md, with no code touched.

The new ## v0.17.3 section is in the right spot, after ## Unreleased and before ## v0.17.2, with the same --- separators and **Bug Fixes** / bold-title / PR-link format as its neighbours. The Unreleased entries for #1419 and #1378 stay under Unreleased, which is correct because they didn't ship in 0.17.3. docs/docs/changelog.md is the only Markdown file in the repo that has release sections, so no second changelog needs the same addition. The vmagent entry reads cleanly after the eMudhra notes in v0.17.1 and v0.17.2, and it doesn't contradict either of them.

You describe the text as copied verbatim from the tag. I can't compare it against the tag from here, but nothing in it looks out of place for this file. A docs-only carry-over like this has no runtime impact, so I don't think it needs a separate human code review.


Verdict: ready

Data

{
  "owner": "mirendev",
  "repo": "runtime",
  "number": 1429,
  "verdict": "ready",
  "approve": true,
  "event": "approve",
  "summary": "This is ready to merge. It changes only the docs: one 11-line section added to `docs/docs/changelog.md`, with no code touched.\n\nThe new `## v0.17.3` section is in the right spot, after `## Unreleased` and before `## v0.17.2`, with the same `---` separators and `**Bug Fixes**` / bold-title / PR-link format as its neighbours. The Unreleased entries for #1419 and #1378 stay under Unreleased, which is correct because they didn't ship in 0.17.3. `docs/docs/changelog.md` is the only Markdown file in the repo that has release sections, so no second changelog needs the same addition. The vmagent entry reads cleanly after the eMudhra notes in v0.17.1 and v0.17.2, and it doesn't contradict either of them.\n\nYou describe the text as copied verbatim from the tag. I can't compare it against the tag from here, but nothing in it looks out of place for this file. A docs-only carry-over like this has no runtime impact, so I don't think it needs a separate human code review.",
  "posted_to_pr": true,
  "draft": true,
  "head_sha": "b35e02637737e2bfe3ad513708810262468022c5"
}