Conversation
Instead of manually computing Upstash-Redact-Fields headers in _get_headers, pass the redact parameter directly to qstash_client.message.publish_json which handles it natively. Bump qstash dependency to ^3.4.0 and version to 0.1.5. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Bypass qstash v3 SDK's batch_json which auto-prefixes all headers with Upstash-Forward-, corrupting workflow control headers. Construct the batch body manually and send via the HTTP client directly. Also add integration tests for triggering workflows with redact fields. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
alitariksahin
approved these changes
Mar 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.