Skip to content

docs: clarify changelog is maintained by hand - #536

Merged
cbravobernal merged 3 commits into
WordPress:trunkfrom
faisalahammad:fix/497-doc-changelog-process
Oct 26, 2026
Merged

cbravobernal merged 3 commits into
WordPress:trunkfrom
faisalahammad:fix/497-doc-changelog-process

Conversation

@faisalahammad

@faisalahammad faisalahammad commented Aug 14, 2026 •

Copy link
Copy Markdown
Contributor

Clarify the changelog is maintained by hand and not generated by an automated tool.

The Changelog section of the release guide described the entry format (== Changelog == in readme.txt) but never stated how the changelog is actually maintained. Contributions to the repo keep asking how the changelog updates automatically, and there is no CHANGELOG.md or release automation publishing text to it.

This adds a short note to docs/contributing/releases.md stating:

  • The changelog lives in readme.txt and is written by hand by a maintainer before each release.
  • No automated tool generates the changelog text.
  • The milestone workflow only assigns merged pull requests to the next milestone to make gathering changes easier; it does not produce release notes.

Closes #497

Use of AI Tools

I used Claude Code to help draft the doc text and address review feedback. I reviewed and edited every change.

The Changelog section of the release guide described the entry format but
never said the changelog is written by hand and is not produced by an
automated tool. Add a short note stating that the changelog lives in
readme.txt, is maintained by a maintainer before each release, and that
the milestone workflow only gathers merged PRs, it does not write the
changelog text.

Closes WordPress#497
@github-actions

github-actions Bot commented Aug 14, 2026 •

Copy link
Copy Markdown

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props faisalahammad, cbravobernal.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

Comment thread docs/contributing/releases.md Outdated
- List categories as open examples: Security, Features, Fixes,
  Enhancements. Maintainers pick what fits the release.
- Update the example block to match the real readme.txt format:
  release date line, italic category headings, and dash bullets.

Addresses PR feedback.

Refs WordPress#536
@faisalahammad

Copy link
Copy Markdown
Contributor Author

@cbravobernal I updated the changelog categories and the example block in e8d4c06. Could you take another look when you have time? Thanks.

@cbravobernal
cbravobernal merged commit 31ead85 into WordPress:trunk Oct 26, 2026
20 of 21 checks passed
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