Update master branch to 1.0.4.99 #705
Merged
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
mimirmim
approved these changes
Dec 12, 2019
CaveSpectre11
added
Component: Core App
codeofalltrades
added
Code Review: Passed
and removed
Tag: Waiting For Code Review
codeofalltrades
added a commit
that referenced
this pull request
Dec 12, 2019
af76e5b Update master branch to 1.0.4.99 (CaveSpectre11) Pull request description: ### Problem master branch builds are still at 1.0.3.99 instead of 1.0.4.99 ### Root cause It wasn't updated to 1.0.4.99 when 1.0.4 was first released ### Solution Bump it now so it's done ### Notes This is only affecting the master branch, and is code that changes on release branches. Really only a little missed paperwork when 1.0.4 was created, and should be a trivial merge. Tree-SHA512: fbe8c082feb8a6f810628b70c1a014f3f51b9c53ba8a3e3f1ffa1eb1e2040bfbd4f404b8f3df16f4db832c58c3017b45a58e9dabff618a14f4ed7d01d2c003b5
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.
Problem
master branch builds are still at 1.0.3.99 instead of 1.0.4.99
Root cause
It wasn't updated to 1.0.4.99 when 1.0.4 was first released
Solution
Bump it now so it's done
Notes
This is only affecting the master branch, and is code that changes on release branches. Really only a little missed paperwork when 1.0.4 was created, and should be a trivial merge.