Merged
Conversation
Br1an-Boyle
approved these changes
Apr 17, 2026
Patch release for the JWT signed fields script tag validation fix (#375). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
rishab-intercom
force-pushed
the
shab/bump-version-1.1.1
branch
from
2ad89ec to
b8a4539
Compare
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.
Why?
Release the fix for JWT signed fields causing script tag validation failure. When both
user_idandemailare configured assigned_user_fields, thevalid?check was failing because those fields had already been promoted to the JWT payload, leaving theuser_detailshash empty.How?
Patch version bump (
1.1.0→1.1.1) so the fix from PR #375 can be published to RubyGems. After merge, rungem releaseto publish.Generated with Claude Code