1 new commit pushed to

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

by wild-endeavor

<https://github.com/flyteorg/flytekit/commit/47be97412bdfd90e084dabb970ca587b202538ad|47be9741>

- Pass verify flag to all authenticators (#1641) flyteorg/flytekit

#3703 [BUG] Parent dynamic task registered in non-fast mode, child subtask registered in fast mode. Child subtask executes in non-fast mode. Issue created by redartera Describe the bug The task

foo

is registered in fast mode, while

bar

is registered in non-fast mode. The subtask

foo

is executed with

pyflyte-execute

rather than

pyflyte-fast-execute

when called from within

bar

, causing

ModuleNotFoundError

.

# a.py
@task
def foo(x: int) -> int:
  return x

# This task foo was registered in fast registration
 
# b.py

@reference_task(
  project="flytesnacks",
  domain="development",
  name="a.foo",
  version="v0.1.0",
)
def foo(x: int) -> int:
  ...

@dynamic(image="...")
def bar(x: int) -> int:
  for i in range(10):
   foo(x)

# This task bar was registered in non-fast mode

Expected behavior

foo

should be executed with

pyflyte-fast-execute

. Additional context to reproduce flytekit==1.4.2 and using

flyte-binary

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

#767 wip: simple way to audit npm package licenses Pull request opened by FrankFlitton TL;DR Generates a file to produce a summary of licenses used within the project. 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 Added a

licenses

script to

package.json

. It prints a 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 & Push FlyteConsole Image GitHub Actions: Get Release Tag GitHub Actions: Generate Release WIP: Title contains "wip" ✅ 5 other checks have passed 5/9 successful checks

1 new commit pushed to

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

by jsonporter

<https://github.com/flyteorg/flyteconsole/commit/c69f010959a2d854bac7a694baf5e5a635aeae8b|c69f0109>

- Feature: Fullview Flyte Deck modal (#764) flyteorg/flyteconsole

#2774 [UI Feature] Make Flyte Deck modal expandable Issue created by hankfanchiu Motivation: Why do you think this is important? We're using Flyte Deck to render static Jupyter notebooks serving as data reports. Given the current size of the Flyte Deck modal, some long notebook paragraphs are difficult to view. Goal: What should the final outcome look like, ideally? The Flyte Deck modal should be enlarged, perhaps scaled based on the viewport size while having the existing dimensions as the minimum. 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/06fffc786edfe9d4cbb891d6c0e14181a5823998|06fffc78>

- Allow annotated FlyteFile as task input argument (#1632) flyteorg/flytekit

#991 Use flytekit 1.6 in core image Pull request opened by eapolinario The version of

s3fs

in the core image was outdated. We set a lower-bound in flyteorg/flytekit@4251751, but that only went out in flytekit 1.6.0, so let's use latest flytekit. flyteorg/flytesnacks GitHub Actions: Serialize & Register Flytesnacks workflow / Register example to sandbox GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/kubernetes/ray_example) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/kubernetes/pod) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/kubernetes/kftensorflow) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/kubernetes/kfpytorch) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/kubernetes/kfmpi) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/kubernetes/k8s_spark) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/kubernetes/k8s_dask) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/flytekit_plugins/whylogs_examples) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/flytekit_plugins/sql) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/flytekit_plugins/papermilltasks) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/flytekit_plugins/pandera_examples) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/flytekit_plugins/onnx_examples) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/flytekit_plugins/modin_examples) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/flytekit_plugins/mlflow_example) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/core) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/case_studies/ml_training/spark_horovod) ✅ 13 other checks have passed 13/30 successful checks

1 new commit pushed to

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

by eapolinario

<https://github.com/flyteorg/flytesnacks/commit/19a410752cd6bd9a41b6906656473e1da04ae0c4|19a41075>

- Use flytekit 1.6 in core image (#991) flyteorg/flytesnacks

#992 Remove awscli from core and use botocore to create an s3 client Pull request opened by eapolinario We removed boto3 in #991 but didn't update this reference in

chain_entities.py

. flyteorg/flytesnacks GitHub Actions: Mark github pre-release as Release GitHub Actions: Publish artifacts to github release GitHub Actions: Create Prerelease GitHub Actions: Bump Version ✅ 26 other checks have passed 26/30 successful checks

#3704 fix typo in cluster resources doc Pull request opened by samhita-alla Tracking issue This PR replaces TB with Ti in the cluster resources config. 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

1 new commit pushed to

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

by eapolinario

<https://github.com/flyteorg/flytesnacks/commit/2c457dfec000912bb22e527fee6229c8808910c0|2c457dfe>

- Remove awscli from core and use botocore to create an s3 client (#992) flyteorg/flytesnacks

Release - flytesnacks v0.3.195 New release published by flyte-bot Changelog • 2c457df Remove awscli from core and use botocore to create an s3 client (#992) • 19a4107 Use flytekit 1.6 in core image (#991) flyteorg/flytesnacks

#1651 Use logger instead of print statement in sqlalchemy plugin Pull request opened by wirthual TL;DR Use root logger instead of print statement in sqlalchemy plugin Type • [x ] Bug Fix ☐ Feature ☐ Plugin Complete description Just replaced the print statement with the root loggers info statement as suggested in the issue Tracking Issue flyteorg/flyte#3651 flyteorg/flytekit ✅ All checks have passed 30/30 successful checks

#1652 Add support image overriding Pull request opened by pingsutw TL;DR This PR allows people to override image by using

with_overrides

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 https://flyte-org.slack.com/archives/CP2HDHKE1/p1683934828365009 Follow-up issue NA flyteorg/flytekit GitHub Actions: build (windows-latest, 3.8) ✅ 29 other checks have passed 29/30 successful checks

#3403 [Core feature] Support partial tasks Issue created by cosmicBboy Motivation: Why do you think this is important? Currently, invoking tasks in `workflow`s or

dynamic

workflows requires fully-specifying the arguments to a

task

. This behavior is clunky in the context of map tasks, where users need to write a bunch of code to prepare the inputs to a map task (see here. The purpose of this issue is to support partial tasks, which allow users to partially bind inputs to a task so that it can then be invoked with the remaining arguments, similar to https://docs.python.org/3/library/functools.html#functools.partial. Goal: What should the final outcome look like, ideally? Requirements Partial tasks should: 1. support partial task inputs that are python values 2. support partial task inputs that are promises 3. support partial task definitions in the top-level scope of a module 4. support use of partial tasks in map tasks Once partial tasks are implemented, it should look something like: Support partial task inputs that are python values

from flytekit import task, workflow, partial

@task
def t1(x: int, y: float) -> float:
    return x + y

@workflow
def wf(y: float):
   partial_t1 = partial(t1, x=5)
   return partial_t1(y=y)

Support partial task inputs that are promises

from flytekit import task, workflow, partial

@task
def t1(x: int, y: float) -> float:
    return x + y

@task
def t2() -> int:
    return 5

@workflow
def wf(y: float):
   partial_t1 = partial(t1, x=t2())
   return partial_t1(y=y)

Support partials in the top-level module scope If a user wants to specify partial tasks using python literal values in the top-level scope:

from flytekit import task, workflow, partial

@task
def t1(x: int, y: float) -> float:
    return x + y

partial_t1 = partial(t1, x=5)

@workflow
def wf(y: float):
   return partial_t1(y=y)

Support partials in map tasks

from flytekit import task, workflow, partial, map_task

@task
def t1(x: int, y: float) -> float:
    return x + y

@workflow
def wf(y: List[float]):
   partial_t1 = partial(t1, x=5)
   return map_task(partial_t1)(y=y)

Describe alternatives you've considered Besides syntactic alternatives, not supporting partial tasks would require writing additional code to make some of Flyte's constructs work (e.g. map tasks with multiple inputs). 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

#3371 [Core feature] Support Yaml / JSON input for pyflyte run Issue created by zeryx Motivation: Why do you think this is important? A bunch of ML workflows and training systems take huge amounts of hyper parameters when configuring training jobs. Sometimes on the order of hundreds of separate variables that are needed to define a training run. Today there does not seem to be a way to provide a file based input for workflow execution. This causes users to either pass a URL as input towards a hosted datafile somewhere, or to manually break out each variable in their configuration and provide that in either the CLI or via the web UI - this is not realistic or tenable for modern ML training projects. Goal: What should the final outcome look like, ideally? With pyflyte run, you should be able to provide a structured yaml or json input defining the configuration of your workflow. Ideally all of those configuration settings would be matched against a user defined hyperparameter class, rather than piecemeal parameters passed in like a conventional python function. A user should also be able to register their workflow, and be able to provide the yaml file to execute via the UI, and also via a launch plan. Describe alternatives you've considered We do support setting some parameters as fixed in launch plans, however that takes control and agency out of the users hands around what actual elements are fixed and variable; and forcing users to generate potentially hundreds of separate launch plans for each individual training event. Even when setting up Launch Plans, the user must manually hardcode all of the variables that are static between executions, which defeats a lot of the purpose here. Propose: Link/Inline OR Additional context https://pypi.org/project/yamldataclassconfig/ Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

#2848 [BUG] Failed to restart demo cluster Issue created by pingsutw Describe the bug FlyteAdmin failed to connect to Postgres after restarting the demo cluster Expected behavior Successfully restart demo cluster Additional context to reproduce

$ flytectl demo start
$ docker restart flyte-sandbox
$ docker logs
...
{"json":{"routine":"worker-8","src":"workers.go:113"},"level":"info","msg":"Started Worker","ts":"2022-09-05T11:49:35Z"}
{"json":{"routine":"worker-7","src":"workers.go:113"},"level":"info","msg":"Started Worker","ts":"2022-09-05T11:49:35Z"}
{"json":{"routine":"worker-12","src":"workers.go:113"},"level":"info","msg":"Started Worker","ts":"2022-09-05T11:49:35Z"}
{"json":{"routine":"worker-9","src":"workers.go:113"},"level":"info","msg":"Started Worker","ts":"2022-09-05T11:49:35Z"}
{"json":{"routine":"worker-10","src":"workers.go:113"},"level":"info","msg":"Started Worker","ts":"2022-09-05T11:49:35Z"}
{"json":{"routine":"worker-11","src":"workers.go:113"},"level":"info","msg":"Started Worker","ts":"2022-09-05T11:49:35Z"}

2022/09/05 11:49:38 /go/pkg/mod/github.com/flyteorg/flyteadmin@v1.1.29/pkg/repositories/database.go:113
[error] failed to initialize database, got error failed to connect to `host=localhost user=postgres database=flyteadmin`: dial error (dial tcp [::1]:30089: connect: cannot assign requested address)

2022/09/05 11:49:38 /go/pkg/mod/github.com/flyteorg/datacatalog@v1.0.1/pkg/repositories/config/postgres.go:73
{"json":{"src":"initialize.go:22"},"level":"fatal","msg":"failed to connect to `host=localhost user=postgres database=flyteadmin`: dial error (dial tcp [::1]:30089: connect: cannot assign requested address)","ts":"2022-09-05T11:49:38Z"}
[error] failed to initialize database, got error failed to connect to `host=localhost user=postgres database=flyteadmin`: dial error (dial tcp [::1]:30089: connect: cannot assign requested address)

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

#2447 [Core feature] Injection of env vars at run time [discussion needed] Issue created by wild-endeavor Motivation: Why do you think this is important? A user requested that Flyte be able to inject environment variables at execution launch time to a workflow run that would get propagated into all downstream tasks, subworkflows, and launch plans. I think this feature is possibly reasonable, but warrants discussion. The reason is that this breaks referential transparency kinda. The injected environment variable are designed to alter the behavior of the task. However. the idea is that these env vars will not affect caching at all, so that is a bit strange. The original use-case for this would be to direct service queries. One may run the same task against production services (non-Flyte stuff) or development services for example. Goal: What should the final outcome look like, ideally? Not entirely clear, but basically at all the points where users can run workflows (flytectl, console, flyte-cli, flyteremote, etc.) the user would be able to pass along a dict that would get set at the top execution level, and this propagate through all nodes/subexecutions. Describe alternatives you've considered It feels more natural to use either a task's domain or the execution's domain to alter behavior, but perhaps not. Another alternative is to add an explicit service environment variable to all the tasks but this is cumbersome and inelegant. 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 eapolinario

<https://github.com/flyteorg/flytekit/commit/d7060cc13be711ea37773435abcc7fbca6c3e4df|d7060cc1>

- Use logger instead of print statement in sqlalchemy plugin (#1651) flyteorg/flytekit

Pending review on flyteorg/flytekit-java - Manage reminder [#6] Update .env.local in README (kanterov) a year stale · 3 years old · Waiting on _ @Ketan (kumare3)_

#3705 [Housekeeping] Store execution namespace in execution closure Issue created by katrogan Describe the issue Not all execution parameters are currently captured in the closure which makes it difficult to reason about the execution after the fact. What if we do not do this? Lose execution-time parameters permanently Related component(s) flyteidl, flyteadmin Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

#406 Add namespace to execution system metadata Pull request opened by katrogan TL;DR Add namespace to execution system metadata 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 N/A see above Tracking Issue flyteorg/flyte#3705 Follow-up issue NA flyteorg/flyteidl ✅ All checks have passed 13/13 successful checks

#3706 [UI Feature] Domain tabs do not persist Issue created by jsonporter Motivation: Why do you think this is important? Users reported that when switching between nav items (workflows, tasks, launchplans, etc) the domain state is not persisted. Goal: What should the final outcome look like, ideally? That the current selected domain is persisted when users interact with the nav. 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

#3707 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 GitHub Actions: generate_helm GitHub Actions: docs GitHub Actions: generate_kustomize GitHub Actions: trigger-sandbox-lite-build GitHub Actions: test-bootstrap GitHub Actions: trigger-sandbox-build GitHub Actions: compile ✅ 2 other checks have passed 2/9 successful checks

1 new commit pushed to

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

by katrogan

<https://github.com/flyteorg/flyteidl/commit/f091fd6da363cf9920701d29d221546478f787be|f091fd6d>

- Add namespace to execution system metadata (#406) flyteorg/flyteidl

Release - v1.5.7 New release published by flyte-bot Changelog • f091fd6 Add namespace to execution system metadata (#406) flyteorg/flyteidl

#568 Save execution namespace in system metadata Pull request opened by katrogan TL;DR Save execution namespace in system metadata 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 N/A see summary Tracking Issue fixes flyteorg/flyte#3705 Follow-up issue NA flyteorg/flyteadmin GitHub Actions: Unit Tests / Run Unit Test GitHub Actions: Docker Build Images / Build Docker Image GitHub Actions: Lint / Run Lint GitHub Actions: Check Go Generate / Go Generate ✅ 2 other checks have passed 2/6 successful checks

#993 Rename session in chain entities Pull request opened by wild-endeavor it's clobbering the import otherwise. flyteorg/flytesnacks GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/kubernetes/ray_example) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/kubernetes/pod) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/kubernetes/kftensorflow) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/kubernetes/kfpytorch) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/kubernetes/kfmpi) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/kubernetes/k8s_spark) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/kubernetes/k8s_dask) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/flytekit_plugins/whylogs_examples) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/flytekit_plugins/sql) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/flytekit_plugins/papermilltasks) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/flytekit_plugins/pandera_examples) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/flytekit_plugins/onnx_examples) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/flytekit_plugins/modin_examples) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/flytekit_plugins/mlflow_example) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/flytekit_plugins/greatexpectations) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/flytekit_plugins/duckdb_examples) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/flytekit_plugins/dolt) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/flytekit_plugins/dbt_example) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/external_services/databricks) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/aws/sagemaker_training) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/aws/sagemaker_pytorch) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/aws/batch) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/aws/athena) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/core) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/case_studies/ml_training/spark_horovod) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/case_studies/ml_training/pima_diabetes) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/case_studies/ml_training/nlp_processing) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/case_studies/ml_training/mnist_classifier) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/case_studies/ml_training/house_price_prediction) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/case_studies/feature_engineering/feast_integration) ✅ No checks have passed 0/30 successful checks

1 new commit pushed to

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

by wild-endeavor

<https://github.com/flyteorg/flytesnacks/commit/2cc66f4b88444376bd0fdd4d07ed1efc43f49442|2cc66f4b>

- Rename session in chain entities (#993) flyteorg/flytesnacks

#994 Update messageFormat explanation on log links Pull request opened by hamersaw Currently, the

messageFormat

field expects a proto generated enum in the configuration. This doc requests a string value (ie. "unknown", "json", or "csv") which, if provided, will result in a failure to parse the configuration. This PR updates the docs to explain that

messageFormat

is an optional parameter that is unused anywhere in the codebase and setting it requires the use of an integer for the corresponding proto generated enum value. fixes flyteorg/flyte#3664 flyteorg/flytesnacks GitHub Actions: Mark github pre-release as Release GitHub Actions: Publish artifacts to github release GitHub Actions: Create Prerelease GitHub Actions: Bump Version ✅ 26 other checks have passed 26/30 successful checks