Conversation
Contributor
Author
|
Blocked on new CLI release with test dev server that supports this CAN behavior |
THardy98
force-pushed
the
upgrade-on-can
branch
from
7f3cc8c to
d1184cf
Compare
Merged
Contributor
Author
|
Superceded by #1972 |
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
1 participant
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.
What was changed
Propagate CAN versioning and CAN suggested reasons to Python.
Why?
Users can specify auto-upgrade behavior on CAN.
Part of Expose upgrade on continue as new in SDKs features#738
How was this tested:
Integration tests
Any docs updates needed?
Maybe