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/1dcb81813585e6217a4321bbaa1add16aa0249b3|1dcb8181>

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

1 new commit pushed to

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

by eapolinario

<https://github.com/flyteorg/flytekit/commit/ae23ddb85c8a472fa31f34b2ea35454cd4656803|ae23ddb8>

- Pyflyte run workflows correctly handles Optional[TYPE] = None (#1849) flyteorg/flytekit

#618 Upgrade coreos/go-oidc to v3 to pickup claims parsing fixes Pull request opened by EngHabu TL;DR Reference conversation 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/flyteadmin GitHub Actions: Build & Push Flytescheduler Image GitHub Actions: Build & Push Flyteadmin Image GitHub Actions: Goreleaser GitHub Actions: Bump Version Codecov: 58.99% (-0.04%) compared to af81751 ✅ 9 other checks have passed 9/14 successful checks

20 new commits pushed to

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

by eapolinario

<https://github.com/flyteorg/flyte/commit/9dec0ced8bb9c5100434b5779b345b7101e1b176|9dec0ced>

- Update boilerplate version (#605)

<https://github.com/flyteorg/flyte/commit/45a095e3e844fd8f771a028d325f3daf280e8025|45a095e3>

- Bump flytestdlib version (#404)

<https://github.com/flyteorg/flyte/commit/35ae1b49e01104b084ed5a08884d4c8d0ed7348a|35ae1b49>

- Create a FileOutput reader if the agent produce file output (#391)

<https://github.com/flyteorg/flyte/commit/8caf7dd6c97dc5778b86206c4265156a921b4319|8caf7dd6>

- Bump flytestdlib version (#619)

<https://github.com/flyteorg/flyte/commit/7bd98a9a137375a4d514f0ae6615fdacbc32d19f|7bd98a9a>

- GPU Type (#419)

<https://github.com/flyteorg/flyte/commit/965f86130c65835a08a736c0863b912fb367d990|965f8613>

- [flyteidl] Support attribute access on promises (#439)

<https://github.com/flyteorg/flyte/commit/d740c7b8739908b5ad34e07e2d9971e5ef435baf|d740c7b8>

- Add supportTaskTypes for agentservice without write it in config twice. (#398)

<https://github.com/flyteorg/flyte/commit/d38e89209fcfe0df949d656453b13499c14401db|d38e8920>

- Add supportTaskTypes for agentservice without write it in config twice. (#612)

<https://github.com/flyteorg/flyte/commit/66e7b642262b2ca35d98e578a07fb867999d9b44|66e7b642>

- Add ray dashboard log link (#405)

<https://github.com/flyteorg/flyte/commit/7582ad0540c0cf6466af0daa095399779bb3878a|7582ad05>

- Revert "GPU Type (#419)" (#444)

<https://github.com/flyteorg/flyte/commit/290bd1a12e4187128332dca26bec76dc1f421564|290bd1a1>

- Merge remote-tracking branch 'eapolinario-flyteadmin/prepare-for-monorepo--v1.1.129' into monorepo--bump-components-versions

<https://github.com/flyteorg/flyte/commit/2cb93ed41d08d7b2e0abe19afa66b1ab90ceffbd|2cb93ed4>

- Lint flyteadmin/auth/handlers_test.go

<https://github.com/flyteorg/flyte/commit/ffd88fe7673ece685a030eb4f424cb5fc972c142|ffd88fe7>

- Merge remote-tracking branch 'eapolinario-flytestdlib/prepare-for-monorepo--v1.0.24' into monorepo--bump-components-versions

<https://github.com/flyteorg/flyte/commit/a218a0b683f9f77a77c7bf2e36d285831cdce41b|a218a0b6>

- Merge remote-tracking branch 'eapolinario-flyteplugins/prepare-for-monorepo--v1.1.30' into monorepo--bump-components-versions

<https://github.com/flyteorg/flyte/commit/e4aa18100be371a89ab9fa75e38174808b6544cc|e4aa1810>

- Fix flyteplugins lint errors

<https://github.com/flyteorg/flyte/commit/624d1b3f24b57fe03c74c49e97de186e9ac5430b|624d1b3f>

- Merge remote-tracking branch 'eapolinario-flyteidl/prepare-for-monorepo--v1.5.20' into monorepo--bump-components-versions

<https://github.com/flyteorg/flyte/commit/0879db55f143abb4a77b5da0178677514345e1a4|0879db55>

- Merge remote-tracking branch 'eapolinario-datacatalog/prepare-for-monorepo--v1.0.54' into monorepo--bump-components-versions

<https://github.com/flyteorg/flyte/commit/78d83bc8c63c649f7843a4b81ae7896043e40553|78d83bc8>

- Merge remote-tracking branch 'eapolinario-flytepropeller/prepare-for-monorepo--v1.1.126' into monorepo--bump-components-versions

<https://github.com/flyteorg/flyte/commit/28b55a5101fd309e8dcb20e25e11d96bbd08a5bd|28b55a51>

- Fix typo in flyteplugins/go/tasks/plugins/k8s/dask/dask.go

<https://github.com/flyteorg/flyte/commit/b59c0833884c21cfdc236c46e1bd1c091e0be92a|b59c0833>

- Merge pull request #4072 from flyteorg/monorepo--bump-components-versions-1.10 flyteorg/flyte

#4074 Add bump git tags workflow Pull request opened by eapolinario Describe your changes This PR adds a github workflow to bump the patch version of all necessary git tags (as described in https://go.dev/ref/mod#vcs-version). This is necessary so that downstream golang repositories can update to specific versions of components. In terms of the mechanics of the gh workflow, on merges to master we bump the patch version of the latest tag and we use that version create tags for each component. For example, let's say that the we're updating to version v1.9.1, this is going to create 7 tags: • v1.9.1 • datacatalog/v1.9.1 • flyteadmin/v1.9.1 • flytecopilot/v1.9.1 • flyteplugins/v1.9.1 • flytepropeller/v1.9.1 • flytestdlib/v1.9.1 I also took the chance to improve the fork-ability of the flyte repo. I also tested these changes on a fork. A subsequent change is going to modify the release scripts. flyteorg/flyte GitHub Actions: Integration Test (flyteadmin) / Integration tests ✅ 29 other checks have passed 29/30 successful checks

1 new commit pushed to

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

by eapolinario

<https://github.com/flyteorg/flyte/commit/8090b160596e3854c4b7ba77b4012bc72f7eb2fa|8090b160>

- Add bump git tags workflow (#4074) flyteorg/flyte

#603 Artifact partitioned Pull request opened by wild-endeavor on <!date^1692649758^{date_short}|2023-08-21T20:29:18Z> Read then delete this section - Make sure to use a concise title for the pull-request. _- Use #patch, #minor or #major in the pull-request title to bump the corresponding version. Otherwise, the patch version will be bumped. More details_ TL;DR Please replace this text with a description of what this PR accomplishes. 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/flyteadmin ✅ All checks have passed 2/2 successful checks

#572 Dataset events Pull request opened by wild-endeavor on <!date^1685723580^{date_short}|2023-06-02T16:33:00Z> Read then delete this section - Make sure to use a concise title for the pull-request. _- Use #patch, #minor or #major in the pull-request title to bump the corresponding version. Otherwise, the patch version will be bumped. More details_ TL;DR Please replace this text with a description of what this PR accomplishes. 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/flyteadmin GitHub Actions: Goreleaser GitHub Actions: Build & Push Flyteadmin Image GitHub Actions: Build & Push Flytescheduler Image GitHub Actions: Bump Version GitHub Actions: End2End Test GitHub Actions: Integration Test GitHub Actions: Lint / Run Lint GitHub Actions: Docker Build Images / Build Docker Image GitHub Actions: Unit Tests / Run Unit Test GitHub Actions: Check Go Generate / Go Generate ✅ 2 other checks have passed 2/12 successful checks

#408 Artifacts Pull request opened by wild-endeavor on <!date^1684871437^{date_short}|2023-05-23T19:50:37Z> Read then delete this section - Make sure to use a concise title for the pull-request. _- Use #patch, #minor or #major in the pull-request title to bump the corresponding version. Otherwise, the patch version will be bumped. More details_ TL;DR Please replace this text with a description of what this PR accomplishes. 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/flyteidl DCO: DCO ✅ 1 other check has passed 1/2 successful checks

#619 Artifact handling Pull request opened by wild-endeavor on <!date^1695754051^{date_short}|2023-09-26T18:47:31Z> This PR is a WIP. flyteorg/flyteadmin DCO: DCO ✅ 1 other check has passed 1/2 successful checks

#1852 update codecov config in pythonbuild ci Pull request opened by cosmicBboy TL;DR Fix codecov issue 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 ✅ All checks have passed 30/30 successful checks

#4078 Remove private repos Pull request opened by wild-endeavor flyteorg/flyte GitHub Actions: build-and-push-sandbox-bundled-image GitHub Actions: sandbox-bundled-functional-tests GitHub Actions: docs GitHub Actions: generate_helm ✅ 8 other checks have passed 8/12 successful checks

#4079 [Core feature] Sagemaker Agent Issue created by pingsutw Motivation: Why do you think this is important? This agent can used to submit the training or serving jot to AWS sagemaker. It allows people to easily run SageMaker training in a Flyte workflow. Currently, we have sagemaker backend plugin to submit the job, but the code it outdated, and doesn't work for now. We can write an agent in Python for Sagemaker, and it will be easy to maintain as well. Goal: What should the final outcome look like, ideally? We'll able to submit a training job by leveraging agent. Describe alternatives you've considered NA Propose: Link/Inline OR Additional context • Writing Agents in Python • flyteorg/flytekit#1797 Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

#4080 [Core feature] Chain tasks locally Issue created by pingsutw Motivation: Why do you think this is important? Chaining tasks doesn't work locally. In below example, t3 will be executed first instead t1. We should add an executor in Flytekit; it can schedule and run the task in the proper order.

@workflow
def my_wf():
    t3 = task_a()
    t2 = task_b()
    t1 = task_c()

    t1 >> t2 >> t3

Goal: What should the final outcome look like, ideally? Chaining tasks should work locally Describe alternatives you've considered NA Propose: Link/Inline OR Additional context 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/flytekit/tree/master|master>

by pingsutw

<https://github.com/flyteorg/flytekit/commit/cd9ec18f1959df46ea99046ebdbbab4b9715c688|cd9ec18f>

- Bump gitpython (#1828) flyteorg/flytekit

1 new commit pushed to

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

by pingsutw

<https://github.com/flyteorg/flytekit/commit/6dd29274f988a920a831115ba460a9131eb0b6a4|6dd29274>

- Bump cryptography (#1844) flyteorg/flytekit

#4081 [Core feature] Rust Data Persistence Issue created by pingsutw Motivation: Why do you think this is important? Write a Rust plugin to read/write s3 files. It can replace current data persistence plugin in flytekit. Goal: What should the final outcome look like, ideally? The Rust plugin should offer better data read/write performance than the current one Describe alternatives you've considered Use existing data persistence plugin. Propose: Link/Inline OR Additional context https://docs.rs/object_store/latest/object_store/ Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

#1853 Test codecov Pull request opened by pingsutw TL;DR Please replace this text with a description of what this PR accomplishes. 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 (windows-latest, 3.11) GitHub Actions: build (windows-latest, 3.8) GitHub Actions: build (ubuntu-latest, 3.11) GitHub Actions: lint GitHub Actions: build (ubuntu-latest, 3.8) GitHub Actions: docs GitHub Actions: Docs Warnings ✅ 4 other checks have passed 4/11 successful checks

#4082 [Monorepo] Update manifest using the monorepo components Pull request opened by eapolinario Describe your changes This PR changes the generation of manifests to use the versions of components in the monorepo. A few things to note: 1. This process relies on the fact that changes to components trigger the creation of tags once they are merged to master. This essentially means that two consecutive releases are not supported since component tags are only generated once changes to components are merged to master. We might need to relax this constraint and assume that all merges to master produce component tags. 2. In order to generate the config docs we no longer download component binaries from releases, instead we compile them in place. 3. The release process described in https://github.com/flyteorg/flyte/blob/master/RELEASE.md#create-a-release stays unchanged. flyteorg/flyte GitHub Actions: Build & Push Image GitHub Actions: Bump git tags Codecov: 58.94% (-0.02%) compared to 8090b16 ✅ 27 other checks have passed 27/30 successful checks

1 new commit pushed to

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

by cosmicBboy

<https://github.com/flyteorg/flytekit/commit/6da8ec443b0a769df84c1b5446277a3c3d0ae34a|6da8ec44>

- update codecov config in pythonbuild ci (#1852) flyteorg/flytekit

1 new commit pushed to

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

by eapolinario

<https://github.com/flyteorg/flyte/commit/8c05f4eaf13d73cb1228992e7f19704c70417c9c|8c05f4ea>

- [Monorepo] Update manifest using the monorepo components (#4082) flyteorg/flyte

1 new commit pushed to

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

by pingsutw

<https://github.com/flyteorg/flytekit/commit/de8a5fe7f7e249785c28edfb0ca206e0f12b85f0|de8a5fe7>

- Improved gate node handling (#1850) flyteorg/flytekit

#1854 update codecov yaml, make eager wf test more stable Pull request opened by cosmicBboy Update codecov config to ignore with correct key name, make eager wf unit tests more stable flyteorg/flytekit GitHub Actions: build-plugins (3.11, flytekit-sqlalchemy) GitHub Actions: build-plugins (3.11, flytekit-snowflake) GitHub Actions: build-plugins (3.11, flytekit-polars) GitHub Actions: build-plugins (3.11, flytekit-papermill) GitHub Actions: build-plugins (3.11, flytekit-pandera) GitHub Actions: build-plugins (3.11, flytekit-kf-tensorflow) GitHub Actions: build-plugins (3.11, flytekit-kf-pytorch) GitHub Actions: build-plugins (3.11, flytekit-kf-mpi) GitHub Actions: build-plugins (3.11, flytekit-k8s-pod) GitHub Actions: build-plugins (3.11, flytekit-huggingface) GitHub Actions: build-plugins (3.11, flytekit-hive) GitHub Actions: build-plugins (3.11, flytekit-envd) GitHub Actions: build-plugins (3.11, flytekit-duckdb) GitHub Actions: build-plugins (3.11, flytekit-dolt) GitHub Actions: build-plugins (3.11, flytekit-deck-standard) GitHub Actions: build-plugins (3.11, flytekit-dbt) GitHub Actions: build-plugins (3.11, flytekit-data-fsspec) GitHub Actions: build-plugins (3.11, flytekit-dask) GitHub Actions: build-plugins (3.11, flytekit-bigquery) GitHub Actions: build-plugins (3.11, flytekit-aws-sagemaker) GitHub Actions: build-plugins (3.11, flytekit-aws-batch) GitHub Actions: build-plugins (3.11, flytekit-aws-athena) GitHub Actions: build-plugins (3.8, flytekit-whylogs) GitHub Actions: build-plugins (3.8, flytekit-vaex) GitHub Actions: build-plugins (3.8, flytekit-sqlalchemy) GitHub Actions: build-plugins (3.8, flytekit-spark) GitHub Actions: build-plugins (3.8, flytekit-snowflake) GitHub Actions: build-plugins (3.8, flytekit-ray) GitHub Actions: build-plugins (3.8, flytekit-polars) GitHub Actions: build-plugins (3.8, flytekit-papermill) ✅ No checks have passed 0/30 successful checks

#4083 Update release script Pull request opened by pingsutw Tracking issue

release.sh

should update flyte agent's version as well. 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 GitHub Actions: generate_kustomize GitHub Actions: generate_helm GitHub Actions: publish-development-helm-chart (flyteagent) GitHub Actions: docs GitHub Actions: trigger-sandbox-lite-build GitHub Actions: publish-development-helm-chart (flyte-core) GitHub Actions: trigger-sandbox-build GitHub Actions: publish-development-helm-chart (flyte-binary) GitHub Actions: compile GitHub Actions: Check for spelling errors GitHub Actions: compile GitHub Actions: generate_kustomize GitHub Actions: publish-development-helm-chart (flyteagent) GitHub Actions: trigger-sandbox-lite-build GitHub Actions: publish-development-helm-chart (flyte-core) GitHub Actions: docs GitHub Actions: publish-development-helm-chart (flyte-binary) GitHub Actions: trigger-sandbox-build GitHub Actions: generate_helm GitHub Actions: Check for spelling errors ✅ 2 other checks have passed 2/22 successful checks

#3184 [Core feature] Add a new state called CreatingCluster Issue created by pingsutw Motivation: Why do you think this is important? Some tasks like Ray and Spark on Databricks will create an ephemeral cluster before running the task. Adding a

ClusterCreating

state for tasks would be helpful for people to know what's going on underneath. It is also much easier to debug if an operator fails to create a new cluster. In addition, cluster creation time and current task running time can be measured.it Goal: What should the final outcome look like, ideally? Users will know Flyte is creating a cluster when the node is stared Describe alternatives you've considered NA Propose: Link/Inline OR Additional context No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

#3186 [FlyteCTL Feature] Make default output of `flytectl config init` consistent with the demo sandbox config Issue created by cosmicBboy Describe the feature/command for FlyteCTL Currently, the output of

flytectl config init

is:

admin:
  # For GRPC endpoints you might want to use dns:///flyte.myexample.com
  endpoint: dns:///localhost:30081
  authType: Pkce
  insecure: true
logger:
  show-source: true
  level:

But the config produced by

flytectl demo start

is:

admin:
  # For GRPC endpoints you might want to use dns:///flyte.myexample.com
  endpoint: localhost:30080
  authType: Pkce
  insecure: true
console:
  endpoint: <http://localhost:30080>
logger:
  show-source: true
  level: 0

This may be confusing for new users who would expect the two configs to be consistent Provide a possible output or UX example The output of of

flytectl config init

should be the same as

config-sandbox.yaml

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

#1147 use eval-rst for tags to prevent showing up on sidebar Pull request opened by cosmicBboy Using the

eval-rst

directive prevents tags with the same name as pages will prevent the

Example Tags

sidebar from showing up: flyteorg/flytesnacks GitHub Actions: Build & Push Example Image to GHCR (examples/feast_integration) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (examples/data_types_and_io) GitHub Actions: Build & Push Example Image to GHCR (examples/exploratory_data_analysis) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (examples/customizing_dependencies) GitHub Actions: Build & Push Example Image to GHCR (examples/duckdb_plugin) GitHub Actions: Build & Push Example Image to GHCR (examples/dolt_plugin) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (examples/blast) GitHub Actions: Build & Push Example Image to GHCR (examples/development_lifecycle) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (examples/bigquery_plugin) GitHub Actions: Build & Push Example Image to GHCR (examples/dbt_plugin) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (examples/basics) GitHub Actions: Build & Push Example Image to GHCR (examples/databricks_plugin) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (examples/aws_batch_plugin) GitHub Actions: Build & Push Example Image to GHCR (examples/data_types_and_io) GitHub Actions: Build & Push Example Image to GHCR (examples/customizing_dependencies) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (examples/athena_plugin) GitHub Actions: Build & Push Example Image to GHCR (examples/blast) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (examples/advanced_composition) GitHub Actions: Build & Push Example Image to GHCR (examples/bigquery_plugin) GitHub Actions: Build & Push Example Image to GHCR (examples/basics) GitHub Actions: Build & Push Example Image to GHCR (examples/aws_batch_plugin) GitHub Actions: Build & Push Example Image to GHCR (examples/athena_plugin) GitHub Actions: Build & Push Example Image to GHCR (examples/advanced_composition) GitHub Actions: e2e-tests GitHub Actions: lint (3.11) GitHub Actions: Create a list of example packages GitHub Actions: Docs Warnings GitHub Actions: Create a list of example packages GitHub Actions: lint (3.11) GitHub Actions: e2e-tests ✅ No checks have passed 0/30 successful checks

#4084 Update release script Pull request opened by pingsutw Tracking issue

release.sh

should update flyte agent's version as well. 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 GitHub Actions: generate_helm ✅ 11 other checks have passed 11/12 successful checks

#4085 move memverge doc Pull request opened by helenzhangyc Tracking issue 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 2/2 successful checks

#4086 Run tests in both runners Pull request opened by eapolinario Experimenting with running CI checks in both runners. flyteorg/flyte GitHub Actions: Build & Push Image GitHub Actions: Bump git tags GitHub Actions: Check Go Generate (flytepropeller) / Go Generate (union-k8s-runner) GitHub Actions: Check Go Generate (flytecopilot) / Go Generate (union-k8s-runner) GitHub Actions: Check Go Generate (flyteadmin) / Go Generate (union-k8s-runner) GitHub Actions: Unit Tests (flyteplugins) / Run Unit Test (union-k8s-runner) GitHub Actions: Unit Tests (flytecopilot) / Run Unit Test (union-k8s-runner) GitHub Actions: Unit Tests (datacatalog) / Run Unit Test (union-k8s-runner) GitHub Actions: Lint (flytepropeller) / Run Lint (union-k8s-runner) GitHub Actions: Lint (flyteidl) / Run Lint (union-k8s-runner) ✅ 20 other checks have passed 20/30 successful checks