revert jiffy to 1.0.9 #4320
Closed
revert jiffy to 1.0.9 #4320
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jiffy > 1.0.9 breaks the windows builds. We tracked this down to jiffy getting rebar3 support in version 1.1.0 and fixes to that support in 1.1.1. We shipped our last release with jiffy 1.0.9 which directly preceded 1.1.0 (tho our tag is CouchDB-1.0.9). As far as I can tell there are no substantial fixes* in 1.1.0+ so we might as well unblock our release by reverting to jiffy 1.0.9. * davisp/jiffy@1.0.9...1.1.1
big-r81
approved these changes
Dec 19, 2022
nickva
approved these changes
Dec 19, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
jiffy > 1.0.9 breaks the windows builds. We tracked this down to jiffy getting rebar3 support in version 1.1.0 and fixes to that support in 1.1.1. We shipped our last release with jiffy 1.0.9 which directly preceded 1.1.0 (tho our tag is CouchDB-1.0.9). As far as I can tell there are no substantial fixes* in 1.1.0+ so we might as well unblock our release by reverting to jiffy 1.0.9.