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

Feature/pypi workflow #42

Merged
merged 2 commits into from
Jun 2, 2022

Conversation

SorooshMani-NOAA
Copy link
Contributor

Add workflow to automatically release pyschism on PyPI on publish tag.

@SorooshMani-NOAA
Copy link
Contributor Author

This addresses #23 (comment)

@cuill, in order for this to work, you or another admin developer needs to create a PyPI token (https://pypi.org/help/#apitoken) and add it to the repository secrets (GH documentation) with the name PYPI_TOKEN.

Then every time someone creates a release tag, described here, on the repo with a proper tag (e.g. v0.1.1), the workflow will run and automatically uploads the build to PyPI.

Note that I excluded python 3.6 from the build because it had some issues with netcdf-flattener when I tried to build it.

@SorooshMani-NOAA
Copy link
Contributor Author

@cuill if everything looks fine with this, when you set-up the PyPI token, I appreciate it if you could also create a release tag (e.g. v0.1.1 or anything you see fit) so that pyschism is published on PyPI. I have pyschism as an upstream dependency in coupledmodeldriver and I need pyschism release to be able to release next version of CoupledModelDriver

@jreniel jreniel merged commit 01b03f1 into schism-dev:main Jun 2, 2022
mansurjisan pushed a commit to mansurjisan/pyschism that referenced this pull request Aug 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants