Closed joelb123 closed 1 year ago
In case it's still useful to you, I put together a fork on PyPi to host releases tracking the more recent history on the main branch of DendroPy (https://pypi.org/project/DendroPy-calver/) as well as some pending PRs. As another alternative, python package management systems can usually pin to specific commits on public git repositories.
Hi, first of, apologies to @joelb123 for the delay in responding to this.
Secondly, THANK you so much @mmore500 for your help here as well as the other feedback and PR's. Very much appreciated :)
As you can imagine, I'm a bit behind, but will hopefully take care of this in my next work cycle. As @mmore500 suggests, I personally pin to "development-main" or "main" rather than specific releases, but, of course, that's no excuse for not update version numbers.
No worries --- & totally relatable :). Glad to help how I can. If it would be useful to add some infrastructure to make releasing easier to keep up with (github actions CI for tests, a version bumping script, autodeploy on tagged releases via CI), I'd be happy to contribute a PR with some of that.
That would be awesome! Would you be interested in considering coming aboard as a maintainer? Happy to give you whatever permissions you need
I'd be open to that! That might actually be helpful for getting the CI running. I'll draft something up and @ you if I run into any issues with permissions as an outside contributor.
Hi @joelb123 --- closing this, as we just deployed a new release (v4.6.0) to PyPi. We've put together a more streamlined release process, so this will be easier to keep up with in the future.
Hi, to help with us users keeping up with developments, please create a release as well as update your tags. pypi lists 4.5.2 as the latest package, but there is no tag for 4.5.2 and no releases for anything.