Skip to content

release_checklist.md

Latest commit

 

History

History
32 lines (30 loc) · 2.18 KB

release_checklist.md

File metadata and controls

32 lines (30 loc) · 2.18 KB
Raw
name Release checklist
about Steps to take when releasing a new version (only for Oxide release team).
labels release

Release checklist

  • Update the Terraform configuration version constraints in the following files to use the version you want to release.
  • Update the following files with the version you want to release.
  • Update the github.com/oxidecomputer/oxide.go dependency to the latest release.
  • Run the acceptance tests against an environment with the same Omicron version as the Go SDK version the provider is on.
  • Generate the CHANGELOG.md file.
    • Run make changelog
    • Add the date of the release to the title
  • Release the new version draft by running make tag.
  • Verify the release is correct, it's being created from the correct tag on GitHub, and make the release live. Note: Terraform registry will silently fail to publish if the tag is incorrect, and GitHub has a habit of messing up the tag a release is created from on occasion.
  • Verify the release is available on the Terraform provider registry.
  • If this is a major or minor release, create a new MAJOR.MINOR branch from the newly created tag.
  • Update the following files with the upcoming version.
  • Create new changelog file in .changelog/ on the relevant branches.