chore: v1.2.0 -> v1.2.1#224
Merged
Merged
Conversation
bchampp
approved these changes
May 21, 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
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.
Bumps testing SDK from v1.2.0 to v1.2.1 in preparation for a new release.
Notable change since v1.2.0:
This fixes a regression introduced in v1.2.0:
dex-local-runner(WebRunner) returned404for every Get/State/History/Checkpoint/Stop call against an execution whose ARN contained a literal/, and silently returned an empty list forListDurableExecutionsByFunctionwhen the function name contained:or$. The cause was that the WebServer's route layer wasn't URL-decoding captured path segments before using them as store-lookup keys, while boto's rest-json serializer percent-encodes those characters in non-greedy URI labels. See #222 for the full bug report.Verification
hatch version patchran cleanly;__about__.pyupdated 1.2.0 → 1.2.1.