This repository was archived by the owner on Jul 27, 2026. It is now read-only.
|
I am super excited for this feature described in the README: When will version 1.3.2 be available? Could the README be updated so that others aren't disappointed getting excited about a feature that doesn't exist yet? |
Answered by
snicoll
Mar 3, 2022
Replies: 1 comment 2 replies
|
Thanks for the interest @sckirk. We'll release 1.3.2 shortly as we've configured a new release pipeline and we'd like to give it a try. As for this particular feature, I can see that the fix was actually merged in |
2 replies
Answer selected by
garyrussell
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thanks for the interest @sckirk. We'll release 1.3.2 shortly as we've configured a new release pipeline and we'd like to give it a try.
As for this particular feature, I can see that the fix was actually merged in
1.3.1and the readme wrongly references 1.3.2. So you should be able to use this already.