v0.7.3 does not include #16 #19
Comments
|
Indeed. I will have to investigate why there are missing commits in the 0.7.3 tag, in the master branch the tag is clearly made after #16 was merged. At this point I do not see why the commit is not included when checking out the 0.7.3 tag. |
|
We really need to make another release in the near future, we will have to make sure that it includes all of the missing commits, and likely amend the CHANGELOG to reflect the release that the changes are actually included in. Thank you so much for pointing this out, it has gone unnoticed for quite some time. ;-) |
Just bumps the version so we can make sure the 0.7.3 fixes are included this time. The tag for 0.6.3 did not include aoo of the commits since the 0.6.2 release. 0.6.3 was never released on hex.pm, but we still need to bump the version to ensure no users end up using a cached version from the 0.6.3 tag on GitHub. Closes #19 Signed-off-by: Winford <[email protected]>
Just bumps the version so we can make sure the 0.7.3 fixes are included this time. The tag for 0.6.3 did not include aoo of the commits since the 0.6.2 release. 0.6.3 was never released on hex.pm, but we still need to bump the version to ensure no users end up using a cached version from the 0.6.3 tag on GitHub. Closes #19 Signed-off-by: Winford <[email protected]>
|
It would be nice if you publish 0.7.4 on hex.pm too, once it is released. Seems 0.7.3 was not published. |
|
That is absolutely the plan! We had a temporary problem with not being able to release on hex.pm, but that is sorted out now. I did not release 0.7.3 to hex.pm late, because somehow that was a bad tag, and did not actually include the fix that it was intended to address. I did not want to try retagging the release on GitHub, since this could cause problems for users who had pulled the tag and had it cached. I did discover a few housekeeping chores that I need to take care of before making this release. |
|
Thanks @UncleGrumpy , |
It seems v0.7.3 is for #16 (65e9053), however 65e9053 is not on the history of 0.7.3 (81543e5).
The text was updated successfully, but these errors were encountered: