[fix] Set upper limit for aim version #739
Open
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
alberttorosyan
requested review from
suchenzang,
ngoyal2707,
punitkoura,
moyapchen,
davides,
igormolybogFB,
Xirider,
andrewPoulton,
bashnick,
tangbinh,
urielsinger,
zycalice,
ArmenAg,
lilisierrayu and
adampolyak
as code owners
|
We are going to release the major release of Aim soon. Would be great if this PR can be merged beforehand, to prevent any failures. |
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.
With the upcoming major release of Aim (https://github.com/aimhubio/aim) Aim SDK will not be backwards compatible.
To prevent any failures on metaseq side, setting upper limit for the install Aim version