@high-accountant-32689 / @average-finland-92144 / @glamorous-carpet-83516 I see this PR https://github.com/flyteorg/flytekit/issues/2501 (and many such PRs)
I don’t think we should remove the protective upper bound of flytekit 2.0.0 unless it’s causing problems?
➕ 1
h
high-accountant-32689
06/20/2024, 6:28 PM
Agreed .
@glamorous-carpet-83516, can we hold off on all those PRs? Wwe have 17 PRs that are essentially removing the upper bound constraint on the flytekit version.
g
glamorous-carpet-83516
06/20/2024, 6:31 PM
why do we need upper-bound of flytekit?
glamorous-carpet-83516
06/20/2024, 6:32 PM
if we need it, should we add that to all the flytekitplugins? some plugins don’t have upper bound
h
high-accountant-32689
06/26/2024, 3:51 AM
This is more to future-proof plugins (major versions signal potential fundamental breakages). However, as we don't have any plans for a major version bump of flytekit, I feel that those PRs only add noise and don't accomplish much.
g
glamorous-carpet-83516
06/26/2024, 5:38 AM
cc @high-accountant-32689 My point is that if a user installs Flytekit v2 in the future, they won’t be able to use plugin v1 anymore, even if Flytekit v2 is backward compatible or plugin v1 is compatible with Flytekit v2