Skip to content

Truncate tag to allow longer workflow names#251

Merged
timothyF95 merged 4 commits intomainfrom
truncate-wf-tag
Feb 6, 2026
Merged

Truncate tag to allow longer workflow names#251
timothyF95 merged 4 commits intomainfrom
truncate-wf-tag

Conversation

@timothyF95
Copy link
Contributor

@timothyF95 timothyF95 commented Feb 5, 2026

Summary

  • The workflow registry contract limits tags to 32 bytes, but the CLI uses the workflow name (up to 64 chars) as the tag, causing deployments to fail for longer names.
  • Truncates the tag to 32 bytes in ResolveInputs and updates workflowExists() to use the truncated tag for consistency.
  • No impact on existing workflows — names >32 chars always failed before, so no on-chain records need migration.

Test plan

  • Added TestResolveInputs_TagTruncation covering short names, exactly 32 chars, 33 chars, and 64 chars
  • All existing deploy tests pass

@timothyF95 timothyF95 marked this pull request as ready for review February 5, 2026 19:28
@timothyF95 timothyF95 requested a review from a team as a code owner February 5, 2026 19:28
@timothyF95 timothyF95 added this pull request to the merge queue Feb 6, 2026
Merged via the queue into main with commit d1260f3 Feb 6, 2026
21 checks passed
@timothyF95 timothyF95 deleted the truncate-wf-tag branch February 6, 2026 14:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants