Open davidxia opened 1 week ago
Unfortunately, there was an issue with that release, which explains the discrepancy. We've reconciled this for others though. Apologies for the inconvenience.
I see. Can you move the git tag to the correct commit so it’s possible to examine the source in GitHub?
Expected Behavior
I expect git tags associated with released versions to correspond to the commit that produced software artifacts for those versions in PyPI.
Current Behavior
Currently v0.36.0 has a protobuf requirement of
protobuf>=4.24.0,<5.0.0
(permalink in case the tag moves). But when I download the sourcefeast-0.36.0.tar.gz
from https://pypi.org/project/feast/0.36.0/#files, I seesetup.py
hasprotobuf<4.23.4,>3.20
.Also the date that 0.36.0 was created in PyPI is Feb 17, 2024. The date of the git tag is April 15, 2024. 🤔
Steps to reproduce
See links in "current behavior."