Antsibull-changelog in non-collection projects

Project Discussions
,
1

Hey @felixfontein (and all), I’ve been looking at adding changelogs to a non-collection project with antsibull-changelog. I thought it might be good to ask here in the forum instead of in the Antsibull Tools channel on Matrix.

Here is the config I used:

is_other_project: true
use_semantic_versioning: false
title: Amazing project title
sanitize_changelog: true
trivial_section_name: trivial

I initialized with antsibull-changelog init --is-other-project ., created a few test fragments, and ran two releases:

  1. antsibull-changelog release --version 2026.05.0
  2. Added another fragment and then antsibull-changelog release --version 2026.05.1

Everything seems great. I also looked at the ansible-community GitHub org and found that the antsibull-* tooling projects use is_other_project: true.

So my question is pretty basic. Are there any gotchas or considerations for using antsibull-changelog with non-collection projects? I guess everything is fine but would appreciate any insights if I’m overlooking something.

Another thing I’m curious about is that I see there’s a antsibull-changelog lint option for validating fragments but wondering if there’s any tooling for checking that PRs contain fragments?

Thanks!

1 Like
2

For me it has been working pretty well so far. I’m not aware of gotchas.

There’s no tooling I know for checking that PRs contain fragments. I know that some collections do this, but none that I maintain.

2 Likes