when newline conf changes from one release to the other, we currently let bin/add-new-release.sh generate a new .buildspec without update, then have a failed build, then do manual research
recent exemple: https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/content/org/apache/maven/surefire/README.md with #2125
automating .buildspec update based on new artifact detection would ease that pain
when newline conf changes from one release to the other, we currently let
bin/add-new-release.shgenerate a new.buildspecwithout update, then have a failed build, then do manual researchrecent exemple: https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/content/org/apache/maven/surefire/README.md with #2125
automating
.buildspecupdate based on new artifact detection would ease that pain