docs(changelog): add release dates to version headings#401
Conversation
Add the published release date to every version heading on the user-facing changelog pages (English half-width, Chinese full-width), covering 0.2.0 through 0.9.0. Dates come from each version's published release tag. Also update the sync-changelog skill so future syncs carry the date convention forward.
|
commit: |
![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: 56546ece20
ℹ️ 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".
| Take the date from the version's published GitHub Release tag, not from when you run the sync: | ||
|
|
||
| ```bash | ||
| git log -1 --format=%cs "@moonshot-ai/kimi-code@<version>" |
There was a problem hiding this comment.
When a release is published from an annotated tag or GitHub creates/publishes the release on a different date than the tagged commit, this command records the commit’s committer date (%cs), not the GitHub Release publish date the new rule asks for. That can make future changelog syncs pass the checklist while showing the wrong ship date; use the release metadata instead, e.g. gh release view "@moonshot-ai/kimi-code@<version>" --json publishedAt, if the intended source is the published GitHub Release.
Useful? React with 👍 / 👎.
# Conflicts: # docs/en/release-notes/changelog.md # docs/zh/release-notes/changelog.md
1 participant
Problem
The user-facing changelog pages listed each release by version number only (
## 0.9.0), with no publish date. Readers couldn't tell when a version actually shipped, and the changeset-based release flow never adds dates.What changed
## 0.9.0 (2026-06-03); Chinese uses full-width, e.g.## 0.9.0（2026-06-03）. Dates come from each version's published release tag, not from sync time.sync-changelogskill so future syncs always carry the release date forward: the date-sourcing rule, the English/Chinese parenthesis styles, a verify-step check, and a common-mistakes entry.Docs- and skill-only change; no changeset needed.