Skip to content

Latest commit

 

History

History
26 lines (20 loc) · 1.43 KB

RELEASE.md

File metadata and controls

26 lines (20 loc) · 1.43 KB

dbt-utils releases

When do we release?

There's a few scenarios that might prompt a release:

Scenario Release type
Breaking changes to existing macros major
New functionality minor
Fixes to existing macros patch

Release process

  1. Begin a new release by clicking here
  2. Click "Choose a tag", then paste your version number (with no "v" in the name), then click "Create new tag: x.y.z. on publish"
    • The “Release title” will be identical to the tag name
  3. Click the "Generate release notes" button
  4. Copy and paste the generated release notes into CHANGELOG.md, commit, and merge into the main branch
  5. Click the "Publish release" button
    • This will automatically create an "Assets" section containing:
      • Source code (zip)
      • Source code (tar.gz)

Post-release

  1. Delete the automatic Zapier post (example of one intentionally not deleted) and replace it with a custom post in the #package-ecosystem channel in “The Community Slack” using the content from the tagged release notes (but replace GitHub handles with Slack handles) (example)