Merged
Conversation
Contributor
|
Shouldn't we update to 48.1-2, instead? |
Contributor
Author
|
UDENG-6692 specified 46.0. @seb128, is there a particular reason to have 46.0 or should we go for 48.1? |
No, it's just that we pinned 46 as a serie in the versions report because they didn't release a 47, I will unpin so 48 is picked, it makes sense to go for current |
Contributor
Author
|
The snap builds (I did a no-op force-push because the CI had an issue) and I installed and launched it without issues. |
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
3 participants
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.
Local x64 build succeeded.