Repository navigation
Be able to configure the filename for version in .changes/ folder #776
Description
Activity
Hmm, it does seem like you are able to change every part of that file name except that. Do you just not like the v prefix or does it affect something?
Nothing major but it does create some kind of confusion between the file name and the content of the changelog where the v prefix can be dropped.
It’s a nice to have really but doesn’t seem crazy to implement either
☺️ Reacted by RonnieYea, I may have done a little work in the v2 config structure around this. Just trying to think of the best config option here. I'm torn between a simple bool to enable or disable the prefix or to just support another template value.
I would be happy with either of them but maybe having a full template option would be better in terms of flexibility?
I’m thinking about a filename template in the same fashion as the change template worksReacted by RonnieI would be happy with either of them but maybe having a full template option would be better in terms of flexibility?
I’m thinking about a filename template in the same fashion as the change template worksI agree I think that style works better
Reacted by Jonathan Liuti- linked a pull request that will close this issueOption to specify the generated release notes file name #835
on Nov 22, 2025
Is your feature request related to a problem? Please describe.
I want to use versions without prefixes.
It's possible to act on that in multiple places of changie but not to generate the proper file name in the
.changesfolder after runningchangie batch, it will always include thevprefix.e.g:
Describe the solution you'd like
Change the line at
changie/cmd/batch.go
Line 228 in 5c067bd
so that
data.Versioncan be switched todata.VersionNoPrefixbased on some configuration.Describe alternatives you've considered
Not making use of automatic versioning when using
changie batchbut this is a bit sad.Let me know if you think it's a meaningful addition and how you would approach it.
Cheers!