1 new commit pushed to

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

by cosmicBboy

<https://github.com/flyteorg/flytekit/commit/71d436ac456285a75b3ec462f34fc4524933c309|71d436ac>

- update configuration docs, fix some docstrings (#1530) flyteorg/flytekit

#1531 Data subsystem use fsspec Pull request opened by wild-endeavor flyteorg/flytekit GitHub Actions: build-plugins (3.8, flytekit-ray) GitHub Actions: build-plugins (3.8, flytekit-polars) GitHub Actions: build-plugins (3.8, flytekit-papermill) GitHub Actions: build-plugins (3.8, flytekit-pandera) GitHub Actions: build-plugins (3.8, flytekit-onnx-scikitlearn) GitHub Actions: build-plugins (3.8, flytekit-onnx-pytorch) GitHub Actions: build-plugins (3.8, flytekit-modin) GitHub Actions: build-plugins (3.8, flytekit-kf-tensorflow) GitHub Actions: build-plugins (3.8, flytekit-kf-pytorch) GitHub Actions: build-plugins (3.8, flytekit-kf-mpi) GitHub Actions: build-plugins (3.8, flytekit-k8s-pod) GitHub Actions: build-plugins (3.8, flytekit-hive) GitHub Actions: build-plugins (3.8, flytekit-greatexpectations) GitHub Actions: build-plugins (3.8, flytekit-duckdb) GitHub Actions: build-plugins (3.8, flytekit-dolt) GitHub Actions: build-plugins (3.8, flytekit-deck-standard) 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.9) GitHub Actions: build (windows-latest, 3.8) GitHub Actions: build (ubuntu-latest, 3.10) GitHub Actions: build (ubuntu-latest, 3.9) GitHub Actions: build (ubuntu-latest, 3.8) ✅ No checks have passed 0/30 successful checks

#3389 Use correct team in create-pull-request Pull request opened by eapolinario Tracking issue Describe your changes We should use an existing team in the github action we use to open the "Update Flyte Components" PR, otherwise we now see errors like https://github.com/flyteorg/flyte/actions/runs/4318515846/jobs/7536896252, even though the PR ends up being opened. 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 2/2 successful checks

1 new commit pushed to

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

by wild-endeavor

<https://github.com/flyteorg/flyte/commit/e9250c7255dadf283b364933dec2c47dd9a3aea6|e9250c72>

- Use correct team in create-pull-request (#3389) flyteorg/flyte

#3390 Bump golang.org/x/net from 0.3.1-0.20221206200815-1e63c2f08a10 to 0.7.0 in /docker/sandbox-bundled/bootstrap Pull request opened by dependabot[bot] Bumps golang.org/x/net from 0.3.1-0.20221206200815-1e63c2f08a10 to 0.7.0. Commits • See full diff in compare view Dependabot compatibility score Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting

@dependabot rebase

. * * * Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: •

@dependabot rebase

will rebase this PR •

@dependabot recreate

will recreate this PR, overwriting any edits that have been made to it •

@dependabot merge

will merge this PR after your CI passes on it •

@dependabot squash and merge

will squash and merge this PR after your CI passes on it •

@dependabot cancel merge

will cancel a previously requested merge and block automerging •

@dependabot reopen

will reopen this PR if it is closed •

@dependabot close

will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually •

@dependabot ignore this major version

will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) •

@dependabot ignore this minor version

will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) •

@dependabot ignore this dependency

will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) •

@dependabot use these labels

will set the current labels as the default for future PRs for this repo and language •

@dependabot use these reviewers

will set the current reviewers as the default for future PRs for this repo and language •

@dependabot use these assignees

will set the current assignees as the default for future PRs for this repo and language •

@dependabot use this milestone

will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the Security Alerts page. flyteorg/flyte GitHub Actions: generate_kustomize GitHub Actions: docs GitHub Actions: trigger-sandbox-lite-build GitHub Actions: compile GitHub Actions: trigger-sandbox-build GitHub Actions: test-bootstrap GitHub Actions: generate_helm ✅ 2 other checks have passed 2/9 successful checks

