Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
BrianInglis opened this issue Apr 29, 2024 · 2 comments
Open

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

BrianInglis opened this issue Apr 29, 2024 · 2 comments

Comments

@BrianInglis
Copy link

BrianInglis commented Apr 29, 2024

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
Copy link
Owner

scop commented May 2, 2024

Looks like the 2.12.0 and 2.13.0 entries ended up after 2.11 in CHANGELOG.md, and #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 added a commit that referenced this issue May 2, 2024
@scop
Copy link
Owner

scop commented May 2, 2024

With c488548 release-please now puts 2.14.0 entries between 2.12.0 and 2.13.0 :/ (#1155)

scop added a commit that referenced this issue May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants