From: Dan Callaghan <noreply@github.com>
To: djc@djc.id.au, sup-commits@supmua.dev
Subject: [sup-heliotrope/sup] e5b96d: contrib/nix: bump nixpkgs
Date: Sun, 05 Apr 2026 18:07:35 -0700 [thread overview]
Message-ID: <sup-heliotrope/sup/push/refs/heads/develop/4ac006-2837f0@github.com> (raw)
Branch: refs/heads/develop
Home: https://github.com/sup-heliotrope/sup
Commit: e5b96de0f61042ffdc73467b27baf0423e5b58a9
https://github.com/sup-heliotrope/sup/commit/e5b96de0f61042ffdc73467b27baf0423e5b58a9
Author: Dan Callaghan <djc@djc.id.au>
Date: 2026-04-06 (Mon, 06 Apr 2026)
Changed paths:
M Manifest.txt
M contrib/nix/Gemfile.lock
M contrib/nix/gemset.nix
A contrib/nix/ruby3.1-Gemfile.lock
A contrib/nix/ruby3.1-gemset.nix
M contrib/nix/ruby3.1-shell.nix
A contrib/nix/ruby3.2-Gemfile.lock
A contrib/nix/ruby3.2-gemset.nix
M contrib/nix/ruby3.2-shell.nix
M contrib/nix/ruby3.3-shell.nix
M contrib/nix/ruby3.4-shell.nix
Log Message:
-----------
contrib/nix: bump nixpkgs
This is to get ruby_4_0.
ruby_3_1 and ruby_3_2 have been dropped, so pin these to their current
nixpkgs commit.
This also brings in gpgme 2.0.0, which broke ruby-gpgme. Bump ruby-gpgme
to 2.0.26 to get the fixes:
https://github.com/ueno/ruby-gpgme/pull/203
Commit: d5b5955a344fab493f4dad1798ccdcbdbfb4e1f2
https://github.com/sup-heliotrope/sup/commit/d5b5955a344fab493f4dad1798ccdcbdbfb4e1f2
Author: Dan Callaghan <djc@djc.id.au>
Date: 2026-04-06 (Mon, 06 Apr 2026)
Changed paths:
M .github/workflows/checks.yml
M Manifest.txt
A contrib/nix/ruby4.0-shell.nix
Log Message:
-----------
test against Ruby 4.0
Commit: 099412d0b5d622c320e4bca8e3c1fb0bb57cacaa
https://github.com/sup-heliotrope/sup/commit/099412d0b5d622c320e4bca8e3c1fb0bb57cacaa
Author: Dan Callaghan <djc@djc.id.au>
Date: 2026-04-06 (Mon, 06 Apr 2026)
Changed paths:
M .rubocop.yml
M Rakefile
M contrib/nix/Gemfile.lock
M contrib/nix/gemset.nix
Log Message:
-----------
rubocop: 1.63.2 → 1.86.0
Skip rubocop checks on Ruby < 3.3 since these cannot get the newer
rubocop and so they will not understand the .rubocop.yml changes.
Commit: 2837f0614381052c77e213cf6ab23729ba84777b
https://github.com/sup-heliotrope/sup/commit/2837f0614381052c77e213cf6ab23729ba84777b
Author: Dan Callaghan <djc@djc.id.au>
Date: 2026-04-06 (Mon, 06 Apr 2026)
Changed paths:
M contrib/nix/Gemfile.lock
M contrib/nix/gemset.nix
Log Message:
-----------
contrib/nix: bump all gem dependencies to their latest versions
Compare: https://github.com/sup-heliotrope/sup/compare/4ac006085b55...2837f0614381
To unsubscribe from these emails, change your notification settings at https://github.com/sup-heliotrope/sup/settings/notifications
reply other threads:[~2026-04-06 1:07 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=sup-heliotrope/sup/push/refs/heads/develop/4ac006-2837f0@github.com \
--to=noreply@github.com \
--cc=djc@djc.id.au \
--cc=sup-commits@supmua.dev \
/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