Always lint before releasing

[felixfontein]

Fixes #65.

[codecov]

Codecov Report

Merging #67 (eb3e967) into main (ec7f6ce) will increase coverage by 0.02%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #67      +/-   ##
==========================================
+ Coverage   88.96%   88.98%   +0.02%     
==========================================
  Files          16       16              
  Lines        2021     2025       +4     
  Branches      505      506       +1     
==========================================
+ Hits         1798     1802       +4     
- Misses        138      141       +3     
+ Partials       85       82       -3     

Impacted Files	Coverage Δ
antsibull_changelog/cli.py	74.91% <100.00%> (+0.36%)	⬆️
antsibull_changelog/yaml.py	84.21% <0.00%> (-15.79%)	⬇️
antsibull_changelog/fragment.py	92.64% <0.00%> (+2.20%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ec7f6ce...eb3e967. Read the comment docs.

[dmsimard]

Thanks @felixfontein ! Do you think this could have adverse effects on release changelogs that have already been generated without first being linted ?

[felixfontein]

I think the main downside is that releasing will be a bit slower (well, most time is still used for collection module/plugin version_added fields), and that it's no longer possible to insert invalid fragments into a release this way. Which I think is a good thing.

[felixfontein]

(Also this PR only lints the changelog fragments that haven't been integrated into the changelog yet, and will be integrated by the release command.)