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

antsibull_changelog skips certain fragments #46

Closed
NilashishC opened this issue Nov 26, 2020 · 1 comment · Fixed by #47
Closed

antsibull_changelog skips certain fragments #46

NilashishC opened this issue Nov 26, 2020 · 1 comment · Fixed by #47

Comments

@NilashishC
Copy link

SUMMARY

While generating the changelog for a release, if there's a fragment with the same name as a fragment from a previous release, the current one isn't picked up.

ISSUE TYPE
  • Bug Report
VERSION
Name: antsibull-changelog
Version: 0.7.0
Summary: Changelog tool for Ansible-base and Ansible collections
Home-page: https://github.com/ansible-community/antsibull-changelog
Author: Felix Fontein
Author-email: felix@fontein.de
License: GPL-3.0-or-later
Location: /Users/nchakrab/venvs/dev/lib/python3.6/site-packages
Requires: semantic-version, rstcheck, packaging, PyYAML, docutils
Required-by: antsibull
STEPS TO REPRODUCE
  • Add a changelog fragment with the same name as fragment from previous release (which is not present now but has an entry in changelog.yaml).
  • Run antsibull-changelog release --version x.x.x
EXPECTED RESULTS

The current fragment is read and added in the correct sections in both CHANGELOG.rst and changelog.yaml

ACTUAL RESULTS

The current fragment with the same name as fragment from previous release is not read.

@felixfontein
Copy link
Collaborator

Will be resolved by #47.

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

Successfully merging a pull request may close this issue.

2 participants