Prepare 1.3.1 release - #63
Merged
Merged
Conversation
nickmoreton
marked this pull request as ready for review
July 16, 2026 11:36
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.
Summary
Why
This prepares the patch release containing the malformed honeypot timestamp fix currently on main. The runtime version constant was still reporting 1.2.1 after the prior release, so this release also brings it back in sync with the package metadata.
Impact
Malformed honeypot timestamps will be ignored instead of raising an exception, and consumers inspecting the runtime version will receive the published 1.3.1 version.
Verification