fix: use configurable GPU resource name instead of hardcoded nvidia.com/gpu

.github/dco.yml

@@ -0,0 +1,5 @@
+require:
+  members: false
+allowRemediationCommits:
+  individual: true
+  thirdParty: true

.github/workflows/single-binary.yml

@@ -24,7 +24,7 @@ jobs:
       - name: golangci-lint
         uses: golangci/golangci-lint-action@v9
         with:
-          version: v2.6.2
+          version: v2.11.4
           working-directory: docker/sandbox-bundled/bootstrap
       - name: Check formatting
         working-directory: docker/sandbox-bundled/bootstrap

CHANGELOG/CHANGELOG-v1.16.6.md

@@ -0,0 +1,34 @@
+# Flyte 1.16.6
+
+## Added
+
+- docs: add comment about passwordPath usage in helm chart ([#6895](https://github.com/flyteorg/flyte/pull/6895))
+
+## Changed
+
+- Use retryable failure for failed Ray job deployments ([#7153](https://github.com/flyteorg/flyte/pull/7153))
+- Fix copilot TerminationGracePeriodSeconds set to nanoseconds instead of seconds ([#7183](https://github.com/flyteorg/flyte/pull/7183))
+- Fix: Correctly set 'child data dir/output dir' in branch handler's Abort and Finalize ([#7117](https://github.com/flyteorg/flyte/pull/7117))
+- Fix: Make flytectl hydrate pod template spec in task node overrides ([#7096](https://github.com/flyteorg/flyte/pull/7096))
+- fix(sandbox-bundled): Use a yaml string for FLYTE_PLATFORM_INSECURE ([#7079](https://github.com/flyteorg/flyte/pull/7079))
+- Fix: Allow toggling dynamic log links for Ray, Dask, Spark plugins ([#7193](https://github.com/flyteorg/flyte/pull/7193))
+- Fix type error for suspended kubeflow jobs ([#7241](https://github.com/flyteorg/flyte/pull/7241))
+
+## Dependencies / Security
+
+- Bump pygments from 2.18.0 to 2.20.0 in /flytectl/docs ([#7118](https://github.com/flyteorg/flyte/pull/7118))
+- Bump requests from 2.32.4 to 2.33.0 in /flytectl/docs ([#7095](https://github.com/flyteorg/flyte/pull/7095))
+- Bump github.com/go-jose/go-jose/v3 from 3.0.4 to 3.0.5 ([#7149](https://github.com/flyteorg/flyte/pull/7149))
+- Upgrade viper to v1.21.0 and fix case-sensitive key handling ([#7013](https://github.com/flyteorg/flyte/pull/7013))
+- Update to Go 1.25 ([#7201](https://github.com/flyteorg/flyte/pull/7201))
+- Bump the go_modules group across 10 directories with 3 updates ([#7216](https://github.com/flyteorg/flyte/pull/7216))
+- Bump the go_modules group across 5 directories with 2 updates ([#7228](https://github.com/flyteorg/flyte/pull/7228))
+- Bump the go_modules group across 4 directories with 1 update ([#7256](https://github.com/flyteorg/flyte/pull/7256))
+- Bump urllib3 from 2.6.0 to 2.6.3 in /flytectl/docs ([#6849](https://github.com/flyteorg/flyte/pull/6849))
+
+## New Contributors
+* @spwoodcock made their first contribution in https://github.com/flyteorg/flyte/pull/6895
+* @strigazi made their first contribution in https://github.com/flyteorg/flyte/pull/7241
+* @bergman made their first contribution in https://github.com/flyteorg/flyte/pull/7183
+
+**Full Changelog**: https://github.com/flyteorg/flyte/compare/v1.16.5...v1.16.6

CONTRIBUTING.md

@@ -1,15 +1,124 @@
 # Contributing to Flyte
 
-For information related to contributing to Flyte, please check out the [Contributing to Flyte](https://docs.flyte.org/en/latest/community/contribute/index.html) section of the documentation.
-
-## Recommendation Order (For Beginners)
-* Setup dev environment 
-* Read the following and run at least 5 examples. Pay close attention to the generated outputs, the Graph view, task  
-  logs, etc. Repeat with as many examples as you need to have an initial understanding of what an execution looks like:
-  * https://docs.flyte.org/en/latest/user_guide/introduction.html
-  * https://docs.flyte.org/en/latest/flytesnacks/userguide.html
-* Finish reading the [Concepts](https://docs.flyte.org/en/latest/user_guide/concepts/main_concepts/index.html)
-* Finish reading the [Control Plane](https://docs.flyte.org/en/latest/user_guide/concepts/control_plane/index.html)
-* Finish reading the [Component Architecture](https://docs.flyte.org/en/latest/user_guide/concepts/component_architecture/index.html)
-* Choose 2 good first issues from the following and start solving them with the knowledge you have read.
-* Familiar with using [ImageSpec to push images to localhost for development](https://docs.flyte.org/en/latest/user_guide/customizing_dependencies/imagespec.html#image-spec-example)
+First off, thanks for taking the time to contribute! ❤️
+
+All types of contributions are encouraged and valued. See the [Table of Contents](#table-of-contents) for different ways to help and details about how this project handles them. Please make sure to read the relevant section before making your contribution. It will make it a lot easier for the team and smooth out the experience for all involved. The community looks forward to your contributions. 🎉
+
+If you don't have time to contribute, that's fine. There are other easy ways to support the project and show your appreciation, which we would also be very happy about:
+
+- Star the project
+- Post on X or Linkedin about Flyte `#flyte
+- Mention the project at local meetups and tell your friends/colleagues
+
+## Table of Contents
+
+- [Code of Conduct](#code-of-conduct)
+- [I Have a Question](#i-have-a-question)
+- [I Want To Contribute](#i-want-to-contribute)
+    - [Code Contributors](#code-contributors)
+      - [Recommendation Order (For Beginners)](#recommendation-order-for-beginners)
+    - [Reporting Bugs](#reporting-bugs)
+    - [Feature Requests](#feature-requests)
+    - [Improving The Documentation](#improving-the-documentation)
+    - [Improving The Design](#improving-the-design)
+    - [Publish a Blog Post or Case Study](#publish-a-blog-post-or-case-study)
+    - [Commit Messages](#commit-messages)
+- [Pull requests](#pull-requests)
+- [Contributor Ladder](#contributor-ladder)
+
+## Code of Conduct
+
+This project and everyone participating in it is governed by the [Code of Conduct](https://github.com/flyteorg/flyte/blob/master/CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. Please report unacceptable behavior
+to [security@union.ai](mailto:security@union.ai).
+
+## I Have a Question
+
+If you need clarification after reading this document, we encourage you to join our [slack](https://slack.flyte.org/) workspace and join channels [#flyte-support](https://flyte-org.slack.com/archives/CP2HDHKE1) and [#contribute](https://flyte-org.slack.com/archives/C04NJPLRWUX) channel.
+
+## I Want To Contribute
+
+### Code Contributors
+
+We’re excited that you’re interested in contributing code to Flyte! Before you start, please take a look at our [Quickstart](https://www.union.ai/docs/v2/flyte/user-guide/quickstart/) docs, it includes setup instructions, build steps, and details on running your first workflow locally.
+
+#### Recommendation Order (For Beginners)
+
+- Finish reading [Core Concepts](https://www.union.ai/docs/v2/flyte/user-guide/core-concepts/)
+- Finish reading [Connecting a Cluster](https://www.union.ai/docs/v2/flyte/user-guide/connecting-to-a-cluster/)
+- Finish reading [Projects and Domain](https://www.union.ai/docs/v2/flyte/user-guide/projects-and-domains/) 
+- Finish reading [From Flyte 1 to Flyte 2](https://www.union.ai/docs/v2/flyte/user-guide/flyte-2/) 
+
+### Reporting Bugs
+
+Please use our issues templates that provide hints on what information we need to help you.
+
+> You must never report security related issues, vulnerabilities or bugs including sensitive information to the issue tracker, or elsewhere in public. Instead sensitive bugs must be sent by email to [security@union.ai](mailto:security@union.ai) or use the Report a security vulnerability issue template. 
+
+### Feature Requests
+
+Suggest an idea for the project by using the [Issues template](https://github.com/flyteorg/flyte/issues) and choose your desired option and kindly provide as much context as you can about what you're running into. Do not open issues for questions or support, instead join our [slack workspace](https://slack.flyte.org/) and ask there.
+
+Unsure if your contribution is “small”, “large” or whether it fits into the project's goal? Kindly start a quick [discussion](https://github.com/flyteorg/flyte/discussions) on github.
+
+### Improving The Documentation
+
+If you notice outdated information or areas that could be clarified, kindly start a discussion in the [contribute](https://flyte-org.slack.com/archives/C04NJPLRWUX) channel on slack. For more information, please checkout [Contributing to documentation](https://www.union.ai/docs/v2/flyte/community/#contributing-to-documentation).
+
+### Improving The Design
+
+Design contributions are welcome! To ensure smooth collaboration, please use the UI Feature Request Template when opening a design-related issue. This helps us gather the right context (such as wireframes, mockups, or visual references) and maintain a consistent design language across the project. Feedback and iterations are highly encouraged, design is always a shared process.
+
+### Publish a Blog Post or Case Study
+
+We love hearing how people use or extend Flyte in their own projects. If you’ve written about your experience, we’re happy to review it! To share your work, please start a discussion in the [#contribute](https://flyte-org.slack.com/archives/C04NJPLRWUX) channel on slack, summarizing your post or case study, with a link to the full content.
+
+### Commit Messages
+
+Writing clear and consistent commit messages helps maintainers understand the purpose of your changes. A good commit message should:
+
+- Be written in the present tense (e.g., Add new feature, not Added new feature)
+
+- Be short (50 characters or less for the summary line)
+
+- Include additional context in the body if needed
+
+- Reference related issue numbers (e.g., Fixes `#123)
+
+- Keep each commit focused on one logical change
+
+## Pull Requests
+
+When you’re ready to contribute your changes, follow these steps to create a clear and reviewable pull request:
+
+- Push your changes to your fork:
+
+    ```bash
+    git push origin your-branch-name
+    ```
+
+- Open a Pull Request against the main Flyte Code repository.
+
+- Select "Compare across forks" and choose your fork and branch.
+
+- Fill out the PR template with:
+
+- A clear description of your changes
+
+    - Any related issues (e.g., “changed `#123”). 
+
+    - Testing steps or screenshots (if applicable)
+
+    - Notes for reviewers, if special attention is needed.
+
+For more context, kindly read the official [Before Submitting Your PR](https://www.union.ai/docs/v1/flyte/community/contributing-code/#before-submitting-your-pr) docs.
+
+## Contributor Ladder
+
+The Flyte Contributor Ladder is a key resource for understanding how to grow within Flyte, outlining expectations, responsibilities, and progression across roles. It helps create transparency, recognize contributions, and ensure a sustainable and inclusive path for community members to deepen their impact. [Read more](https://github.com/flyteorg/community/blob/main/GOVERNANCE.md#community-roles-and-path-to-maintainership).
+
+
+Your contributions, big or small help make Flyte better for everyone!🫶
+
+## References
+
+This document was adapted from [https://contributing.md](https://contributing.md/)!

Dockerfile

@@ -2,7 +2,7 @@ ARG FLYTECONSOLE_VERSION=latest
 FROM ghcr.io/flyteorg/flyteconsole:${FLYTECONSOLE_VERSION} AS flyteconsole
 
 
-FROM --platform=${BUILDPLATFORM} golang:1.25-bookworm AS flytebuilder
+FROM --platform=${BUILDPLATFORM} golang:1.26-bookworm AS flytebuilder
 
 ARG TARGETARCH
 ENV GOARCH="${TARGETARCH}"

Dockerfile.datacatalog

@@ -3,7 +3,7 @@
 #
 # TO OPT OUT OF UPDATES, SEE https://github.com/flyteorg/boilerplate/blob/master/Readme.rst
 
-FROM --platform=${BUILDPLATFORM} golang:1.25-alpine3.21 AS builder
+FROM --platform=${BUILDPLATFORM} golang:1.26-alpine3.23 AS builder
 
 
 ARG TARGETARCH

Dockerfile.flyteadmin

@@ -3,7 +3,7 @@
 #
 # TO OPT OUT OF UPDATES, SEE https://github.com/lyft/boilerplate/blob/master/Readme.rst
 
-FROM --platform=${BUILDPLATFORM} golang:1.25-alpine3.21 AS builder
+FROM --platform=${BUILDPLATFORM} golang:1.26-alpine3.23 AS builder
 
 ARG TARGETARCH
 ENV GOARCH="${TARGETARCH}"

Dockerfile.flytecopilot

@@ -3,7 +3,7 @@
 #
 # TO OPT OUT OF UPDATES, SEE https://github.com/lyft/boilerplate/blob/master/Readme.rst
 
-FROM --platform=${BUILDPLATFORM} golang:1.25-alpine3.21 AS builder
+FROM --platform=${BUILDPLATFORM} golang:1.26-alpine3.23 AS builder
 
 
 ARG TARGETARCH

Dockerfile.flytepropeller

@@ -4,7 +4,7 @@
 # TO OPT OUT OF UPDATES, SEE https://github.com/lyft/boilerplate/blob/master/Readme.rst
 
 
-FROM --platform=${BUILDPLATFORM} golang:1.25-alpine3.21 AS builder
+FROM --platform=${BUILDPLATFORM} golang:1.26-alpine3.23 AS builder
 
 
 ARG TARGETARCH

Dockerfile.flytescheduler

@@ -4,7 +4,7 @@
 # TO OPT OUT OF UPDATES, SEE https://github.com/lyft/boilerplate/blob/master/Readme.rst
 
 
-FROM --platform=${BUILDPLATFORM} golang:1.25-alpine3.21 AS builder
+FROM --platform=${BUILDPLATFORM} golang:1.26-alpine3.23 AS builder
 
 
 ARG TARGETARCH

README.md

@@ -1,8 +1,9 @@
 > [!IMPORTANT]
 > ## Looking for Flyte 2?
 >
-> - **Use Flyte locally?** Head to **[flyte-sdk](https://github.com/flyteorg/flyte-sdk)** — the new Python SDK for Flyte 2.
-> - **Want to contribute to the distributed backend?** See the **[`v2` branch](https://github.com/flyteorg/flyte/tree/v2)** of this repo.
+> - **⭐️ Flyte 2 Devbox is now available!** Check out the guide [here](https://www.union.ai/docs/v2/flyte/user-guide/run-modes/running-devbox/)
+> - **Use Flyte 2 locally?** Head to **[flyte-sdk](https://github.com/flyteorg/flyte-sdk)** — the new Python SDK for Flyte 2.
+> - **Want to contribute to the Flyte 2 distributed backend?** See the **[`main` branch](https://github.com/flyteorg/flyte/tree/main)** of this repo.
 >
 > **The README below is for Flyte 1.x.**
 
@@ -119,7 +120,7 @@ Go to the [Deployment guide](https://docs.flyte.org/en/latest/deployment/deploym
 🧬 **Data lineage**: Track the movement and transformation of data throughout the lifecycle of your data and ML workflows. <br />
 📊 **Map tasks**: Achieve parallel code execution with minimal configuration using [map tasks](https://docs.flyte.org/en/latest/user_guide/advanced_composition/map_tasks.html). <br />
 🌎 **Multi-tenancy**: Multiple users can share the same platform while maintaining their own distinct data and configurations. <br />
-🌟 **Dynamic workflows**: [Build flexible and adaptable workflows](https://docs.flyte.org/en/latest/user_guide/advanced_composition/dynamic_workflows.html) that can change and evolve as needed, making it easier to respond to changing requirements. <br />
+🌟 **Dynamic workflows**: [Build flexible and adaptable workflows](https://www.union.ai/docs/v1/flyte/user-guide/core-concepts/workflows/dynamic-workflows) that can change and evolve as needed, making it easier to respond to changing requirements. <br />
 ⏯️ [Wait](https://docs.flyte.org/en/latest/user_guide/advanced_composition/waiting_for_external_inputs.html) for **external inputs** before proceeding with the execution. <br />
 🌳 **Branching**: [Selectively execute branches](https://docs.flyte.org/en/latest/user_guide/advanced_composition/conditionals.html) of your workflow based on static or dynamic data produced by other tasks or input data. <br />
 📈 **Data visualization**: Visualize data, monitor models and view training history through plots. <br />