fix: Cleanup deprecated concurrency strategies, fix FE omissions

[juliusgeo]

Description

Deprecated concurrency strategies were accidentally added, removed them. Also deleted from the proto. Fixed a few issues in FE where the new concurrency strategies were not added to some switch statements.

Fixes # (issue)

Type of change

• Bug fix (non-breaking change which fixes an issue)
• Documentation change (pure documentation change)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Refactor (non-breaking changes to code which doesn't change any behaviour)
• Performance improvement (non-breaking change which improves performance)
• CI (any automation pipeline changes)
• Chore (changes which are not directly related to any business logic)
• Test changes (add, refactor, improve or change a test)
• This change requires a documentation update

Checklist

Changes have been:

• Documented (where applicable)
• Added to CHANGELOG (where applicable) -- see Keep a Changelog

---

🤖 AI Disclosure

• I acknowledge that an LLM was used in the creation of this Pull Request, in accordance with Hatchet's AI_POLICY.md.

• Details: [e.g. generating tests, writing docs]

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
hatchet-docs	Ready	Preview	Sep 3, 2026 5:15pm UTC

[greptile-apps]

Greptile Summary

This PR removes deprecated concurrency-strategy symbols, reserves their protobuf identifiers, and fills omissions for newer strategies in frontend and generated TypeScript enums.

• Updates OpenAPI, protobuf, and generated frontend contracts.
• Extends workflow settings labels for all current strategies.
• Removes deprecated Go and Python SDK symbols.
• Leaves a generated TypeScript enum out of sync with its source protobuf and omits required SDK release metadata.

Confidence Score: 4/5

The PR appears safe to merge after addressing the non-blocking generated-contract consistency and SDK release-metadata issues.

The active v1 concurrency path supports the new strategies, but the legacy generated TypeScript enum additions will be lost on regeneration and do not round-trip through its JSON helpers; the Python and TypeScript SDK changes also lack required version and changelog updates.

Files Needing Attention: sdks/typescript/src/protoc/workflows/workflows.ts, api-contracts/workflows/workflows.proto, sdks/python/hatchet_sdk/types/concurrency.py

_{Reviews (1): Last reviewed commit: "initial commit" | Re-trigger Greptile}

[greptile-apps]

SDK release metadata omitted

These Python and TypeScript SDK contract changes have no corresponding version bumps or changelog entries, so the removed and added public enum members can ship without the repository-required package versions and migration records.

Context Used: AGENTS.md (source)

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[greptile-apps]

Generated enum contradicts protobuf

These values are absent from the source protobuf and from this file's JSON conversion cases. Regenerating the binding removes them, while using the current conversion helpers maps them to UNRECOGNIZED instead of preserving the strategy.

[github-actions]

⚠️ Optional test failure: The load-deadlock job failed on this PR (optimistic-scheduling=true). This check is non-mandatory and does not block merging, but may be worth investigating. View logs