DX-2556: Switch to release drafter #4302
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
A ton of BLT code exists solely to manage releases. This is a pain to maintain, and we are also using deprecated Github API methods that would require a fair amount of effort to fix.
Proposed changes
Instead of manually rolling releases, switch to the Release Drafter app that will automatically generate new releases, release notes, and version numbers / tags.
This introduces a dependency on Composer 2 to return version number since we need APIs available in Composer 2 to get the BLT version number (since we'll no longer be baking it into each release via a commit). I think this is acceptable because Composer 1 is now EOL and we can soon make Composer 2 mandatory (or else have a fallback way of getting version number).