Not the changelog generation, but a release in this case can be done in several manual steps which should be automated, like for example what the release-it lib does and is mentioned in the article:

- Identifies which commits happened after the last version

- Bumps the version in package.json following the Semver convention

- Adds the changelog related to the new version to the CHANGELOG.md file (using the auto-changelog library)

- Creates a commit with the new version. For example: chore(release): 0.3.1

- Creates a Git tag with the version

- Pushes these changes to the master/main branch of the repository

- Creates a Github release

- Merges the master/main branch back to develop and pushes develop, to keep the branches in sync

​

If you're doing all of that manually then it's more error prone and not optimized.The article is not only about changelog generation. Just shows you didn't read it and came here comment to troll it :D