Latest CHANGELOG.md starts at `## 2.11...` and earlier

[BrianInglis]

Describe the bug

CHANGELOG.md distributed in tarball or cloned from repo starts at ## 2.11 ...

To reproduce

View CHANGELOG.md in the release tarball, on GH, or in a cloned repo

Expected behavior

CHANGELOG.md starts at ## 2.13 ...

Versions (please complete the following information)

2.13.0

Additional context

Looking at the CHANGELOG.md history, some code or JSON data was included in commit messages after 2.11 - by GH release bot? - and some tool in the chain does not like how it is used - JS or python or git shellcode?

See also rendering of PR #1094 magenta sections "Unable to render expression." with embedded shell expressions that GH or its MD renderer seems to want to evaluate! [A few thousand fake repos with those expressions could cause a fuss!] ;^>

[scop]

Looks like the 2.12.0 and 2.13.0 entries ended up after 2.11 in CHANGELOG.md, and https://github.com/scop/bash-completion/pull/1155 show the same about to happen for 2.14.0. I'll fix up the order manually, let's see if that makes a difference in the open PR.

Will try to have a look at the other findings later.

[scop]

With https://github.com/scop/bash-completion/commit/c48854850f702604aeb600ae496fb6b2eb840f8e release-please now puts 2.14.0 entries between 2.12.0 and 2.13.0 :/ (#1155)