fix: upgrade node and package versions (#264)

<!-- markdownlint-disable-next-line first-line-heading -->
## Description

<!-- Describe your changes in detail. -->
Update docs to make it clear on the commit message requirement. Allow
latest release to happen with node and package upgrades.

## Context

<!-- Why is this change required? What problem does it solve? -->

## Type of changes

<!-- What types of changes does your code introduce? Put an `x` in all
the boxes that apply. -->

- [x] Refactoring (non-breaking change)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would change existing
functionality)
- [ ] Bug fix (non-breaking change which fixes an issue)

## Checklist

<!-- Go over all the following points, and put an `x` in all the boxes
that apply. -->

- [ ] I am familiar with the [contributing
guidelines](../docs/CONTRIBUTING.md)
- [ ] I have followed the code style of the project
- [ ] I have added tests to cover my changes
- [ ] I have updated the documentation accordingly
- [ ] This PR is a result of pair or mob programming

---

## Sensitive Information Declaration

To ensure the utmost confidentiality and protect your and others
privacy, we kindly ask you to NOT including [PII (Personal Identifiable
Information) / PID (Personal Identifiable
Data)](https://digital.nhs.uk/data-and-information/keeping-data-safe-and-benefitting-the-public)
or any other sensitive data in this PR (Pull Request) and the codebase
changes. We will remove any PR that do contain any sensitive
information. We really appreciate your cooperation in this matter.

- [ ] I confirm that neither PII/PID nor sensitive data are included in
this PR and the codebase changes.

Author: susana-zhou1

docs/developer-guides/Release_Process.md

@@ -6,7 +6,7 @@ For details on securely signing release commits and using a GitHub App token, se
 
 ## Overview
 
-1. Developers raise pull requests with source changes only (no `dist/` directory committed).
+1. Developers raise pull requests with source changes only (no `dist/` directory committed). Commits should follow the conventional commit format under [Conventional Commit Examples](#conventional-commit-examples)
 2. The pull request workflow performs a semantic-release dry run to preview the next version.
 3. Once changes are merged to `main`, the publish workflow: