1 new commit pushed to

<https://github.com/flyteorg/flytekit-java/tree/master|master>

by github-actions[bot]

<https://github.com/flyteorg/flytekit-java/commit/e224daad3950387e46abd665b75c42806ddb6c3a|e224daad>

- [maven-release-plugin] prepare for next development iteration flyteorg/flytekit-java

1 new commit pushed to

<https://github.com/flyteorg/flytekit-java/tree/master|master>

by narape

<https://github.com/flyteorg/flytekit-java/commit/71f7e50dddfe5ad771b163a6c991b270a04f8de0|71f7e50d>

- Add JacksonSdkLiteralType (#220) flyteorg/flytekit-java

1 new commit pushed to

<https://github.com/flyteorg/flyte/tree/master|master>

by cosmicBboy

<https://github.com/flyteorg/flyte/commit/42a24678efe301e837e8f643f0b45c857b63f621|42a24678>

- Update RFC process (#3460) flyteorg/flyte

#3551 [Docs] Copy code button puts too much html in buffer Issue created by tsheiner Description As example, just after this point in docs there is a code block with copy code button. If you press button and then paste you get this output:

span.prompt1:before {
  content: "$ ";
}
git clone <https://github.com/flyteorg/flytesnacks>
cd flytesnacks/cookbook
pip install -r core/requirements.txt

Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

#55 [Snyk] Security upgrade alpine from 3.14 to 3.16 Pull request opened by snyk-bot Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image. Changes included in this PR • boilerplate/flyte/golang_dockerfile/Dockerfile.GoTemplate We recommend upgrading to

alpine:3.16

, as this image has only 1 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected. Some of the most important vulnerabilities in your base image include: * * * Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs. For more information: https://camo.githubusercontent.com/3b9c5f09a18418eeed3bebe90bf9e6718391de585a68b91af0383c637489ced1/68747470733a2f2f6170692e7365676d656e742e696f2f76312f706978656c2f747261636b3f646174613d65794a33636d6c305a55746c65534936496e4a79576d785a634564485932527954485a7362306c596430645563566734576b4652546e4e434f5545774969776959573576626e6c746233567a535751694f6949354e32466c593245354e5330325a5759354c5451774e6d5974595467794f5330345a6a4a6c5957466a595467774d4751694c434a6c646d567564434936496c425349485a705a58646c5a434973496e42796233426c636e52705a584d694f6e736963484a4a5a434936496a6b335957566a59546b314c545a6c5a6a6b744e4441325a6931684f4449354c54686d4d6d566859574e684f4441775a434a3966513d3d 🧐 View latest project report 🛠️ Adjust project settings * * * Learn how to fix vulnerabilities with free interactive lessons: 🦉 Learn about vulnerability in an interactive lesson of Snyk Learn. flyteorg/flytecopilot GitHub Actions: Build & Push Flyte copilot Image GitHub Actions: Goreleaser GitHub Actions: Bump Version DCO: DCO ✅ 6 other checks have passed 6/10 successful checks

1 new commit pushed to

<https://github.com/flyteorg/flytekit/tree/master|master>

by wild-endeavor

<https://github.com/flyteorg/flytekit/commit/c0b06bedb6d6dcd3d1200b19f1e3198d20c9baf8|c0b06bed>

- General Partial support in flytekit and multi-list support in flytekit (#1556) flyteorg/flytekit

Release - [Beta] Partials, deviceflow, pyflyte run multiple files, python 3.11 support New release published by wild-endeavor What's Changed • Make

FlyteFile

compatible with

Annotated[..., HashMethod]

by @AdrianoKF in #1544 • move FlyteSchema deprecation warning to initialization method by @cosmicBboy in #1558 • add pod_template and pod_template_name arguments for ContainerTask by @flixr in #1515 • Pass locally defined scopes to RemoteClientConfigStore by @franco-bocci in #1553 • TypeTransformer for TensorFlow model by @samhita-alla in #1562 • Remove flytekit-fsspec plugin from default dockerfile by @wild-endeavor in #1561 • Device auth flow / Headless auth by @kumare3 in #1552 • support python 3.11 by @cosmicBboy in #1557 • url encode secret in client credentials flow by @wild-endeavor in #1566 • Python run multiple files by @pingsutw in #1559 • General Partial support in flytekit and multi-list support in flytekit by @kumare3 in #1556 New Contributors • @franco-bocci made their first contribution in #1553 Full Changelog: v1.5.0b0...v1.5.0b1 flyteorg/flytekit

1 new commit pushed to

<https://github.com/flyteorg/flyteadmin/tree/master|master>

by hamersaw

<https://github.com/flyteorg/flyteadmin/commit/eb695b19dcc6fd53492176586c2ab9d64f0c990d|eb695b19>

- Populate TaskNodeMetadata on CreateNodeExecutionModel to correctly display fast cache (#483) flyteorg/flyteadmin

#483 Populate TaskNodeMetadata on CreateNodeExecutionModel to correctly display fast cache Pull request opened by hamersaw TL;DR Current the CacheStatus field on node executions is only set when updating an existing model. In the case of fast cache work, where only a single node execution event will be sent for a node (ie. cache hit / succeeded), this information is never set and as a result the "cache hit" icon is never displayed in the UI. This PR sets CacheStatus if it exists on the first node execution event. Type ☑︎ Bug Fix ☐ Feature ☐ Plugin Are all requirements met? ☑︎ Code completed ☑︎ Smoke tested ☑︎ Unit tests added ☑︎ Code documentation added ☐ Any pending items have an associated Issue Complete description ^^^ Tracking Issue flyteorg/flyte#2886 Follow-up issue NA flyteorg/flyteadmin GitHub Actions: Goreleaser GitHub Actions: Build & Push Flyteadmin Image GitHub Actions: Build & Push Flytescheduler Image GitHub Actions: Bump Version ✅ 6 other checks have passed 6/10 successful checks

Release - v1.1.88 New release published by flyte-bot Changelog • eb695b1 Populate TaskNodeMetadata on CreateNodeExecutionModel to correctly display fast cache (#483) flyteorg/flyteadmin

#3552 Update troubleshooting guide Pull request opened by davidmirror-ops Tracking issue Implements the idea of #3340 Describe your changes Check all the applicable boxes ☑︎ I updated the documentation accordingly. ☑︎ All new and existing tests passed. ☑︎ All commits are signed-off. Screenshots Note to reviewers flyteorg/flyte ✅ All checks have passed 6/6 successful checks

#1856 rfc: docstring metadata Pull request opened by kennyworkman flyteorg/flyte DCO: DCO ✅ 5 other checks have passed 5/6 successful checks

#1568 fix: Silence keyring warnings by changing to debug Pull request opened by ggydush TL;DR Replace warning with debug logs for keyring. Type ☑︎ Bug Fix ☐ Feature ☐ Plugin Are all requirements met? ☐ Code completed ☐ Smoke tested ☐ Unit tests added ☐ Code documentation added ☐ Any pending items have an associated Issue Complete description How did you fix the bug, make the feature etc. Link to any design docs etc Tracking Issue https://github.com/flyteorg/flyte/issues/ Follow-up issue NA OR https://github.com/flyteorg/flyte/issues/ flyteorg/flytekit GitHub Actions: build-plugins (3.8, flytekit-dbt) GitHub Actions: build-plugins (3.8, flytekit-data-fsspec) GitHub Actions: build-plugins (3.8, flytekit-dask) GitHub Actions: build-plugins (3.8, flytekit-bigquery) GitHub Actions: build-plugins (3.8, flytekit-aws-sagemaker) GitHub Actions: build-plugins (3.8, flytekit-aws-batch) GitHub Actions: build-plugins (3.8, flytekit-aws-athena) GitHub Actions: lint GitHub Actions: docs GitHub Actions: build (windows-latest, 3.11) GitHub Actions: build (windows-latest, 3.9) GitHub Actions: build (windows-latest, 3.8) GitHub Actions: build (ubuntu-latest, 3.11) GitHub Actions: build (ubuntu-latest, 3.10) GitHub Actions: build (ubuntu-latest, 3.9) GitHub Actions: Docs Warnings GitHub Actions: build (ubuntu-latest, 3.8) ✅ 2 other checks have passed 2/19 successful checks

1 new commit pushed to

<https://github.com/flyteorg/flytekit/tree/master|master>

by wild-endeavor

<https://github.com/flyteorg/flytekit/commit/6c52297ae65914bec5988e6fbae0a20fa9917599|6c52297a>

- fix: Silence keyring warnings by changing to debug (#1568) flyteorg/flytekit

#3553 [RFC] Config Override Pull request opened by ByronHsu Tracking issue #475 Describe your changes Add RFC Note to reviewers Need discussion on the UI part! flyteorg/flyte DCO: DCO ✅ 5 other checks have passed 5/6 successful checks

Release - 0.4.13 New release published by narape What's Changed • Add support to apply node using a Map[String, SdkBindingData[_]] by @andresgomezfrr in #216 Full Changelog: 0.4.12...0.4.13 flyteorg/flytekit-java

Release - 0.4.14 New release published by narape What's Changed • [Snyk] Upgrade com.google.api.grpc:proto-google-common-protos from 2.14.1 to 2.14.2 by @EngHabu in #215 • Add binding collection/map to SdkBindingDataFactory for Scala by @narape in #219 Full Changelog: 0.4.13...0.4.14 flyteorg/flytekit-java

#3554 [UI Feature] Detailed schedule information in workflow page Issue created by pradithya Motivation: Why do you think this is important? When multiple scheduled launch plans are bound to a single workflow the information on the workflow page is lacking. The schedules section in the workflow page currently only shows the list of schedules and no further information about the corresponding launch plan. Goal: What should the final outcome look like, ideally? Ideally, in addition to the schedule, the launch plan name and a link that points to the corresponding launch plan page should be visible on the workflow page. Propose: Link/Inline OR Additional context Add the launch plan name and link to the launch plan page next to the schedule in the workflow page. Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

#3555 [UI Feature] Show launchplan name and ability to filter by launchplan in workflow execution list Issue created by pradithya Motivation: Why do you think this is important? When multiple launch plan is bound to the same workflow, it's unclear which workflow execution correspond with which launch plan. In order to figure that out, users typically have to open the execution details and check the execution inputs. This user experience is not ideal. As can be seen below, multiple executions started on 3/25/2023 50012 AM UTC but it's lacking information about the launch plan/schedule which trigger the execution. Goal: What should the final outcome look like, ideally? Users should be able to easily identify which launch plan is used when executing a workflow, either by adding a column that identifies the launch plan or the ability to filter execution by launch plan or both. Propose: Link/Inline OR Additional context • Ability to filter execution using the launch plan name in the workflow page • Display the launch plan name as a column in the execution list Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

1 new commit pushed to

<https://github.com/flyteorg/flytekit-java/tree/master|master>

by github-actions[bot]

<https://github.com/flyteorg/flytekit-java/commit/ee214e1fe43d08be21a68aecb1d613815c0e74c5|ee214e1f>

- [maven-release-plugin] prepare release 0.4.15 flyteorg/flytekit-java

1 new commit pushed to

<https://github.com/flyteorg/flytekit-java/tree/master|master>

by github-actions[bot]

<https://github.com/flyteorg/flytekit-java/commit/707398f90c32578e59b28529d59d74f26cdeaa2d|707398f9>

- [maven-release-plugin] prepare for next development iteration flyteorg/flytekit-java

Release - 0.4.15 New release published by honnix The same as 0.4.14 flyteorg/flytekit-java

#3556 [Housekeeping] Add ggydush to flytekit committers Issue created by wild-endeavor Add ggydush to the https://github.com/orgs/flyteorg/teams/flytekit-committers/members group. flyteorg/flyte

1 new commit pushed to

<https://github.com/flyteorg/flytepropeller/tree/master|master>

by hamersaw

<https://github.com/flyteorg/flytepropeller/commit/01218d2636a30c05b3daf362c335f2b21b793b49|01218d26>

- persisting k8s plugin state between evaluations (#540) flyteorg/flytepropeller

#3557 [BUG] Unnecessary warning in response to every pyflyte command Issue created by tsheiner Describe the bug 1. execute any valid pyflyte command 2. see in response the following warning

{"asctime": "2023-03-30 10:54:22,803", "name": "flytekit", "levelname": "WARNING", "message": "FlyteSchema is deprecated, use Structured Dataset instead."}

Expected behavior That I only get this warning if I am doing something that involves FlyteSchema Additional context to reproduce No response Screenshots No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

1 new commit pushed to

<https://github.com/flyteorg/flyteconsole/tree/master|master>

by jsonporter

<https://github.com/flyteorg/flyteconsole/commit/ca1b5b83e7177efd941e0c29b0c539fc610dfa87|ca1b5b83>

- gate node in dynamic task (#729) flyteorg/flyteconsole

#3354 [BUG] [CONSOLE] gate node in dynamic task Issue created by wild-endeavor Describe the bug Gate nodes inside of dynamic tasks don't behave the same. This workflow https://github.com/flyteorg/flytesnacks/blob/cecf8b1c98b784da3f15c1ab04624619890d1d16/cookbook/core/control_flow/human_in_the_loop.py#L82 is functionally the same as the

mainwf

that we've been testing on, except that it happens inside a dynamic task instead of the top level workflow. However when run inside a dynamic workflow, things don't look the same. None of the gate node stuff is there and the approval node only shows Running not Paused. Expected behavior Things should look the same as the non-dynamic case. This includes all views (node-list, graph, timeline) Additional context to reproduce No response Screenshots No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

Release - v1.1.74 New release published by flyte-bot Changelog • 01218d2 persisting k8s plugin state between evaluations (#540) flyteorg/flytepropeller

#547 [Snyk] Security upgrade alpine from 3.13.7 to 3.14 Pull request opened by eapolinario This PR was automatically created by Snyk using the credentials of a real user. Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image. Changes included in this PR • boilerplate/flyte/golang_dockerfile/Dockerfile.GoTemplate We recommend upgrading to

alpine:3.14

, as this image has only 0 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected. Some of the most important vulnerabilities in your base image include: * * * Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs. For more information: https://camo.githubusercontent.com/a181da9b8d903a5b93ab84f1a9e0434cafbd927f88695cc88b2ba64ccc456fb9/68747470733a2f2f6170692e7365676d656e742e696f2f76312f706978656c2f747261636b3f646174613d65794a33636d6c305a55746c65534936496e4a79576d785a634564485932527954485a7362306c596430645563566734576b4652546e4e434f5545774969776959573576626e6c746233567a535751694f69497a5a6a646c5a47526c4d69316d596a63334c5451785a4449744f5441304f43316b4f5459354d7a426c4e5759355a6a4d694c434a6c646d567564434936496c425349485a705a58646c5a434973496e42796233426c636e52705a584d694f6e736963484a4a5a434936496a4e6d4e32566b5a4755794c575a694e7a63744e44466b4d6930354d4451344c5751354e6a6b7a4d4755315a6a6c6d4d794a3966513d3d 🧐 View latest project report 🛠️ Adjust project settings * * * Learn how to fix vulnerabilities with free interactive lessons: 🦉 Learn about vulnerability in an interactive lesson of Snyk Learn. flyteorg/flyteadmin DCO: DCO ✅ 1 other check has passed 1/2 successful checks

1 new commit pushed to

<https://github.com/flyteorg/flyteconsole/tree/master|master>

by jsonporter

<https://github.com/flyteorg/flyteconsole/commit/c82e7556250582d315d3f6cb3edafb7ab2a16fdf|c82e7556>

- fix: type error on invalid nested json input (#693) flyteorg/flyteconsole