-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Keep updating v5 #106
base: master
Are you sure you want to change the base?
Keep updating v5 #106
Conversation
6e8c993
to
5d21c9d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @Michaelvll!
# compatibility. | ||
# TODO(zhwu): Remove v5 support after 0.10.0 release. | ||
version_commit: | ||
v5: 1ed40e3174646ba835423b9308d8d6489f83b6bc |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just so I understand: when we update catalog fetchers in our main skypilot repo, this hash would also need to be updated?
If so, we should probably make a note of this in README.md
# TODO(zhwu): Remove v5 support after 0.10.0 release. | ||
version_commit: | ||
v5: 1ed40e3174646ba835423b9308d8d6489f83b6bc | ||
v6: latest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we also add a quick update to README.md for this repo that v6 is now a supported catalog version? Can be another PR too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch! Updated.
Although we bump the version to v6. We should keep updating the v5 so that the older version skypilot user can get the latest catalogs.