Why did npx commit-and-tag-version miss the most recent commit?

[ramonrails]

I have the following commits in a git repo

* b834d91 - (HEAD -> main, tag: v1.3.1) chore(release): 1.3.1
* 5edaef6 - refactor(utilities): utility scripts each moved to their seperate scripts inside subfolder
* 6b76a6c - fix(git): app-tag script skips the run when no relevant changes are detected
* 8b21c9d - (tag: v1.3.0) chore(release): 1.3.0
* e27d1d1 - feat(ansible): ansible moved to devops folder
* 8b308bf - (tag: v1.2.3) chore(release): 1.2.3
* 240d0cf - (tag: v1.2.2) chore(release): 1.2.2
* d07d01e - (tag: v1.2.1) chore(release): 1.2.1
* db633c8 - (tag: v1.2.0) chore(release): 1.2.0
* a0bb9b8 - feat(ansible): ansible script moved to devops/ansible
* 8d41f0a - feat: playbook separated into file and converted to a function
* c6096a7 - (tag: v1.1.1) chore(release): 1.1.1
* c26875d - (tag: v1.1.0) chore(release): 1.1.0
* 3737bbf - feat: ansible playbook script converted to a function
* 5639760 - feat: disk_usage command added based on dua-cli

But my changelog does not show the top most commit in the v1.3.1 run.

* 5edaef6 - refactor(utilities): utility scripts each moved to their seperate scripts inside subfolder

I just ran npx commit-and-tag-version
What did I miss?

The CHANGELOG.md file is the following

# Changelog

All notable changes to this project will be documented in this file. See [commit-and-tag-version](...) for commit guidelines.

## [1.3.1](...) (2024-02-28)


### Bug Fixes

* **git:** app-tag script skips the run when no relevant changes are detected ([6b76a6c](...))

## [1.3.0](...) (2024-02-28)


### Features

* **ansible:** ansible moved to devops folder ([e27d1d1](...))

## [1.2.3](...) (2024-02-28)

## [1.2.2](...) (2024-02-28)

## [1.2.1](...) (2024-02-28)

## [1.2.0](...) (2024-02-28)


### Features

* **ansible:** ansible script moved to devops/ansible ([a0bb9b8](...))
* playbook separated into file and converted to a function ([8d41f0a](...))

## [1.1.1](...) (2024-02-28)

## 1.1.0 (2024-02-28)


### Features

* ansible playbook script converted to a function ([3737bbf](...))
* disk_usage command added based on dua-cli ([5639760](...))

[ramonrails]

This behaviour is happening consistently.
Is someone else experiencing this? Or, did I really do something incorrect?

[TimothyJones]

On mobile so can’t link you, but refactor isn’t shown by default, only user facing changes (fix and feat) and anything marked as breaking are shown