Cross posting - https://flyte-org.slack.com/archives/C0308A8TNAU/p1746735621409459

can someone add Flyte to this list - https://github.com/astral-sh/ruff/tree/2abcd86c57f8fafc219ea622d11d0984d639fba2?tab=readme-ov-file#whos-using-ruff

Hi everyone: The new Flyte docs repo is public! As you may have noticed, the Flyte docs were migrated to a new/common system, and the repo is now made public for anyone to contribute. Both Flyte and Union docs are now open to all. Changes will, of course, be done via pull request and will require approval of the code owners, but anyone in the community will be able to contribute. Contributor guides can be found here: https://www.union.ai/docs/flyte/community We'll be running an intro and Q&A during the next community sync (June 3) but drop your questions in this thread at anytime. Thank you!

📣 Flyte Monthly Contributors Spotlight Here’s a roundup of this month’s amazing contributors and their contributions: • @microscopic-truck-17789 made `image_spec.tag` a cached property to avoid repeated hash computations. • @faint-pilot-24699 fixed an issue to allow cache policies to accept a list. • @cool-lifeguard-49380 added support for `labels` and `annotations` in the task decorator. • @clean-glass-36808 added support for configuring storage from a secret, enabled plumbing of pod affinity and topology spread constraints, and introduced customization of rollout strategy for flyte components. • Perttu Kärnä added support for configuring deployment annotations in the helm chart. • @redartera added the `--interruptible` option to `pyflyte run --remote`. • @bland-dress-83134 updated the default propeller raw output prefix to use the storage bucket name in the helm chart config. • @worried-airplane-87065, @gentle-tomato-480, @proud-glass-36655, and @echoing-account-76888 were active in helping others on Slack. Thank you all for pushing flyte forward with your awesome contributions! 🚀

Happening today at 9:00am PT 🙂 https://flyte-org.slack.com/archives/C02JMT8KTEE/p1748392003149539

📣 Flyte Monthly Contributors Spotlight Here’s a roundup of this month’s amazing contributors and their contributions: • @faint-pilot-24699 fixed a bug where agent auto discovery conflicted with explicit task type mappings. • @clean-glass-36808 resolved issues with pod template overrides, cleaned up the workflow store interface, and has been actively supporting users on Slack. • @echoing-account-76888 added a signal watcher to copilot and has been helping out in the community. • @bitter-megabyte-57097 fixed dataclass deserialization for optional fields and added support for setting default resource requests/limits in pyflyte. • @gentle-tomato-480 and @proud-glass-36655 have been actively helping others on Slack. Thank you all for pushing flyte forward with your awesome contributions! 🚀

Dear Flyte Community, I know it’s unconventional, but I want to start by saying sorry. We’ve been quiet for a while, and for that, I want to apologize. The silence wasn’t neglect. We’ve been heads-down building something big. Today, I finally get to share a glimpse of what’s next. Flyte 2.0 is coming. This isn’t just an upgrade. Flyte 2.0 reimagines the platform as a fully dynamic orchestrator with Python-native authoring, letting you build agentic systems, ML pipelines, and AI applications. The same core principles of Flyte remain: modularity, composability, auto-caching, durability, versioning, parallel execution. But now we’re adding the flexibility and dynamism you’ve been asking for. And we’re staying true to what made Flyte special from the beginning: open source. That won’t change. Flyte 2.0 will be built in the open, and we want your feedback to shape its future, especially from those most actively using Flyte and our community already. What you need to know: On July 29th, I’m introducing the Flyte 2.0 vision in a virtual session. I’ll walk through the thinking behind Flyte 2.0. I’ll share what’s changing, what’s staying the same, and where we’re headed. We’ll also host “office hours” so our community can contribute to Flyte’s vision. Three asks for you: 1. RSVP here to join the Flyte 2.0 vision session (even if you can’t make it, we’ll send you the recording) 2. Stay tuned on LinkedIn for ways to get involved 3. Please like/share/comment on our Flyte 2.0 content on LinkedIn (this is so important for us as we grow our community) Thanks for being part of the journey. We can’t wait to build the future of AI infrastructure with you. With gratitude and excitement, Ketan Co-creator of Flyte CEO, Union.ai My LinkedIn

Anyone in SF and wants to meet up tomorrow. I am around. Also can do a sneak peek at v2

