Processes/workflow for releasing a new version of a dbt package

[dbeatty10]

As a maintainer of a dbt package, I want to automate the process of cutting a new release so that I can do it quickly and without worry

What topic would you like to see discussed more in-depth?

I want to learn about example processes/workflow for releasing a new version of a dbt package. Are there existing GitHub Actions or Workflows that can be reused?

Why do you think this is important?

If all the steps are manual, then it takes more time margin and mental focus to execute the process. This can lead to a release being delayed for longer than is strictly necessary.

Also, any manual steps are likely to be performed incorrectly at some point.

Are there any existing resources that you’ve seen explore this topic? What do you think they’re missing? Please share any relevant links.

An example workflow might look like this:

1. create a release branch
2. bump the version number in dbt_project.yml
3. Create the release itself

Background

Inspired by this conversation:

• https://getdbt.slack.com/archives/CU4MRJ7QB/p1649899210584679