orbax icon indicating copy to clipboard operation
orbax copied to clipboard
verified publisher icon google

Tagging releases

Open nhey opened this issue 1 year ago • 2 comments

Would it possible for you to resume tagging releases to keep up with orbax-checkpoint and orbax-export on pypi? Something like checkpoint-vX.X.X and export-vX.X.X would be helpful.

nhey avatar Feb 07 '24 16:02 nhey

Sorry, don't quite understand the question. On PyPI, orbax-checkpoint and orbax-export are totally independent packages, so why is there a need for tagging there?

Also, you say "resume tagging releases" but I'm not aware that we've ever done this in the past?

cpgaffney1 avatar Feb 07 '24 16:02 cpgaffney1

Apologies for the lack of context. When you release a new version for orbax-checkpoint or orbax-export on pypi, I ask that you also create a git tag for the corresponding commit in this repository so that it is possible to identify the git revision for that version.

Releases were tagged on github until orbax split into two independent packages: https://github.com/google/orbax/tags and https://github.com/google/orbax/releases.

nhey avatar Feb 07 '24 17:02 nhey