core/services/workflows/types: add WorkflowID.String()

[jmank88]

These log as raw bytes otherwise, which is spammy and unreadable.

[github-actions]

👋 jmank88, thanks for creating this pull request!

To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team.

Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks!

[github-actions]

I see you updated files related to core. Please run pnpm changeset in the root directory to add a changeset as well as in the text include at least one of the following tags:

• #added For any new functionality added.
• #breaking_change For any functionality that requires manual action for the node to boot.
• #bugfix For bug fixes.
• #changed For any change to the existing functionality.
• #db_update For any feature that introduces updates to database schema.
• #deprecation_notice For any upcoming deprecation functionality.
• #internal For changesets that need to be excluded from the final changelog.
• #nops For any feature that is NOP facing and needs to be in the official Release Notes for the release.
• #removed For any functionality/config that is removed.
• #updated For any functionality that is updated.
• #wip For any change that is not ready yet and external communication about it should be held off till it is feature complete.

[cl-sonarqube-production]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[trunk-io]

🔴 Test Results: Unrelated Failure

Affected failures:

1. Workflow Run: Integration Tests

What Broke

This failure appears to be unrelated to the changes in this PR. The CI failure is not caused by the changes introduced in this PR. The failure is due to an external, unrelated issue within the CI environment or the existing codebase. The PR only adds a String() method to the WorkflowID type, and a code search confirms this new method is not being called anywhere in the codebase. The CI failure logs are generic, indicating 'Process completed with exit code 1.' without any specific error messages or stack traces that could be linked to the PR's changes.

Autofix Options

You can use our MCP server to get AI assistance with debugging and fixing these failures.

• Use MCP in your IDE to debug the issue. Try Help me fix CI failures from 0gQip4KH to get started.

View all test uploads

[trunk-io]

     

View Full Report ↗︎ ⋅ Docs