Publish to PyPI

[edgarrmondragon]

Tasks

Preview Give feedback

1. Set up trusted publisher on PyPI
2. Set up pypi environment in this GitHub repo, with some permissions
3. Use VCS versioning: chore: Use poetry-dynamic-versioning #68
4. Add a build + release workflow: ci: Add release workflow #71
5. Publish: https://pypi.org/project/meltano-dbt-ext/0.3.0/
6. Update the Hub: Use meltano-dbt-ext hub#1815

[edgarrmondragon]

First part is done:

(excuse the Spanglish UI)

[edgarrmondragon]

[edgarrmondragon]

PyPI doesn't like our package name:

* `invalid-payload`: The name 'dbt-ext' is too similar to an existing project. See https://pypi.org/help/#project-name for more information.

https://github.com/meltano/dbt-ext/actions/runs/10201267503/job/28222731657

It probably thinks we're trying to typo-squat some other dbt-related package 😅.

Opinions on renaming the package meltano-dbt-ext? The repo would keep the same name, so git refs in any pip_url would continue working, but when we switch them to use the package name it'd be meltano-dbt-ext instead of dbt-ext.

We could also open an issue in https://github.com/pypi/support, but that seems to be too slow of a process and I don't think we're married to dbt-ext as the PyPI package name.

Thoughts @meltano/engineering?

[WillDaSilva]

That's mildly frustrating, but also a natural consequence of there being a shared global namespace on PyPI.

I support renaming the package to meltano-dbt-ext. Normally for something like this I'd recommend a major version bump just to be safe, but in this case we're still using version 0 as the major version, wherein breaking changes are permitted, so it doesn't really matter.

[edgarrmondragon]

PR to rename the package: #73

[edgarrmondragon]

All done here