Add automated release pipeline

[guenp]

See packaging guide for setup instructions on PyPI:

Go to https://pypi.org/manage/account/publishing/.

Fill in the name you wish to publish your new PyPI project under (the name value in your setup.cfg or pyproject.toml), the GitHub repository owner’s name (org or user), and repository name, and the name of the release workflow file under the .github/ folder, see Creating a workflow definition. Finally, add the name of the GitHub Environment (pypi) we’re going set up under your repository. Register the trusted publisher.

Your “pending” publisher is now ready for their first use and will create your project automatically once you use them for the first time.

This was tested on TestPyPI (see: https://test.pypi.org/project/dbt-duckdb/)

[guenp]

The pipeline currently triggers when you push a semver tag but still requires you to update the version manually, we can implement automated versioning e.g. with versioningit in a separate PR. Let me know what you think

[guenp]

Ah I missed this earlier, looks like if we want to push an automatic release as well we need to set up a github token.

[jwills]

okay cool-- so I need to set that up, somehow. It's int he docs you linked to?

[guenp]

Oh good point, no it's not. I'll open a PR to the packaging docs page to add a note.

I looked it up and looks like the token itself is automatically generated by GitHub, see docs.
However we would need to set the permissions so it has contents:write access, see docs.
See also this post on stackoverflow.

To change the permissions go to https://github.com/duckdb/dbt-duckdb/settings/actions and scroll down to "Workflow permissions" and choose "Read and write permissions".

Alternatively you can create a Personal Access Token and use that instead of the GITHUB_TOKEN.

If none of this sparks joy we can take this part out and just manually post release notes

[guenp]

Also just realized that right now it posts empty release notes (--notes "")
Maybe a nice follow up PR could be to add automated release notes?
See: https://github.com/marketplace/actions/release-notes-generator#use-github-action

Edit: nvm I can just use --generate-notes