Repository navigation
README: Flyte 1 reaches end of life on December 31, 2026 - #3484
Merged
Merged
Conversation
Add an end-of-life notice above the existing 'Looking for Flyte 2?' block: bug and security fixes until 2026-12-31, no updates or releases of any kind after that, and the repositories stay available to fork. Links to the Flyte 1 docs and the Flyte 1 to 2 migration guide. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Peeter Piegaze <1153481+ppiegaze@users.noreply.github.com>
ppiegaze
requested review from
cosmicbboy,
davidmirror-ops,
kumare3,
machichima,
pingsutw,
samhita-alla and
wild-endeavor
as code owners
November 5, 2026 10:07
davidmirror-ops
approved these changes
Nov 5, 2026
This file contains hidden or 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
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.
Adds a Flyte 1 end-of-life notice to the top of the README, above the existing "Looking for Flyte 2?" block.
Policy:
flytekit1.x and the Flyte 1 backend) gets bug fixes and security fixes.flyteorg/flytestay available, and the community can fork them to keep maintaining Flyte 1.The notice links to the Flyte 1 docs, which carry the same notice: https://www.union.ai/docs/v1/flyte/community/. It also links to the migration guide: https://www.union.ai/docs/v2/flyte/user-guide/migration/flyte-2/.
The same change is going into the
flyterepo'smasterbranch (the Flyte 1 backend).🤖 Generated with Claude Code