📣 Flyte Monthly Contributors Spotlight Here’s a roundup of this month’s contributors and their fantastic work: • @cool-lifeguard-49380 added support for specifying Kubernetes labels and annotations directly in the task decorator. • @big-memory-81882 resolved incorrect overriding of CPU and memory in compile-time pod templates by task defaults. • @clean-glass-36808 optimized the workflow equality check in flytepropeller, fixed enqueueing in the node execution context, made plugin metric registration thread-safe, and added support for overriding the service account in Ray pod specs. • @ambitious-airplane-25777 added NATS as a new cloud events sender. • @dazzling-zebra-38345 implemented graceful shutdown for flyteadmin servers. • @worried-airplane-87065, @gentle-tomato-480, @tall-appointment-97015, @clean-glass-36808, @numerous-actor-35946, and @cool-nest-98527 have been actively supporting the community on Slack! Thank you all for pushing flyte forward with your contributions! 🚀

Hey everyone! You probably saw our the other week about Flyte 2.0! flyte 2 The team has been hard at work bringing in features to the new SDK: https://github.com/flyteorg/flyte-sdk We just released v2.0.0b13 on github • Now you can use flyteplugins-[Ray, Spark, Dask and OpenAI]. • The openai agents sdk natively works with flyte-sdk. • Spark/Ray and Dask async work with native sdk. • Better handling of data, much much faster! Previously we also added support for Decks(with streaming!), reusable containers and much more! 🙏 We'd love your feedback, if you'd like to try it out sign up for the beta: https://www.union.ai/beta

👋 Hey everyone, docker + flyte update We are rolling out a change to the container registry proxy (cr.flyte.org) to lower latency, globally available one that should lead to better pull times. The change should be seamless to any deployments but I wanted to call it in case you see any issues with

ImagePullBackoff

. Please let us know! cc @average-finland-92144 @tall-lock-23197

📣 Flyte Monthly Contributors Spotlight Here’s a roundup of August’s contributors and their fantastic work: • @clean-glass-36808 has been a consistent contributor to Flyte for over a year 🙌. In August alone, Jason: ◦ Updated the description entity repo to use auto-generated mocks via mockery, replacing hand-crafted mocks. ◦ Fixed Grafana dashboard queries for dynamic workflow metrics. ◦ Removed unused projectcontour annotations from Helm charts. ◦ Added option to configure service monitor for Flyte scheduler. ◦ Added OTEL configuration support in Helm chart. ◦ Cleaned up FlytePlugins code. ◦ Added support for Datacatalog service monitor. • Hsuan-Chen Chen added support for pyspark dataframe transformer when pyspark=4.0.0> and enabled execution creation via Flytectl config. • @nutritious-piano-11388 enabled namespace-scoped installations and replaced deprecated ClusterRole/ClusterRoleBinding with namespace-specific roles. • @witty-evening-52399 added project-level workflow concurrency control. • @alert-oil-1341, @early-napkin-90297, @clean-glass-36808, @numerous-actor-35946, @proud-glass-36655, and @rapid-artist-48509 have been actively supporting the community on Slack! Thank you all for helping push flyte forward! 🚀

Hey all 👋 If you're in SF for Tech Week this year, come join us! https://www.linkedin.com/posts/sageelliott_sftechweek-activity-7371572938216706048-Fv[…]m=member_desktop&rcm=ACoAABRR_mEBnNCOYJa19q8mvHt0uUz7nkjTCpk

🚨 New Flyte V1 release 🎉Flyte 1.16 is out! Big thanks to all new and existing contributors for making this happen 🙇🏽 Read the Release Notes, try it and let us know any feedback/questions!

📣 Flyte Monthly Contributors Spotlight Celebrating our awesome contributors for September ✨: • Barry Wu ◦ Added support for Literal type ◦ Introduced local caching with LRU for serialized literals ◦ Enabled dynamic platform detection for `ImageSpec` to support cross-platform development • @ancient-kilobyte-3161 ◦ Restored behavior for passing FlyteClient kwargs to gRPC channel creation • @clean-glass-36808 ◦ Removed unused node selector functions & legacy environment variables ◦ Added horizontal pod autoscaling ◦ Fixed OTEL helm chart config map • @acceptable-knife-37130, @early-napkin-90297, and @clean-glass-36808 have been actively supporting the community on Slack! Huge thanks to all of you for helping push flyte forward!

We just released flyte-sdk version v2.0.0b25 - Its a massive release and effort by a lot of folks! Top features: • Triggers - cron and rate schedules • Blazing fast data downloads. 5GB in 5s on a 10Gbps • Dist training support (torch elastic) • Support for

