You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We can automate the whole process of reviewing the version, that it's a tag, and that it's uploaded to PyPI with existing GitHub Actions used in multiple other projects. Here are some examples that I am aware of or worked with in the past:
Note: we must not test this with our official package in PyPI. I believe RO-Crate-py uses the test-pypi instance. It's an old service offered by PyPI so that devs can test that everything works before publishing a release. We can fork it or create a new repo, play with actions, and then once we are confident of how things work, then we schedule half-day to cut the first release (and solve any issues).
Then future releases should take between 30 and 180 seconds, I think (tests are taking 30 seconds at the moment). After this time, the package would then be available on PyPI, with the GitHub tag created, etc.
We can automate the whole process of reviewing the version, that it's a tag, and that it's uploaded to PyPI with existing GitHub Actions used in multiple other projects. Here are some examples that I am aware of or worked with in the past:
The text was updated successfully, but these errors were encountered: