dbc Release Process

Since we rely on goreleaser and automation for managing our releases, the actual release process is exceptionally easy:

$ git tag -a v0.2.0 -m "dbc v0.2.0 Release"
$ git push --tags

For pre-releases, we utilize tags such as alpha and beta. e.g., to do a pre-release, you use the following command:

$ git tag -a v0.2.0-beta1 -m "dbc v0.2.0 Beta Release"
$ git push --tags

The automation will take over from the tag being pushed.

Release Checklist

Before creating and pushing the tags, please consult the following checklist of steps:

Are the docs up to date with any new/changed features?
Are the auto-complete scripts up to date with changes to the options and subcommands?
If any new features or CLI subcommands/flags have been added in this release, add {{ since_version('v1.2.3') }} tags in the docs where appropriate
Is the llmstxt plugin config in sync with the main nav in mkdocs.yml?
(Before promoting a pre-release) Has the pre-release been manually tested?
After pushing the tag, you will need to approve the deployment on the Actions tab of the repo.

Once the above checklist is completed, just push the new tag to kick off the release process.