tranium, gpus, and tpus

• Sync/async apis for file and dir • flyteidl2 usage • Faster flyte imports and cli • Lots of examples for HoF, UDFs • Context passing in tasks • Push/pull private images • Provides externally built images by name -

Image.from_ref_name("my_image")

. --

flyte run --image my_image="<http://docker.io/|docker.io/>...."

Thank you to everyone for all the feedback so far on the Flyte 2.0 beta 🙏 flyte https://github.com/flyteorg/flyte-sdk/releases/tag/v2.0.0b25

📣 Flyte Monthly Contributors Spotlight Celebrating our awesome contributors for October ✨: • Anshul Jindal ◦ Lepton plugin for AI inference endpoints • @clean-glass-36808 ◦ Removed use of deprecated pod phase ◦ Fixed plugin resolution logic ◦ Fail branch node when child node times out ◦ Added default `sort_by` to `iterate_node_executions` • @gentle-umbrella-41187 ◦ Added support for `typing.Union` to copilot • @witty-evening-52399 ◦ Added a new concurrency policy feature to `LaunchPlan` • @acceptable-knife-37130 and @clean-glass-36808 have been actively supporting the community on Slack! Huge thanks to all of you for helping push flyte forward!

📣 Flyte Monthly Contributors Spotlight Celebrating our awesome contributors for November ✨: • @cool-lifeguard-49380 ◦ Fixed the resource construction process in the `plugin.BuildResource` function and improved user feedback on fatal errors ◦ Added start- and end-time log link template vars to Ray plugin • @aloof-magazine-44547 ◦ Fixed Pydantic transformer to support `from future import annotations` • @clean-glass-36808 ◦ Removed unused `DefaultWorkflowActiveDeadline` config ◦ Flyte 1.16.2 release 🎉 • @delightful-solstice-18580 ◦ Added support for Spark dataframes to flyte-sdk (flyte 2.0) • Sally Ouyang ◦ Addressed a bug in `enqueueBatches` function • @worried-airplane-87065, @acceptable-knife-37130 and @clean-glass-36808 have been actively supporting the community on Slack! Huge thanks to you all for helping push flyte forward!

📣 Flyte Monthly Contributors Spotlight Closing out the year by celebrating our awesome contributors from December ✨ • CtfChan ◦ Added remote workflow execution support to `pyflyte run` • @acceptable-knife-37130 ◦ Updated the standard ignore patterns to include more files in the new Flyte SDK • @aloof-magazine-44547 ◦ Fixed Pydantic deserialization for files and directories • @clean-glass-36808 ◦ Updated Flyte to Go 1.24 ◦ Updated x/crypto to v0.45.0 to fix security warnings • @delightful-solstice-18580 ◦ Updated the Spark plugin to ensure compatibility with both Spark 3.x and 4.x • @purple-father-70173 ◦ Added user annotations to K8s objects • @alert-oil-1341 and Debasis Dwivedy have been actively supporting the community on Slack Thanks for an incredible year of building flyte together!

@powerful-horse-58724 and I are live in the AI Eng office hours! https://www.linkedin.com/posts/local-ai-development-with-flyte-20-sdk-ugcPost-7435051[…]m=member_desktop&rcm=ACoAAApOVaYBcYw7AjC-iR9T9GF3c8V4XJtlqN0 Join us here 👆

Dear friends, When I first announced Flyte 2 last year, I promised we were building something big. Today, I get to say: we did it. Flyte 2 is here — locally, in open source, for everyone. 👉 Learn more about Flyte 2 💻 you can also find a live in-browser demo on this page, no install required. What is Flyte 2? This is fully dynamic, self-healing AI orchestration. Pure Python authoring. A terminal UI you'll actually love. Durable agent workflows that recover from failures on their own — including infrastructure failures like OOM errors and container pre-emption that most "durable execution" tools simply can't handle. What you can run today, locally: Durable agent workflows - orchestration AI and agents locally Terminal UI - launch, inspect, and manage workflows straight from your laptop Async I/O - non-blocking, concurrent task execution out of the box Local caching - reuse prior results to speed up iteration and reruns Local serving - serve apps that call workflows and execute agentic logic locally 🙏 Thank you. Genuinely. Every PR, every Slack message, every piece of feedback helped shape what Flyte 2 is today. A full Production K8s scale deployment is next. Flyte 2 (Union backend) is already available deployed in your cloud as part of our production preview on Union.ai Let us know here if your team wants in. In the meantime: try it, push it to its limits (if you dare), tell us what you think. With gratitude and momentum, Ketan Co-creator of Flyte P.S. If you've been waiting to share Flyte with your team or on socials, now's the moment. It means more than you know.

