Discussions of development and use of the Sup email client
 help / color / mirror / Atom feed
From: Dan Callaghan <djc@djc.id.au>
To: supmua <supmua@googlegroups.com>
Subject: release 1.2
Date: Sun, 21 Apr 2024 12:22:15 +1000	[thread overview]
Message-ID: <1713666045-sup-1599@honeycomb.djc.id.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 794 bytes --]

I've just released Sup 1.2. It includes a few minor fixes related to
Ruby 3.2 and 3.3 support.

The new release is available from Rubygems and Github.

== 1.2 / 2024-04-21

* #619: Sup is now compatible with and tested on Ruby 3.2 and Ruby 3.3.
  (Dan Callaghan)
* #603: Fixed deprecated usage of Enumerator.new, which caused a crash on
  Ruby 3+. (Gui Goncalves)
* OutOfSyncSourceErrors now show an error message in the thread view in place
  of the out-of-sync message body, instead of crashing. (Dan Callaghan)
* #613: When installing Sup as a gem, the dependency on xapian-ruby is now
  skipped if the SUP_SKIP_XAPIAN_GEM_INSTALL environment variable is set.
  Previously it was skipped unconditionally on OpenBSD only. (Dan Callaghan)

-- 
Dan Callaghan <djc@djc.id.au>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

                 reply	other threads:[~2024-04-21  2:22 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=1713666045-sup-1599@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