fix: add requirements to update the changelog

Author: ChengShi-1

.github/CONTRIBUTING.md

@@ -74,9 +74,10 @@ guidelines to help:
 
 1. **Solve a problem** – Features are great, but even better is cleaning-up and fixing issues in the code that you discover.
 2. **Write tests** – This helps preserve functionality as the codebase grows and demonstrates how your change affects the code.
-3. **Write documentation** – We have a [README] that always needs updating.
-4. **Small > big** – Better to have a few small pull requests that address specific parts of the code, than one big pull request that jumps all over.
-5. **Comply with Coding Standards** – See next section.
+3. **Update the changelog** – All PRs should include a changelog entry. (see [Changelog Guidelines](#changelog-guidelines) below).
+4. **Write documentation** – We have a [README] that always needs updating.
+5. **Small > big** – Better to have a few small pull requests that address specific parts of the code, than one big pull request that jumps all over.
+6. **Comply with Coding Standards** – See next section.
 
 ### How to start
 
@@ -107,6 +108,8 @@ When contributing to this project, it's important to document your changes in th
 
 ### When to Add Changelog Entries
 
+**Every pull request should include a changelog entry**
+
 Add a changelog entry for changes, including:
 
 - **Added**: New features, components, or functionality

docs/making-releases.md

@@ -42,6 +42,8 @@ This command will update the version in the `package.json` and `package-lock.jso
 
 ## Update the Changelog
 
+**Note**: Contributors should have already added their changes to the `[Unreleased]` section as part of their pull requests (see [CONTRIBUTING.md](../.github/CONTRIBUTING.md#changelog-guidelines) for details).
+
 Before releasing, ensure the changelog is properly prepared:
 
 1. **Review the [Unreleased] section** in `CHANGELOG.md` and `packages/design-system/CHANGELOG.md`