And a little bonus... Flyte.org has gotten a big update! Highly recommend you poke around 🙂

huge shout out to @lemon-grass-73500 for building https://andreahlert.github.io/flyte-plugin-registry/! this is such a comprehensive collection of all the flyte integrations. thank you so much for putting this together, André. this is incredibly valuable for the community 💛 flyte’s integrations come from both the core team and community contributors, and we’ve been working hard to expand native support for frameworks and libraries folks will benefit from. definitely check it out and let us know what you think. contributions are always welcome too!

📣 Pandera 0.30.0 is out, with support for Pandas >= 3 It also includes a bunch of bug-fixes for the polars and pandas backends, see the changelog for more details: https://github.com/unionai-oss/pandera/releases/tag/v0.30.0

Our very own @powerful-horse-58724 is streaming about Model Context Protocol: https://www.linkedin.com/events/7441876978707701760/

📣 Hi all 👋 super excited to announce 2 more major milestones in the path to GA’ing Flyte 2: a backend dev box with a completely reimagined UI. 👉 Try it here 🤔 What is the backend devbox? The dev box lets you run a real Flyte 2 backend (including full scheduling, persistence, API surface) with a single command: flyte start devbox. This is the same architecture that will power Flyte 2 in production. Whatever you build against it today will carry forward. 💻 Reimagined Flyte UI We’ve taken our UI for Union.ai (the enterprise Flyte platform) and created a free Flyte version so our community can have a truly best-in-class DevEx. We’ve spent two years building it alongside teams running AI at scale, and you can feel that. ⭐*️ Some highlights:* • Real-time execution state. • Interactive debugging so if a task runs out of memory, you can rerun it with more resources right from the UI, no code changes. • And when Flyte self-heals from a failure, you can see exactly what happened and when. Not just that it recovered, but how.

👋 Hi all, @powerful-horse-58724 and I will be running “AI Engineering Office Hours” today at 12pm PT. We’re going to cover some fun new stuff that we’ve shipped in Flyte v2: Agents with CodeMode and Memory capabilities. It’s a batteries-included construct in

<http://flyte.ai|flyte.ai>.agents.Agent

where you bring it tools (Flyte `task`s,

@trace

s, or pure Python functions), and it can dynamically compose workflows to get stuff done. Join us here 👇 https://www.linkedin.com/posts/nbantilan_pydanticmonty-ugcPost-7470904018463125506-3l[…]m=member_desktop&rcm=ACoAAApOVaYBcYw7AjC-iR9T9GF3c8V4XJtlqN0

We started a new Flyte newsletter! I shared the first addition in #C06B389BX43 last week, but I thought I should also mention it here. It contains "AI Engineering Tip" each week that highlights a feature Flyte and also includes the latest blogs, events, and more from the Flyte ecosystem and community. You can subscribe on substack: https://flytelog.substack.com/p/fan-out-tasks-like-a-pro-with-map

Flyte 2 Is Generally Available: The Durable, Open-Source AI Runtime! flyte > Today, Flyte 2 is generally available. It is faster, more scalable, and (my personal guarantee) genuinely fun to use. It remains open source and part of the Linux Foundation. Before I tell you what's in it, I want to tell you why it exists, because Flyte 2 is not an incremental release. It is a ground up rebuild of a system we have been refining for nearly a decade, rebuilt for a world that looks nothing like the one Flyte was born into. union.ai/blog-post/flyte-2-is-generally-available-the-durable-open-source-ai-runtime

👋 Hey all! just wanted to share some benchmarks we’ve been doing to benchmark Flyte v1 vs v2: • Flyte v1 vs v2 paper: this is a technical report showing the performance gains of v2, showing 4.3-6.5x faster runtimes on common workflow patterns • Flyte agent benchmark: this one demonstrates that Claude writing Flyte v2 code is ~2x more token efficient and requires 5x less iteration time than Claude writing Flyte v1 code. You can check out the papers in the

flyte-benchmarks

repo: github.com/flyteorg/flyte-benchmarks/…/pdfs