build(deps): bump github.com/hatchet-dev/hatchet from 0.53.14 to 0.59.0 in /go

[dependabot]

Bumps github.com/hatchet-dev/hatchet from 0.53.14 to 0.59.0.

Release notes

Sourced from github.com/hatchet-dev/hatchet's releases.

v0.58.1

What's Changed

New Features

• We've added support for non-retryable errors to the Hatchet SDKs: you can read more here
• We've made major improvements to documentation, with almost all pages migrated from v0 to v1.

Bug Fixes

• Concurrency strategies will no longer drain gracefully between different workflow versions to prevent instances of high blocking on queues (#1477)
• We've fixed an issue on the Python SDK where the HATCHET_CLIENT_TOKEN environment variable was previously required when importing the Hatchet package (this is no longer the case) (#1483)
• Fixes an issue on the Go SDK where step run failed was automatically prepended to error strings in on-failure steps (#1482)

v0.57.1

What's Changed

Small improvements to docs and minor bug fixes.

Bug Fixes

• Fixes an issue where /hatchet/hatchet-migrate isn't set automatically as an entrypoint in the migration container (#1440)
• Improves Typescript typing (#1444)
• Improves error-handling in the Hatchet gRPC service when sending a task to a worker fails (#1441)

Full Changelog: hatchet-dev/hatchet@v0.57.0...v0.57.1

v0.57.0 - v1 SDKs

V1 SDK Improvements

This release bundles SDK improvements for Go, Typescript, and Python.

Python SDK Highlights

The Python SDK has a number of notable highlights to showcase for V1. Many of them have been highlighted elsewhere, such as in the migration guide, on the Pydantic page, an in various examples. Here, we'll list out each of them, along with their motivations and benefits.

First and foremost: Many of the changes in the V1 Python SDK are motivated by improved support for type checking and validation across large codebases and in production use-cases. With that in mind, the main highlights in the V1 Python SDK are:

1. Workflows are now declared with hatchet.workflow, which returns a Workflow object, or hatchet.task (for simple cases) which returns a Standalone object. Workflows then have their corresponding tasks registered with Workflow.task. The Workflow object (and the Standalone object) can be reused easily across the codebase, and has wrapper methods like run and schedule that make it easy to run workflows. In these wrapper methods, inputs to the workflow are type checked, and you no longer need to specify the name of the workflow to run as a magic string.
2. Tasks have their inputs type checked, and inputs are now Pydantic models. The input field is either the model you provide to the workflow as the input_validator, or is an EmptyModel, which is a helper Pydantic model Hatchet provides and uses as a default.
3. In the new SDK, we define the parents of a task as a list of Task objects as opposed to as a list of strings. This also allows us to use ctx.task_output(my_task) to access the output of the my_task task in the a downstream task, while allowing that output to be type checked correctly.
4. In the new SDK, inputs are injected directly into the task as the first positional argument, so the signature of a task now will be Callable[[YourWorkflowInputType, Context]]. This replaces the old method of accessing workflow inputs via context.workflow_input().

Other Breaking Changes

There have been a number of other breaking changes throughout the SDK in V1.

Typing improvements:

1. External-facing protobuf objects, such as StickyStrategy and ConcurrencyLimitStrategy, have been replaced by native Python enums to make working with them easier.

... (truncated)

Commits

• c6abd6b feat: multiple workflow concurrency keys (#1511)
• 9f3addc fix: ensure release VERSION is properly set in lite builds (#1545)
• 8013773 Feat: Priority (#1513)
• eee938e Fix: Unique readable data key errors (#1546)
• 7190078 fix: remove fk constraint on crons (#1543)
• 90805ca Feat: Lifespans! (#1541)
• cc014bd fix: correct create type (#1539)
• 6813ab1 fix: streaming order improvements, go sdk stability (#1536)
• eb78fd1 fix: task output (#1519)
• 5ad3a4b fix: increase PutWorkflowVersion timeout to 25 seconds (#1529)
• Additional commits viewable in compare view

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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]

Superseded by #89.