There are a few updates we should make for the recent changes for v1.4.0:
update the README instructions to describe v1.4.0 instead of v1.3.0
update CHANGES.md to reflect the actual release month instead of when the previous change was submitted for code review
I'm opting not to change version now for the next version since we won't know if it'll be a major, minor, or micro bump; and the "publish" script already avoids clobbering existing releases if somebody were to forget next time.
There are a few updates we should make for the recent changes for v1.4.0:
I'm opting not to change
version
now for the next version since we won't know if it'll be a major, minor, or micro bump; and the "publish" script already avoids clobbering existing releases if somebody were to forget next time.