opentofu/setup-opentofu

Automate release process

kislerdm opened this issue · 4 comments

kislerdm commented

Problem

The release artefacts were prepared manually in a local env, this is highly error prone.

Proposed Solution

Define a release github workflow. See the one hashicorp use as an example.

Followup on #2 (comment).

Ant0wan commented

@kislerdm Do you still need a hand on this issue ? My pleasure to help on this if needed.

kislerdm commented

@Ant0wan Hey Antoine, thank you for your kind offer! Your contribution would be more than welcomed!

I reckon we shall consider covering the following acceptance criteria for the release workflow:

  • It builds all required artifacts (we rely in pre-commit and it's recommended for js/ts github actions)
  • It does only run if the test workflows succeeded
  • It uses CHANGELOG content as a human readable release description
  • It covers the offset for major tag, i.e. the note

WDYT?

Ant0wan commented

@kislerdm

  • What specific artifacts are required to be uploaded, and where should they be uploaded to?
  • Which tool would you prefer to use for generating the changelog? Is the default GitHub changelog not satisfactory for your needs?

Regarding my latest commit, it incorporates the following changes:

  • It will now exclusively execute if the test workflows have successfully completed.
  • There may have been a misunderstanding, but it appears to address the major tag offset.
kislerdm commented

Hey @Ant0wan

Which tool would you prefer to use for generating the changelog?

I'm a proponent of the rule "changelings are for humans" (please find details). WDYT about using the content of the CHANGELOG.md to populate the release notes?