Closed AndrewFasano closed 4 months ago
@AndrewQuijano and I had chatted about this issue.
It seems like the most straightforward path would be to just keep the PyPANDA version in line with the PANDA version.
Seems like we can now close this as the pushing to pypi seems to work now
The CI job to publish pypanda to PyPi fails as it doesn't increment the version. We have auto-versioning in our github actions so I suspect there's a straightforward way to add that version to the packages (perhaps pulling from an environment variable, or adding a step into the workflow that uses the variable to set the package version in some way?).
Perhaps it would be more efficient to only push to pypi if there's a chance within the pypanda source tree, instead of on every panda change? Not sure how that would work with the auto-versioning though.
Example CI failure: https://github.com/panda-re/panda/actions/runs/8510581386/job/23309444668 with relevant details:
@AndrewQuijano