Skip to content
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

Update flyte to use container registry images instead #630

Merged
merged 1 commit into from
Dec 3, 2020

Conversation

EngHabu
Copy link
Contributor

@EngHabu EngHabu commented Dec 2, 2020

Copy link
Contributor

@wild-endeavor wild-endeavor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so we're bumping too?

@kumare3
Copy link
Contributor

kumare3 commented Dec 2, 2020

should we bump, if we so we should create another release of flytekit?

@EngHabu
Copy link
Contributor Author

EngHabu commented Dec 2, 2020

You mean bumping the components' versions? or the flyte version? the former yes... the latter we don't have to... whenever flytekit is ready, we can bump it separately and then create a flyte release... no?

@EngHabu EngHabu requested a review from wild-endeavor December 2, 2020 20:29
@EngHabu EngHabu merged commit d9f6bba into master Dec 3, 2020
eapolinario pushed a commit to eapolinario/flyte that referenced this pull request Dec 20, 2022
Signed-off-by: Flyte-Bot <[email protected]>

Signed-off-by: Flyte-Bot <[email protected]>
Co-authored-by: flyte-bot <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants