Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix up releasing workflow and docs #1032

Merged
merged 3 commits into from
Mar 9, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/release.yml
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ name: Release
on:
release:
types:
- created
- published

jobs:
release:
Expand Down
3 changes: 2 additions & 1 deletion RELEASING.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.