Update release.md [cd build]

Signed-off-by: Arthit Suriyawongkul <arthit@gmail.com>

Author: bact

CHANGELOG.md

@@ -1,6 +1,7 @@
 ---
-SPDX-FileCopyrightText: 2024 PyThaiNLP Project
-SPDX-License-Identifier: Apache-2.0
+SPDX-FileCopyrightText: 2025 PyThaiNLP Project
+SPDX-FileType: DOCUMENTATION
+SPDX-License-Identifier: CC0-1.0
 ---
 
 # Changelog

CONTRIBUTING.md

@@ -1,3 +1,9 @@
+---
+SPDX-FileCopyrightText: 2025 PyThaiNLP Project
+SPDX-FileType: DOCUMENTATION
+SPDX-License-Identifier: CC0-1.0
+---
+
 # Contributing to PyThaiNLP
 
 Hi! Thanks for your interest in contributing to [PyThaiNLP](https://github.com/PyThaiNLP/pythainlp).

release.md

@@ -1,8 +1,16 @@
+---
+SPDX-FileCopyrightText: 2025 PyThaiNLP Project
+SPDX-FileType: DOCUMENTATION
+SPDX-License-Identifier: CC0-1.0
+---
+
 # How to cut a new release
 
 0. Check if the package can be built properly.
    Include "[cd build]" in the commit message to trigger wheel building.
-1. This project follows [semantic versioning][semver].
+1. Update `CHANGELOG.md` with a short summary of important changes since
+   the previous release. For example, deprecation or termination of support.
+2. This project follows [semantic versioning][semver].
    Ensure the version and release date fields (if any) in these files
    have been updated to the version of the new planned release:
     - `codemeta.json`
@@ -13,17 +21,16 @@
     - `CITATION.cff`
     - `README.md`
     - `README.TH.md`
-2. Navigate to the [releases page][releases] and click the
+3. Navigate to the [releases page][releases] and click the
    "Draft a new release" button.
    Only project maintainers are able to perform this step.
-3. Then enter the new tag in the "Choose a tag" box.
+4. Then enter the new tag in the "Choose a tag" box.
    The tag should begin with "v", as in, for instance, `v5.0.1`.
-4. The release title should be the same as the new version tag.
+5. The release title should be the same as the new version tag.
    For instance, the title could be `v5.0.1`.
-5. Add a short summary of important changes in this release.
-   For example, deprecation or termination of support.
-   This should be similar to what have been logged in `CHANGELOG.md`.
-6. Then click the "Generate release notes" button.
+6. Add a short summary of important changes in this release.
+   _This should be similar to what have been logged in `CHANGELOG.md`._
+   Then click the "Generate release notes" button.
 7. You can optionally include any particular thank-you's to contributors or
    reviewers in a note at the bottom of the release.
 8. You can then click "Publish release" button.