release: v3.5.1 - #70
Open
radiosilence wants to merge 1 commit into
Open
Conversation
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016ri9XAwMqKiHLrDyTuA3np
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
1 participant
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.
Patch: one bug fix, no API or behaviour change beyond it.
Cargo.toml3.5.0 → 3.5.1, lockfile regenerated (cargo check --lockedpasses), changelog dated.Changelog entry
Fixed
replynow prefersReply-TooverFrom(#68, closes #67, reported by Kendell). Transactional and support senders routinely put a branded address inFromand the inbox that actually receives mail inReply-To; replying toFromthen bounces off a domain with no MX record, which is how this was found.Reply-ToreplacesFromrather than joining it — on a reply-all the branded address is no more deliverable than it was on a plain reply. An emptyReply-Tolist is not aReply-To, and still falls back.The CLI and GraphQL's
replyToEmailshare the helper, so both were wrong together and are fixed together — including the send preview, which had been reporting the address it was about to fail to deliver to.Also on main since 3.5.0, docs only: real-time streaming got its own row in the feature and comparison tables (#69).
Tag is yours to cut — nothing here creates or pushes one. The publish workflow triggers on it, and v3.5.0 is still untagged, so tagging 3.5.1 releases both changes together.