<@U0265RTUJ5B> / <@U04H6UUE78B> / <@USU6W5ATA> I s...
# contribute
k
@Eduardo Apolinario (eapolinario) / @David Espejo (he/him) / @Kevin Su 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?
e
Agreed . @Kevin Su, can we hold off on all those PRs? Wwe have 17 PRs that are essentially removing the upper bound constraint on the flytekit version.
k
why do we need upper-bound of flytekit?
if we need it, should we add that to all the flytekitplugins? some plugins don’t have upper bound
e
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.
k
cc @Eduardo Apolinario (eapolinario) 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