Support release branches

[mdesmet]

Describe the feature

• CREATE BRANCH for each minor release based on the latest patch tag for each minor
• CREATE CHANGELOG on master branch that refers each minor version latest changeling on the relevant release branch
• Make every release compatible with version bump (standardised setup.py and version.py)
• Ensure master + release branches are tested on push
• Ensure master + release branches are tested on pull request

Describe alternatives you've considered

No response

Who will benefit?

No response

Are you willing to submit PR?

• Yes I am willing to submit a PR!

[damian3031]

Currently dbt trino release workflow uses this github action. Unfortunately, this github action sets every release as latest, so while making backport and releasing 1.0.4, it would be set as latest github release. There is make_latest github API parameter which could be set to false, to avoid setting backported releases as latest ones. Unfortunately, this GH action doesn't support this parameter, and will never do, as this repository is archived.
So, it would require to manually change which version is latest after releasing backported version, or some refactor in a release workflow.

There is another gh action which I used in PyTrino release workflow, which has pending PR for addition of this parameter, maybe it could be used instead after adding this make_latest option there.

[mdesmet]

Unfortunately, this GH action doesn't support this parameter, and will never do, as this repository is archived.

So, it would require to manually change which version is latest after releasing backported version, or some refactor in a release workflow.

As discussed offline, let's not worry about this.