You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Somehow, the commit that bumped the VERSION file to 2.1.7 didn't make it into master. If you check out this repo and build it, setup.py lists the current version as 2.1.6.
I would just update the VERSION file in a PR, but then there's a conflict with the PyPi-released version and the git history on this repo. Perhaps it's just easier to release a 2.1.8?
@JasonMWhite Thanks for the hint! I don't know how that happened actually, it should not be possible actually. Even though it probably points to some issue that should be understood, I prefer the 'fast way' and just go ahead with release 2.1.8 instead.
Activity
JasonMWhite commentedon Nov 22, 2017
I would just update the VERSION file in a PR, but then there's a conflict with the PyPi-released version and the git history on this repo. Perhaps it's just easier to release a 2.1.8?
ankostis commentedon Nov 22, 2017
Byron commentedon Dec 11, 2017
@JasonMWhite Thanks for the hint! I don't know how that happened actually, it should not be possible actually. Even though it probably points to some issue that should be understood, I prefer the 'fast way' and just go ahead with release 2.1.8 instead.