chore: version packages - #158
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
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
@e4a/pg-js@2.4.0
Minor Changes
5fd30b7: Export the MIME reader, PostGuard detection and the archival armor readers, so both add-ins read the envelope through one implementation instead of two hand-rolled copies.
New exports:
parseDecryptedMime,readMimeHeader,bodyFromMime,isMultipart,detectPostGuard,extractArmoredCiphertext,looksLikeArmoredPostGuard,POSTGUARD_ENCRYPTED_FILENAME, and theParsedMessage/ParsedAttachment/DetectPostGuardInputtypes. Additive only — no existing signature changes.Two fixes came out of the move:
=XXwas mapped throughString.fromCharCode, giving one character per octet, socaf=C3=A9read back ascaférather thancafé. The byte path compounded it by re-encoding that as UTF-8, doubling every octet above 0x7f and silently corrupting quoted-printable attachments. Octets are now collected and decoded once.extractCiphertext's documentation claimed it read "attachment or armored body". It has only ever read the attachment. The armor path is now a separate, explicitly archival export, which is whatCOMPATIBILITY.md's never-drops guarantee for stored artifacts actually requires.postguard-outlook-addin@1.0.1
Patch Changes
postguard-tb-addon@0.9.5
Patch Changes
postguard-website@1.8.3
Patch Changes