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

Clean up changelog.txt from duplicate entries #68834

Closed
2 of 6 tasks
afercia opened this issue Jan 22, 2025 · 0 comments · Fixed by #68836
Closed
2 of 6 tasks

Clean up changelog.txt from duplicate entries #68834

afercia opened this issue Jan 22, 2025 · 0 comments · Fixed by #68836
Labels
[Type] Bug An existing feature does not function as intended [Type] Build Tooling Issues or PRs related to build tooling

Comments

@afercia
Copy link
Contributor

afercia commented Jan 22, 2025

Description

Splitting this out from a conversation on Slack.

It appears in the changelog.txt file the entries for the = 19.7.0 = release are duplicated. Not sure about other dupplicates.

GitHub can't show such a long file but here's the referenced section, starting at line 1298 and line 1837:

The entries have been added in two separate autogenerated commits:

Step-by-step reproduction instructions

N/A

Screenshots, screen recording, code snippet

No response

Environment info

No response

Please confirm that you have searched existing issues in the repo.

  • Yes

Please confirm that you have tested with all plugins deactivated except Gutenberg.

  • Yes

Please confirm which theme type you used for testing.

  • Block
  • Classic
  • Hybrid (e.g. classic with theme.json)
  • Not sure
@afercia afercia added [Type] Bug An existing feature does not function as intended [Type] Build Tooling Issues or PRs related to build tooling labels Jan 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Type] Bug An existing feature does not function as intended [Type] Build Tooling Issues or PRs related to build tooling
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant