Skip to content

Latest commit

 

History

History
30 lines (26 loc) · 1.32 KB

RELEASE.md

File metadata and controls

30 lines (26 loc) · 1.32 KB

Release Flow

Since the migration to the Terraform registry, this repository's maintainers now have the ability to self-publish Terraform GitHub provider releases. This process leverages Github Actions and goreleaser to build, sign, and upload provider binaries to a Github release.

The release flow is as follows:

  1. Create a CHANGELOG entry for the release using the following format:
    ## x.y.z (release date)
    
    ## ENHANCEMENTS:
    ...
    
    ## BUG FIXES:
    ...
  2. Tag the commit that adds the CHANGELOG entry with the release version and push:
    $ git tag x.y.z
    $ git push origin x.y.z
  3. Github Actions will trigger the release workflow which can be viewed here. After the workflow executes successfully, the Github release created in the prior step will have the relevant assets available for consumption.
  4. The new release will show up in https://registry.terraform.io/providers/integrations/github/latest for consumption by terraform 0.13.X users.
  5. For terraform 0.12.X users, the new release is available for consumption once it is present in https://releases.hashicorp.com/terraform-provider-github/.