search

collective / zestreleaser.towncrier

GNU General Public License v2.0
1 stars 1 forks source link

Call bumpversion? #5

Open mauritsvanrees opened 6 years ago

mauritsvanrees commented 6 years ago

When there is a news/X.feature file, we could automatically call bumpversion --feature, and with news/.Y.breaking we could call bumpversion --breaking. We would need to read pyproject.toml then, to look for [tool.towncrier] directory = "news". bumpversion would ask you to confirm, so you can still back out.

gforcada commented 6 years ago

bumpversion comes from... which package? :thinking: EDIT: sorry I was so lazy to google: https://pypi.org/project/bumpversion/ then this is yet another dependency right? I see that it does create tags and commits, should that be rather then integrated with zest.releaser directly? As they seem to overlap...

mauritsvanrees commented 6 years ago

Nope. The bumpversion command I am talking about is part of zest.releaser. :-) See https://zestreleaser.readthedocs.io/en/latest/overview.html?highlight=bumpversion near the bottom. And the bumpversion file in zest.releaser.

gforcada commented 5 years ago

While that is not being integrated, an easy and quick solution would be to print the files on news/ folder before the release number version. That would help a lot.

While I wait for that I use a split terminal to see what's on the news entries and the fullrelease command :smile: