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

Tag/Publish releases of PyCIEMSS library #35

Closed
2 of 3 tasks
fivegrant opened this issue Aug 11, 2023 · 0 comments · Fixed by #40
Closed
2 of 3 tasks

Tag/Publish releases of PyCIEMSS library #35

fivegrant opened this issue Aug 11, 2023 · 0 comments · Fixed by #40
Assignees

Comments

@fivegrant
Copy link
Collaborator

fivegrant commented Aug 11, 2023

Currently, we have to specify the exact commit hash for the PyCIEMSS version we want to install. This is confusing from the dev perspective and could cause issues with updates down the line. PyCIEMSS (and ideally MIRA) need to start versioning so we can declare definitely if the system works or not.

tl;dr: tags are less obstuse than hashes. also, the libs we depend on should build as deterministically as possible.

See this discussion.

TODO:

  1. Publish PyCIEMSS to PyPI OR start tagging releases ciemss/pyciemss#344
  2. (Optional?) Freeze MIRA release in PyCIEMSS lib
  3. Start using the specific releases in our poe task.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant