arti: update to 2.6.0.
(leaf package)
Arti 2.6.0 continues our steady progress on relay and directory
authority development, including on document parsing, directory
mirror support, and DNS stream handling.
Additionally, this release makes Congestion control and Counter
Galois Onion cryptography always on in `arti`.
As usual, there are also many under-the-hood improvements and bug
fixes.
pci_resource: use existing BARs even if mem/io space is left disabled
It's possible that firmware assigned resources to a device and left
memory / io space accesses disabled. Let's assume if we see a non-zero
address in a BAR that it was assigned by firmware.
Should help PR# kern/60427 and kern/60463
www/ruby-aws-sdk-kms: update to 1.132.0
1.132.0 (2026-09-11)
* Feature - Code Generated Changes, see ./build_tools or aws-sdk-core's
CHANGELOG.md for details.
www/ruby-aws-sdk-secretsmanager: update to 1.136.0
1.136.0 (2026-09-11)
* Feature - Code Generated Changes, see ./build_tools or aws-sdk-core's
CHANGELOG.md for details.
www/ruby-aws-sdk-core: update to 3.256.0
3.256.0 (2026-09-11)
* Feature - Preserve millisecond precision when serializing Time values on
the request path, instead of truncating to whole seconds.
www/ruby-aws-partitions: update to 1.1286.0
1.1286.0 (2026-09-11)
* Feature - Updated the partitions source data that determines the AWS
service regions and endpoints.
1.1285.0 (2026-09-10)
* Feature - Updated the partitions source data that determines the AWS
service regions and endpoints.
gicv3: don't wait for RWP to clear when unblocking irqs
The RWP bit does not track writes to ISENABLER<n>, only ICENABLER<n>. So
don't bother waiting for it to clear when unblocking IRQs.
This is ok; pic_block_irqs is expected to be synchronous (no IRQs allowed
after the call) but not pic_unblock_irqs (some time can pass before an IRQ
is raised).
net/ruby-winrm: udpate to 2.4.0
2.4.0 (2026-09-10)
What changed
* Fix WinRM shell finalizer for Ruby 3.1+ by safely handling ThreadError
(#354)
* Rename object_id to message_id (#352)
* Replace the unmaintained logging gem with the Ruby standard library Logger
(#358, by @fwininger). Connection#logger is now a stdlib Logger subclass:
the standard API is unchanged, and the one logging-specific call
(add_appenders) still works but logs a deprecation warning (#360)
* Modernize build chain (#357, by @fwininger)
* CI modernization, README fixes
Upgrade notes
If you were calling logging-gem-specific methods (e.g. add_appenders) on
[2 lines not shown]
devel/ruby-msgpack: update to 1.8.5
1.8.5 (2026-09-11)
* Prevent stack depth underflow when skipping from recursive unpacker.
* Fix `Unpacker#skip_nil` to properly consume the buffer.
* Fix some small difference in Factory registration of the Java
implementation.
* Fix some Factory/ext_type optimization edge cases.
vault: upgrade go-limiter package
The old version of the go-limiter dependency is not compatible with
current Go versions, as it accesses internal runtime details.
This also needs a few other dependency updates.