-
Notifications
You must be signed in to change notification settings - Fork 6
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
Publish PyCIEMSS to PyPI OR start tagging releases #344
Comments
3 tasks
@fivegrant , we've now tagged our first 0.0.1 release on PyCIEMSS, and will continue to follow good semantic versioning practices with regular tagged released moving forward. This will include changes to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
TA4 is trying to ensure builds are more reproducible (Here's the issue tracking this on the PyCIEMSS Service side).
Currently, the service grabs PyCIEMSS by the revision hash, but we would ideally like to grab releases instead. Additionally, the MIRA requirement is not locked so this can cause an unexpected update downstream. Tagging PyCIEMSS and MIRA would go a long way in making sure builds are more reliable.
The text was updated successfully, but these errors were encountered: