Closed tatiana closed 1 year ago
Patch coverage: 100.00
% and no project coverage change.
Comparison is base (
2a19f29
) 78.47% compared to head (dcd8a2d
) 78.47%.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.
Change GitHub Actions workflow to release using Hatch instead of Twine so the packages created are valid.
Although the template repo astro-providers-template used hatch for package management, the astro-provider-databricks CI was configured to use Twine to release to PyPI. This PR aims to make package management tools consistent usage consistent.
We also had to yank a release created using the previous Github Actions workflow. This particular version was built/released using Github actions. A possible explanation for the issue is that we're using dynamic versioning and other things done differently in Twine.
How the CI workflow looks like when triggered from a Pull Request (publishing to PyPI is skipped):
This is an example of a package successfully published to PyPI using Github actions: https://github.com/astronomer/astro-provider-databricks/actions/runs/4947422468 https://pypi.org/project/astro-provider-databricks/0.1.3a2/