#204 [Snyk] Upgrade com.google.api.grpc:proto-google-common-protos from 2.10.0 to 2.14.0 Pull request opened by snyk-bot Snyk has created this PR to upgrade com.google.api.grpc:proto-google-common-protos from 2.10.0 to 2.14.0. ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project. * * * • The recommended version is 4 versions ahead of your current version. • The recommended version was released a month ago, on 2023-02-02. * * * Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs. For more information: https://camo.githubusercontent.com/a172dbf815eab377bc7417c56f1e901148817d8c4313dd861071c596a8eb279c/68747470733a2f2f6170692e7365676d656e742e696f2f76312f706978656c2f747261636b3f646174613d65794a33636d6c305a55746c65534936496e4a79576d785a634564485932527954485a7362306c596430645563566734576b4652546e4e434f5545774969776959573576626e6c746233567a535751694f69497a59544e694d3251335a6930345a6a64694c54526d5957457459544d325a69316a4d4463354d7a5931595445795a6a63694c434a6c646d567564434936496c425349485a705a58646c5a434973496e42796233426c636e52705a584d694f6e736963484a4a5a434936496a4e684d32497a5a44646d4c54686d4e3249744e475a68595331684d7a5a6d4c574d774e7a6b7a4e6a56684d544a6d4e794a3966513d3d 🧐 View latest project report 🛠️ Adjust upgrade PR settings 🔕 Ignore this dependency or unsubscribe from future upgrade PRs flyteorg/flytekit-java ✅ All checks have passed 3/3 successful checks

1 new commit pushed to

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

by hamersaw

<https://github.com/flyteorg/flyteidl/commit/3674402608a0d453d8004d84b1685fdf76904a7f|36744026>

