fix: print version number that updater.writeVersion returns #670
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
brettdh
force-pushed
the
fix-dry-run-version
branch
from
b48389d
to
d0673e7
Compare
|
@jbottigliero Can we get this merged? It's causing some serious confusion at the moment. |
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.
For custom updaters that derive the new version from the file contents (e.g.
newVersion = oldVersion + 1), the log output was showing the new computed semver version, rather than the actual version applied by the updater. This PR corrects the output for such custom updaters.Closes expo-community/standard-version-expo#18.
Closes expo-community/standard-version-expo#10.