From: fanquake <fanquake@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Bitcoin Core v30.5 Released
Date: Fri, 20 Nov 2026 05:54:38 -0800 (PST) [thread overview]
Message-ID: <b35d81a4-e207-4068-82e5-88a2f882e871n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2199 bytes --]
v30.5 Release Notes
===================
Bitcoin Core version v30.5 is now available from:
<https://bitcoincore.org/bin/bitcoin-core-30.5/>
This release includes various bug fixes and performance
improvements, as well as updated translations.
Please report bugs using the issue tracker at GitHub:
<https://github.com/bitcoin/bitcoin/issues>
To receive security and update notifications, please subscribe to:
<https://bitcoincore.org/en/list/announcements/join/>
How to Upgrade
==============
If you are running an older version, shut it down. Wait until it has
completely
shut down (which might take a few minutes in some cases), then run the
installer (on Windows) or just copy over `/Applications/Bitcoin-Qt` (on
macOS)
or `bin/` and `libexec/` (on Linux).
Upgrading directly from a version of Bitcoin Core that has reached its EOL
is
possible, but it might take some time if the data directory needs to be
migrated. Old
wallet versions of Bitcoin Core are generally supported.
Compatibility
==============
Bitcoin Core is supported and tested on operating systems using the
Linux Kernel 3.17+, macOS 13+, and Windows 10+. Bitcoin
Core should also work on most other Unix-like systems but is not as
frequently tested on them. It is not recommended to use Bitcoin Core on
unsupported systems.
Notable changes
===============
### Net
- #35878 net_processing: process unique tx INVs only
### CI
- #33693 ci: use pycapnp 2.2.1
- #35348 ci: switch to GitHub cache for all runners
- #35441 ci: inline runner selection
- #35571 ci: use warp docker buildkit cache
Credits
=======
Thanks to everyone who directly contributed to this release:
- fanquake
- Greg Sanders
- willcl-ark
As well as to everyone that helped with translations on
[Transifex](https://explore.transifex.com/bitcoin/bitcoin/).
--
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/b35d81a4-e207-4068-82e5-88a2f882e871n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2794 bytes --]
reply other threads:[~2026-11-20 13:56 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=b35d81a4-e207-4068-82e5-88a2f882e871n@googlegroups.com \
--to=fanquake@gmail.com \
--cc=bitcoindev@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