From bd0f943a8e0b144910991113963f1dfddb5ee024 Mon Sep 17 00:00:00 2001 From: Pete Gadomski Date: Mon, 6 Mar 2023 14:10:13 -0700 Subject: [PATCH 1/2] docs: fix up releasing docs --- RELEASING.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/RELEASING.md b/RELEASING.md index 4e128b7c1..c3d14ec4a 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -23,7 +23,8 @@ This is a checklist to use when releasing a new PySTAC version. 8. Once approved, merge the PR. 9. Once the PR is merged, create a tag with the version name, e.g. `vX.Y.Z`. Prefer a signed tag, if possible. - Push the tag to Github to trigger the PyPI publish. + Push the tag to Github. 10. Use the tag to finish your release notes, and publish those. The "auto generate" feature is your friend, here. + When the release is published, this will trigger the build and release on PyPI. 11. Announced the release in [Gitter](https://matrix.to/#/#SpatioTemporal-Asset-Catalog_python:gitter.im) and on any relevant social media. From e130e3cb749a62222b6556fdffd15deee12836f5 Mon Sep 17 00:00:00 2001 From: Pete Gadomski Date: Mon, 6 Mar 2023 14:25:41 -0700 Subject: [PATCH 2/2] ci: switch to published, not created, for release --- .github/workflows/release.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 841424785..d2c97d41a 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -3,7 +3,7 @@ name: Release on: release: types: - - created + - published jobs: release: