fix: Use latest value when checking release stage #412
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.
A serialization bug in crash reports would erroneously allow or prevent
crash reports from being delivered when the value of release stage
or notify release stages were changed after start() was called, or in a
subsequent build of the same app.
Some values in config are serialized as nested values, while others are
at the "top" level of config when written to disk. This change checks
the expected position and fallback value for every config option.
Fixes #405