Repository navigation
Prepare 0.1.1-beta.14 for merged worker recovery fix - #133
Merged
Merged
Conversation
This file contains hidden or 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
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.
Summary
Published 0.1.1-beta.13 predates the worker recovery fix already merged in #132. After a database retry reloads an attempt and the peer then fails, that fix lets the worker persist the safe error and next recovery time on the current tracked attempt.
Prepare that existing Main implementation for the compatible companion release by changing the authoritative
VersionSuffixfrombeta.13tobeta.14.VersionPrefixremains0.1.1. This PR changes onlyDirectory.Build.propsand preserves the current Main commits, including #122 and #132. NetRatel's requested release remainsv0.1.1-beta.1.Validation
Disclosure check