chore: release#83
Merged
Merged
Conversation
c16a927 to
1b5639c
Compare
ApprovabilityVerdict: Approved Automated release PR that only updates CHANGELOG.md, deletes a consumed changeset file, and bumps the version number in package.json. No runtime code changes. You can customize Macroscope's approvability policy. Learn more. |
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@xmtp/convos-cli@0.10.10
Patch Changes
1a4a74cThanks @saulmc! - FixnormalizeMessageContentso a reply that carries a non-text payload renders its display string instead of a raw JSON dump of the decoded content. A reply containing a remote attachment now rendersreply to "…": [remote attachment: photo.jpg (… bytes) https://…]rather than serializing the attachment envelope — which leaked the AES key material (secret/salt/nonce) into the message text. Inline attachments, reactions, and other nested content types render through the same path.Need help on this PR? Tag
/codesmithwith what you need. Autofix is disabled.Note
Release version 0.10.10 with fix to
normalizeMessageContentfor repliesBumps the package version from 0.10.9 to 0.10.10 and updates CHANGELOG.md to document the patch. The fix addresses rendering of non-text payloads in replies, including remote attachments and other nested content types.
Macroscope summarized 1b5639c.