- added dynamic_job_spec_uri to dynamic workflow metadata and node execution closure (#360) flyteorg/flyteidl

#360 Add dynamic_job_spec_uri to support recovering partially completed DynamicWorkflows Pull request opened by hamersaw TL;DR Add a

dynamic_job_spec_uri

field to the

DynamicWorkflowNodeMetadata

and

NodeExecutionClosure

proto messages. This allows tracking the raw subworkflow for a dynamic task between executions. The main use is recovering from partially completed dynamic tasks - ie. dyanmic parent task completed but a task in the subworkflow failed. 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#3121 Follow-up issue NA flyteorg/flyteidl ✅ All checks have passed 13/13 successful checks

#3391 Proto-docs: client-side pod templates Pull request opened by eapolinario Tracking issue #3385 Describe your changes Documentation for the client-side pod templates feature going out in the Flyte 1.4 release. Check all the applicable boxes ☑︎ I updated the documentation accordingly. ☐ All new and existing tests passed. ☐ All commits are signed-off. Note to reviewers flyteorg/flyte GitHub Actions: compile GitHub Actions: generate_kustomize GitHub Actions: docs GitHub Actions: generate_helm ✅ 2 other checks have passed 2/6 successful checks

#695 [Snyk] Upgrade eslint from 8.31.0 to 8.33.0 Pull request opened by EngHabu This PR was automatically created by Snyk using the credentials of a real user. Snyk has created this PR to upgrade eslint from 8.31.0 to 8.33.0. ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project. * * * • The recommended version is 2 versions ahead of your current version. • The recommended version was released a month ago, on 2023-01-28. Release notes Package name: eslint • 8.33.0 - 2023-01-28 Features • `2cc7954` feat: add

restrictDefaultExports

option to no-restricted-exports rule (#16785) (Nitin Kumar) Documentation • `17f4be2` docs: Fix examples in no-multiple-empty-lines rule (#16835) (jonz94) • `9c7cfe3` docs: 'Source Code' content in 'Set up Development Environment' page (#16780) (Ben Perlmutter) • `ede5c64` docs: Custom processors page (#16802) (Ben Perlmutter) • `2620614` docs: Code of Conduct page (#16781) (Ben Perlmutter) • `50a8efd` docs: report a sec vulnerability page (#16808) (Ben Perlmutter) • `ed60afd` docs: Update page titles, section landing pages, and side TOC (#16760) (Ben Perlmutter) • `333c712` docs: add background to code-path-diagrams for dark-mode (#16822) (Tanuj Kanti) • `f5f7b9b` docs: Update README (GitHub Actions Bot) • `2aa4f5f` docs: no-constant-condition: Add multi-comparison example (#16776) (Sebastian Simon) • `40287db` docs: Remove Google Group icon (#16779) (Nicholas C. Zakas) • `ea10ca5` docs: 'a .eslint' -> 'an .eslint' for consistency (#16809) (Ben Perlmutter) • `3be0748` docs: add example for nodejs lintText api (#16789) (Siva K) • `ce4f5ff` docs: Replace removed related rules with a valid rule (#16800) (Ville Saalo) • 8.32.0 - 2023-01-15 Features • `fc20f24` feat: add suggestions for redundant wrapping in prefer-regex-literals (#16658) (YeonJuan) Bug Fixes • `b4f8329` fix: ignore directives for no-fallthrough (#16757) (gfyoung) Documentation • `17b65ad` docs: IA Update page URL move (#16665) (Ben Perlmutter) • `5981296` docs: fix theme switcher button (#16752) (Sam Chen) • `6669413` docs: deploy prerelease docs under the

/docs/next/

path (#16541) (Nitin Kumar) • `78ecfe0` docs: use inline code for rule options name (#16768) (Percy Ma) • `fc2ea59` docs: Update README (GitHub Actions Bot) • `762a872` docs: Update README (GitHub Actions Bot) Chores • `2952d6e` chore: sync templates/*.md files with issue templates (#16758) (gfyoung) • `3e34418` chore: Add new issues to triage project (#16740) (Nicholas C. Zakas) • 8.31.0 - 2022-12-31 Read more from eslint GitHub release notes Commit messages Package name: eslint • 13552c4 8.33.0 • ddeef02 Build: changelog update for 8.33.0 • 17f4be2 docs: Fix examples in no-multiple-empty-lines rule (#16835) • 9c7cfe3 docs: 'Source Code' content in 'Set up Development Environment' page (#16780) • ede5c64 docs: Custom processors page (#16802) • 2620614 docs: Code of Conduct page (#16781) • 50a8efd docs: report a sec vulnerability page (#16808) • 2cc7954 feat: add

restrictDefaultExports

option to no-restricted-exports rule (#16785) • <https://snyk.i… flyteorg/flyteconsole GitHub Actions: Build Flyteconsole Image / Push to Github Registry GitHub Actions: lint_project GitHub Actions: extract_branch GitHub Actions: unit_tests_with_coverage DCO: DCO ✅ 1 other check has passed 1/6 successful checks

#696 [Snyk] Upgrade eslint-plugin-react from 7.32.0 to 7.32.2 Pull request opened by EngHabu This PR was automatically created by Snyk using the credentials of a real user. Snyk has created this PR to upgrade eslint-plugin-react from 7.32.0 to 7.32.2. ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project. * * * • The recommended version is 2 versions ahead of your current version. • The recommended version was released a month ago, on 2023-01-29. Release notes Package name: eslint-plugin-react • 7.32.2 - 2023-01-29 Fixed • configs: restore

parserOptions

in legacy configs ([#3523][] @ ljharb) • </jsx-eslint/eslint-plugin-react/blob/v7.32.2/docs/rules/jsx-no-constructed-context-values.md|`jsx-no-constructed-context-values`>, </jsx-eslint/eslint-plugin-react/blob/v7.32.2/docs/rules/jsx-no-useless-fragment.md|`jsx-no-useless-fragment`>: add a rule schema (@ ljharb) ( </jsx-eslint/eslint-plugin-react/blob/v7.32.2/docs/rules/no-unknown-property.md|`no-unknown-property`>: add

fill

for

<marker>

(#3525 @ alexey-koran) • 7.32.1 - 2023-01-16 Fixed • prevent circular dependency in index and "all" config (#3519 @ ljharb) • </jsx-eslint/eslint-plugin-react/blob/v7.32.1/docs/rules/destructuring-assignment.md|`destructuring-assignment`>: do not force destructuring of optionally chained properties (#3520 @ ljharb) • 7.32.0 - 2023-01-11 Added • support new config system (#3429 @ jjangga0214) • </jsx-eslint/eslint-plugin-react/blob/v7.32.0/docs/rules/hook-use-state.md|`hook-use-state`>: add

allowDestructuredState

option (#3449 @ ljharb) • add </jsx-eslint/eslint-plugin-react/blob/v7.32.0/docs/rules/sort-default-props.md|`sort-default-props`> and deprecate </jsx-eslint/eslint-plugin-react/blob/v7.32.0/docs/rules/jsx-sort-default-props.md|`jsx-sort-default-props`> (#1861 @ alexzherdev) • add </jsx-eslint/eslint-plugin-react/blob/v7.32.0/docs/rules/no-object-type-as-default-prop.md|`no-object-type-as-default-prop`> rule (#2848 @ cyan33 @ fengkx) Fixed • configs: avoid legacy config system error (#3461 @ ljharb) • </jsx-eslint/eslint-plugin-react/blob/v7.32.0/docs/rules/sort-prop-types.md|`sort-prop-types`>: restore autofixing (#3452, #3471 @ ROSSROSALES) • </jsx-eslint/eslint-plugin-react/blob/v7.32.0/docs/rules/no-unknown-property.md|`no-unknown-property`>: do not check

fbs

elements (#3494 @ brianogilvie) • </jsx-eslint/eslint-plugin-react/blob/v7.32.0/docs/rules/jsx-newline.md|`jsx-newline`>: No newline between comments and jsx elements (#3493 @ justmejulian) • </jsx-eslint/eslint-plugin-react/blob/v7.32.0/docs/rules/jsx-no-leaked-render.md|`jsx-no-leaked-render`>: Don't report errors on empty strings if React >= v18 (#3488 @ himanshu007-creator) • </jsx-eslint/eslint-plugin-react/blob/v7.32.0/docs/rules/no-invalid-html-attribute.md|`no-invalid-html-attribute`>: convert autofix to suggestion (#3474 @ himanshu007-creator @ ljharb) • </jsx-eslint/eslint-plugin-react/blob/v7.32.0/docs/rules/jsx-no-leaked-render.md|`jsx-no-leaked-render`>: fix removing parentheses for conditionals (#3502 @ akulsr0) • </jsx-eslint/eslint-plugin-react/blob/v7.32.0/docs/rules/jsx-no-leaked-render.md|`jsx-no-leaked-render`>: invalid fixes in coerce mode (#3511 @ akulsr0) • </jsx-eslint/eslint-plugin-react/blob/v7.32.0/docs/rules/destructuring-assignment.md|`destructuring-assignment`>: Handle destructuring of useContext in SFC (#2797 @ Zinyon @ ljharb) Changed • [Docs] </jsx-eslint/eslint-plugin-react/blob/v7.32.0/docs/rules/jsx-no-leaked-render.md|`jsx-no-leaked-render`>: Remove mentions of empty strings for React 18 (#3468 @ karlhorky) • [Docs] update

eslint-doc-generator

to v1.0.0 (#3499 @ bmish) • [meta] add issue template (#3483 @ ROSSROSALES) • [Docs] Use emoji for jsx-runtime config and config file for eslint-doc-generator (#3504 @ bmish) • [Docs] </jsx-eslint/eslint-plugin-react/blob/v7.32.0/docs/rules/prefer-exact-props.md|`prefer-exact-props`>: fix example flow syntax (#3510 @ smackfu) • [Perf] use

anyOf

instead of

oneOf

(@ ljharb @ remcohaszing) from eslint-plugin-react GitHub release notes Commit messages Package name: eslint-plugin-react • 66b58dd Update CHANGELOG and bump version • <https://snyk.io/redirect/github/jsx-eslint/eslint-plugin-react/commit/373167c2494727c… flyteorg/flyteconsole GitHub Actions: Build Flyteconsole Image / Push to Github Registry GitHub Actions: extract_branch GitHub Actions: lint_project GitHub Actions: unit_tests_with_coverage DCO: DCO ✅ 1 other check has passed 1/6 successful checks

#697 [Snyk] Upgrade eslint-plugin-import from 2.27.4 to 2.27.5 Pull request opened by EngHabu This PR was automatically created by Snyk using the credentials of a real user. Snyk has created this PR to upgrade eslint-plugin-import from 2.27.4 to 2.27.5. ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project. * * * • The recommended version is 1 version ahead of your current version. • The recommended version was released a month ago, on 2023-01-16. Release notes Package name: eslint-plugin-import • 2.27.5 - 2023-01-16 v2.27.5 • 2.27.4 - 2023-01-12 v2.27.4 from eslint-plugin-import GitHub release notes Commit messages Package name: eslint-plugin-import • 5ff9e45 Bump to v2.27.5 • ee6e1be [Refactor] minor performance refactors • 3cb966e [Deps] update

array.prototype.flatmap

• 0778b03 [Fix] `order`: Fix group ranks order when alphabetizing • af8fd26 [eslint] configure

no-extraneous-dependencies

rule properly, to prevent today’s bugs Compare * * * Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs. For more information: https://camo.githubusercontent.com/34a6309d742a062eaad3fa475223904c1181e885be5ee7ce417a9f3ec7147b9a/68747470733a2f2f6170692e7365676d656e742e696f2f76312f706978656c2f747261636b3f646174613d65794a33636d6c305a55746c65534936496e4a79576d785a634564485932527954485a7362306c596430645563566734576b4652546e4e434f5545774969776959573576626e6c746233567a535751694f694a6d4e5467314e546b775a5330344e475a684c5451344f4451744f5445304d53307a5a574532596a55354e6a67354f574d694c434a6c646d567564434936496c425349485a705a58646c5a434973496e42796233426c636e52705a584d694f6e736963484a4a5a434936496d59314f4455314f54426c4c5467305a6d45744e4467344e4330354d5451784c544e6c59545a694e546b324f446b3559794a3966513d3d 🧐 View latest project report 🛠️ Adjust upgrade PR settings 🔕 Ignore this dependency or unsubscribe from future upgrade PRs flyteorg/flyteconsole GitHub Actions: Build Flyteconsole Image / Push to Github Registry GitHub Actions: lint_project GitHub Actions: extract_branch GitHub Actions: unit_tests_with_coverage DCO: DCO ✅ 1 other check has passed 1/6 successful checks

#698 [Snyk] Upgrade fork-ts-checker-webpack-plugin from 7.2.14 to 7.3.0 Pull request opened by EngHabu This PR was automatically created by Snyk using the credentials of a real user. Snyk has created this PR to upgrade fork-ts-checker-webpack-plugin from 7.2.14 to 7.3.0. ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project. * * * • The recommended version is 1 version ahead of your current version. • The recommended version was released 2 months ago, on 2023-01-10. Release notes Package name: fork-ts-checker-webpack-plugin • 7.3.0 - 2023-01-10 7.3.0 (2023-01-10) Features • add

formatter.pathType

option for absolute path (#792) (3ae3406), closes #789 • 7.2.14 - 2022-12-16 7.2.14 (2022-12-16) from fork-ts-checker-webpack-plugin GitHub release notes Commit messages Package name: fork-ts-checker-webpack-plugin • 3ae3406 feat: add

formatter.pathType

option for absolute path (#792) • 90ff881 chore(deps): bump json5 from 1.0.1 to 1.0.2 (#791) • 4eb03ec chore: blog.johnnyreilly.com (#790) • 9b67b6f chore(deps): bump minimatch from 3.0.4 to 3.0.5 (#788) Compare * * * Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs. For more information: https://camo.githubusercontent.com/0f76829aed30b96b44c9f8a68e1f9995034bb7451c53d3bdb91474b6607cb68e/68747470733a2f2f6170692e7365676d656e742e696f2f76312f706978656c2f747261636b3f646174613d65794a33636d6c305a55746c65534936496e4a79576d785a634564485932527954485a7362306c596430645563566734576b4652546e4e434f5545774969776959573576626e6c746233567a535751694f694a694e7a49345a5755354e5330324e4464684c54517a4d6d45744f4463784e6930324d6a426d5a6a49305a575577595751694c434a6c646d567564434936496c425349485a705a58646c5a434973496e42796233426c636e52705a584d694f6e736963484a4a5a434936496d49334d6a686c5a546b314c5459304e3245744e444d79595330344e7a45324c5459794d475a6d4d6a526c5a5442685a434a3966513d3d 🧐 View latest project report 🛠️ Adjust upgrade PR settings 🔕 Ignore this dependency or unsubscribe from future upgrade PRs flyteorg/flyteconsole GitHub Actions: extract_branch DCO: DCO ✅ 1 other check has passed 1/3 successful checks

#699 [Snyk] Upgrade tslib from 2.4.1 to 2.5.0 Pull request opened by EngHabu This PR was automatically created by Snyk using the credentials of a real user. Snyk has created this PR to upgrade tslib from 2.4.1 to 2.5.0. ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project. * * * • The recommended version is 1 version ahead of your current version. • The recommended version was released a month ago, on 2023-01-26. Release notes Package name: tslib • 2.5.0 - 2023-01-26 What's New • Fix asyncDelegator reporting done too early by @ apendua in #187 • Add support for TypeScript 5.0's

__esDecorate

and related helpers by @ rbuckton in #193 Full Changelog: 2.4.1...2.5.0 • 2.4.1 - 2022-10-31 This release contains fixes for early `return`s and `throw`s invoked on generators. from tslib GitHub release notes Commit messages Package name: tslib • e388a23 Merge pull request #194 from microsoft/bump-version-2.5 • b68d573 Bump package version to 2.5.0 • 62c5322 Add support for __esDecorate and related helpers (#193) • 3bdc002 Merge pull request #188 from microsoft/add-codeql • 697f430 try paths: . • 63319af add codeql • a549d39 Fix asyncDelegator reporting done too early (#187) Compare * * * Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs. For more information: https://camo.githubusercontent.com/957455870ced7578b2ba4481ab7a22808f16631fa50bdb11f6326933204b17a5/68747470733a2f2f6170692e7365676d656e742e696f2f76312f706978656c2f747261636b3f646174613d65794a33636d6c305a55746c65534936496e4a79576d785a634564485932527954485a7362306c596430645563566734576b4652546e4e434f5545774969776959573576626e6c746233567a535751694f694a6d4d446c6c4d5445334e4330344f546c6c4c54517a5a6d49744f44466a4d53316a4f4751335a6a4977595441324d446b694c434a6c646d567564434936496c425349485a705a58646c5a434973496e42796233426c636e52705a584d694f6e736963484a4a5a434936496d59774f5755784d5463304c5467354f5755744e444e6d596930344d574d784c574d345a44646d4d6a42684d4459774f534a3966513d3d 🧐 View latest project report 🛠️ Adjust upgrade PR settings 🔕 Ignore this dependency or unsubscribe from future upgrade PRs flyteorg/flyteconsole GitHub Actions: Build Flyteconsole Image / Push to Github Registry GitHub Actions: unit_tests_with_coverage GitHub Actions: lint_project GitHub Actions: extract_branch DCO: DCO ✅ 1 other check has passed 1/6 successful checks

#3392 Remove resource defaults for flyte-binary deployment in flyte-binary chart Pull request opened by jeevb flyteorg/flyte ✅ All checks have passed 12/12 successful checks

#3393 Update Flyte components Pull request opened by flyte-bot Updated flyte deployment • Updated GCP Flyte kustomize generated manifest file • Updated EKS Flyte kustomize generated manifest file • Updated Sandbox Flyte kustomize generated manifest file • Updated TEST Flyte kustomize generated manifest file • Updated GCP Flyte helm generated manifest file • Updated EKS Flyte helm generated manifest file • Updated Sandbox Flyte helm generated manifest file • Updated TEST Flyte helm generated manifest file • Auto-generated by [flyte-bot] flyteorg/flyte ✅ All checks have passed 12/12 successful checks

Release - v1.3.9 New release published by flyte-bot Changelog • 3674402 added dynamic_job_spec_uri to dynamic workflow metadata and node execution closure (#360) flyteorg/flyteidl

#377 Use TokenCache in ClientCredentialsTokenSourceProvider Pull request opened by andrewwdye TL;DR Modify

ClientCredentialsTokenSourceProvider

and

customTokenSource

to use

TokenCache

so that valid tokens can be reused across

TokenSourceProvider

instances. This is consistent with other providers. I considered refactoring FetchTokenFromCacheOrRefreshIt to share the implementation between client credentials and pkce tokens, but there are a few subtle differences between these token types that would have complicated this logic. Instead I kept the refresh logic the separate, as it is today. Type ☐ Bug Fix ☑︎ Feature ☐ Plugin Are all requirements met? ☑︎ Code completedx ☐ Smoke tested ☑︎ Unit tests added ☐ Code documentation added ☐ Any pending items have an associated Issue Complete description Replaced the existing

oauth2.Token

instance in

customerTokenSource

with a reference to the

TokenCache

originally passed to

NewTokenSourceProvider

. Overall logic stays the same. If we fail to save a new token to the cache we will warn but continue. Tracking Issue NA Follow-up issue NA flyteorg/flyteidl ✅ All checks have passed 22/22 successful checks

#532 Improve error message Pull request opened by pingsutw TL;DR Improve error message, so that we could know the expect type and input type when type mismatch. https://flyte-org.slack.com/archives/C045P7GBGBU/p1677805394589729?thread_ts=1677725600.349759&amp;cid=C045P7GBGBU 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 ^^^ 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 ✅ 10 other checks have passed 10/14 successful checks

1 new commit pushed to

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

by rafaelraposospot

<https://github.com/flyteorg/flytekit-java/commit/dc25731ef33be737c0cf9b981d81e53f16f1ba9e|dc25731e>

- Fix maven config (#203) flyteorg/flytekit-java

1 new commit pushed to

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

by rafaelraposospot

<https://github.com/flyteorg/flytekit-java/commit/5c82a2df37a7cbfcd8ecaf91b68f672199839f4b|5c82a2df>

- Make jib build (#200) 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/ec69cff990bf10bf4bd8928b75025fe7d27b8a7a|ec69cff9>

- [maven-release-plugin] prepare release 0.4.5 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/eab00ee9f4f60a359eb1624ace853d0cf03475a2|eab00ee9>

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

#205 Make jib build and push to v0.3 Pull request opened by rafaelraposospot TL;DR Make jib upload Docker image (v4 #200) 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 flyteorg/flytekit-java ✅ All checks have passed 3/3 successful checks

Release - 0.4.5 New release published by rafaelraposospot What's Changed • Literaltype as sdktype by @narape in #198 • Make Jib upload to GHCR by @rafaelraposospot in #200 flyteorg/flytekit-java

#3271 [Docs] Add new signaling functions/classes to API reference Issue created by cosmicBboy Description The

wait_for_input

,

approve

and

sleep

functions to use gate nodes in flytekit workflows need to be added to the API reference. • Add these functions to the module-level docstring for flytekit Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

#3287 [Docs] Update flytekit API reference configuration page: include flytectl config.yaml as source of configuration Issue created by cosmicBboy Description The configuration api reference does not mention that configuration for flytekit can come from the flytectl

config.yaml

file. Will need to update the docs to explain this. Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

Release - 0.3.31 New release published by rafaelraposospot Full Changelog: 0.3.30...0.3.31 flyteorg/flytekit-java

#3395 [BUG] FE: Structured data sets not working from launch form Issue created by jsonporter Describe the bug Users reported that launching a workflow does not work when using structured data sets. This feature was initially implemented in <405|https://github.com/flyteorg/flyte/issues/405> but is no longer working. Acceptance Criteria: • users can launch workflows using structured data sets. Expected behavior • users can launch workflows using structured data sets. 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

#700 fix: package version to 1.4.2 Pull request opened by jsonporter Small fix to revert package.json version back to 1.4 to prep for monorepo. 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 _Remove the '_fixes_' keyword if there will be multiple PRs to fix the linked issue_ fixes https://github.com/flyteorg/flyte/issues/ Follow-up issue NA OR https://github.com/flyteorg/flyte/issues/ flyteorg/flyteconsole GitHub Actions: Build Flyteconsole Image / Push to Github Registry GitHub Actions: unit_tests_with_coverage ✅ 4 other checks have passed 4/6 successful checks