From: Dan Callaghan <djc@djc.id.au>
To: supmua <supmua@googlegroups.com>
Subject: release 1.3
Date: Mon, 21 Apr 2025 15:27:01 +1000 [thread overview]
Message-ID: <1745213033-sup-5808@honeycomb.djc.id.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1066 bytes --]
I've just released Sup 1.3. It includes some fixes for long-standing
bugs, as well as a change in preparation for the coming frozen string
literals in Ruby 3.5.
The new release is available from Rubygems and Github.
== 1.3 / 2025-04-21
* #596: If a message lacks a Date header, or the Date header is not in valid
RFC2822 format, the local delivery timestamp of the message will now be used
instead. Fixes a bug where such messages would constantly jump to the top of
the thread list.
* #502: Fixed incorrect Content-Transfer-Encoding headers when sending GPG
signed or encrypted messages with attachments.
* #522: Sup now uses the configured signing key when sending a message that is
both signed and encrypted. Previously it would ignore the configured key and
use the GPG default signing key.
* #489: Attachments are now encoded if they have lines longer than 998
characters.
* #602: The message/global MIME type is now recognised as an embedded message.
* Sup is now tested on Ruby 3.4.
--
Dan Callaghan <djc@djc.id.au>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2025-04-21 5:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1745213033-sup-5808@honeycomb.djc.id.au \
--to=djc@djc.id.au \
--cc=supmua@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox