Repository navigation
ci: publish v* releases to PyPI by trusted publishing - #90
Merged
Merged
Conversation
…un; release checklist
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #90 +/- ##
=======================================
Coverage 92.81% 92.81%
=======================================
Files 32 32
Lines 4357 4357
=======================================
Hits 4044 4044
Misses 313 313 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary: Adds PyPI publishing for code releases. Publishing a GitHub release whose tag is
v*(pre-releases such asv0.2.0rc1included) builds the package withuv buildand uploads it to PyPI by trusted publishing. Data releases (catalog-*,primers-*,tech-primers-*) never publish.Changes:
.github/workflows/release.yaml: the scverse cookiecutter workflow (scverse/cookiecutter-scverse@f46993f), withfetch-depth: 0, environmentpypiand the same pinned actions.if: github.event_name == 'release' && startsWith(github.event.release.tag_name, 'v')keeps catalog releases from publishing.testpypi). It runs only from "Run workflow" on av*tag, as a dry run before the first PyPI release..github/RELEASING.md: a short checklist.SUPPORTED_CATALOG_SCHEMAcovers the newest catalog'scatalog_schema_version(both are 3 today).Before the first release: the pending trusted publishers for
spatialdata-dbhave to exist on PyPI (environmentpypi) and TestPyPI (environmenttestpypi). The name is free on both today.Tests: in a clone of main with the tags
v0.2.0rc1andcatalog-2099-01-01,uv buildproducedspatialdata_db-0.2.0rc1.tar.gzand-py3-none-any.whl, so hatch-vcs takes the version from thev*tag only.