dependabot[bot] opened a new pull request, #738: URL: https://github.com/apache/karaf-decanter/pull/738
Bumps [com.github.oshi:oshi-core](https://github.com/oshi/oshi) from 6.12.0 to 7.6.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/oshi/oshi/releases";>com.github.oshi:oshi-core's releases</a>.</em></p> <blockquote> <h2>Release 7.6.1</h2> <h5>Bug Fixes and Improvements</h5> <ul> <li><a href="https://redirect.github.com/oshi/oshi/pull/3710";>#3710</a>: Fix the bnd imports for <code>oshi-core</code> and <code>oshi-core-ffm</code> to make the JSpecify annotations optional, so both bundles resolve in an OSGi container without JSpecify - <a href="https://github.com/dbwiddis";><code>@dbwiddis</code></a>.</li> </ul> <p><a href="https://github.com/oshi/oshi/blob/master/CHANGELOG.md";>Full change log</a></p> <h2>Release 7.6.0</h2> <h5>Maven Central Publication Change</h5> <p>The <code>oshi-dist</code> zip is no longer published to Maven Central; download it from the <a href="https://github.com/oshi/oshi/releases";>GitHub release</a> instead.</p> <h5>New Features</h5> <ul> <li><a href="https://redirect.github.com/oshi/oshi/pull/3652";>#3652</a>: <code>oshi-metrics</code> reports the OpenTelemetry <code>reserved</code> state for <code>system.filesystem.usage</code> and <code>system.filesystem.utilization</code>, alongside the existing <code>used</code> and <code>free</code>. The three states partition the filesystem, so the <code>usage</code> gauges sum to <code>system.filesystem.limit</code> and the <code>utilization</code> gauges sum to 1.0 - <a href="https://github.com/dbwiddis";><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3660";>#3660</a>, <a href="https://redirect.github.com/oshi/oshi/pull/3678";>#3678</a>: <code>Display.getDevicePort()</code> reports the port a display is attached to, and on systems with X RandR, <code>Display.getOutputName()</code> gives the name <code>xrandr --output</code> accepts for it - <a href="https://github.com/ayonization";><code>@ayonization</code></a>, <a href="https://github.com/dbwiddis";><code>@dbwiddis</code></a>.</li> </ul> <h5>Behavior Changes</h5> <ul> <li><a href="https://redirect.github.com/oshi/oshi/pull/3705";>#3705</a>: <code>OSDesktopWindow.getLocAndSize()</code> returns a copy of the window's <code>Rectangle</code> and the constructor copies the one it is given, so the class honors the immutability its documentation promises. <code>ApplicationInfo.getAdditionalInfo()</code> returns an unmodifiable map. Code that wrote through either return value silently mutated OSHI's own state; it now has no effect, or throws <code>UnsupportedOperationException</code> for the map - <a href="https://github.com/dbwiddis";><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3705";>#3705</a>: <code>UsbDevice.compareTo()</code> breaks ties on the unique device ID, vendor ID, product ID and serial number after comparing names, and <code>AbstractUsbDevice</code> implements <code>equals()</code> and <code>hashCode()</code> over the same fields. Two distinct devices sharing a name previously compared equal, so a <code>TreeSet</code> or <code>SortedSet</code> of them kept only one. The ordering is now a default method on <code>UsbDevice</code>, so every implementation shares it - <a href="https://github.com/dbwiddis";><code>@dbwiddis</code></a>.</li> </ul> <h5>Bug Fixes and Improvements</h5> <ul> <li><a href="https://redirect.github.com/oshi/oshi/pull/3651";>#3651</a>: <code>OSFileStore</code> now guarantees <code>0 <= getUsableSpace() <= getFreeSpace() <= getTotalSpace()</code> on every platform. The three values are read by separate queries, so on a ZFS dataset or a swap-backed <code>tmpfs</code> they could previously contradict each other; they are now clamped downward to restore the ordering - <a href="https://github.com/dbwiddis";><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3657";>#3657</a>: Fix the <code>TcpState</code> for the FFM implementation of <code>InternetProtocolStats.getConnections()</code> on macOS and set the process cap from the kernel - <a href="https://github.com/dbwiddis";><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3661";>#3661</a>: Setting <code>oshi.os.windows.hkeyperfdata</code> to <code>false</code> now also skips the registry when fetching thread counters, matching its documented behavior and the existing handling for processes - <a href="https://github.com/dbwiddis";><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3662";>#3662</a>: Reading the processor description from the registry no longer throws when a value is missing. <code>CentralProcessor.getFeatureFlags()</code> on Windows now reports every processor feature <code>IsProcessorFeaturePresent()</code> accepts, matching the <code>PF_</code> defines in <code>winnt.h</code> - <a href="https://github.com/dbwiddis";><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3665";>#3665</a>: <code>NetworkParams.getRoutes()</code> reads the routing table from the kernel through a <code>NET_RT_DUMP</code> sysctl on macOS, FreeBSD, DragonFly BSD and OpenBSD, rather than by running <code>netstat</code> twice - <a href="https://github.com/dbwiddis";><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3670";>#3670</a>: <code>NetworkParams.getHostName()</code> on Linux reads the kernel host name from <code>/proc/sys/kernel/hostname</code> in every backend, fixing the native-free implementation, which truncated a fully qualified name at the first dot and reported <code>localhost</code> when the name did not resolve - <a href="https://github.com/dbwiddis";><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3671";>#3671</a>: <code>NetworkParams.getHostName()</code> and <code>getDomainName()</code> report the empty-string sentinel when the local host name does not resolve, rather than the loopback address's <code>localhost</code>. NetBSD is the most affected platform, having no native host name query of its own - <a href="https://github.com/dbwiddis";><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3672";>#3672</a>, <a href="https://redirect.github.com/oshi/oshi/pull/3674";>#3674</a>: <code>CentralProcessor</code> frequencies and <code>PhysicalProcessor.getEfficiency()</code> on Apple Silicon are correct regardless of call order and on the M4 and M5 generations. Frequencies previously fell back to a 2.4 GHz placeholder unless <code>getProcessorIdentifier()</code> happened to be called first, were reported a thousand times too low on the M4 and later, and a chip with more or fewer than two kinds of core was misclassified - <a href="https://github.com/dbwiddis";><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3675";>#3675</a>: <code>CentralProcessor.getCurrentFreq()</code> on Apple Silicon can report the frequency the hardware actually ran at, rather than a nominal maximum that never changes. Set <code>oshi.os.mac.cpu.frequency.ioreport</code> to <code>true</code>; it is opt-in because it holds a subscription to a private framework for the lifetime of the process - <a href="https://github.com/dbwiddis";><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3680";>#3680</a>: <code>oshi-metrics</code> reads a disk or network interface once per memoizer expiration window rather than once per meter, so a scrape makes one query where it previously made five or seven, and the meters of one device report the same reading. A rate computed across two of them, such as errors per packet, is now comparable - <a href="https://github.com/dbwiddis";><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3681";>#3681</a>: <code>GpuStats.getGpuUtilization()</code> on Linux reads NVIDIA GPU utilization from NVML. It previously read only the amdgpu/i915/xe sysfs paths, none of which the NVIDIA driver exposes, so an NVIDIA card always returned the -1 sentinel - <a href="https://github.com/Krillsson";><code>@Krillsson</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3686";>#3686</a>: <code>GpuStats.getGpuUtilization()</code> on Windows reads NVIDIA utilization from NVML and AMD utilization from ADL, matching the source order of every other metric on the class. It previously ran only LibreHardwareMonitor and a PDH engine-tick delta, which needs two samples, so the first call returned the -1 sentinel - <a href="https://github.com/dbwiddis";><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3687";>#3687</a>: <code>GpuStats.getSharedMemoryUsed()</code> on Linux reports the amdgpu GTT memory in use rather than always returning -1, and <code>GraphicsCard.getVRam()</code> on an amdgpu card reports the driver's own figure rather than the memory BAR size parsed from <code>lspci</code> or <code>lshw</code>. Several <code>GpuStats</code> metrics on Linux also now return the -1 sentinel when the sysfs file behind them is absent; they previously reported 0, so a card whose hwmon directory omits <code>power1_average</code> read as drawing 0.0 W - <a href="https://github.com/dbwiddis";><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3698";>#3698</a>: <code>OSProcess.getCurrentWorkingDirectory()</code> on macOS returns the directory rather than an empty string in the FFM implementation, and <code>NetworkParams.getDomainName()</code> on macOS and the BSDs returns the canonical name rather than an empty string in both implementations - <a href="https://github.com/dbwiddis";><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3705";>#3705</a>: An AIX process or thread that exits between enumeration and the <code>/proc</code> read is now reported as invalid rather than as a live process owned by root - <a href="https://github.com/dbwiddis";><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3705";>#3705</a>: A failure of <code>kstat_open()</code> on Solaris throws rather than releasing no lock and passing a null control structure to the kernel. The chain lock is static, so a failed open previously blocked every later kstat query on any thread - <a href="https://github.com/dbwiddis";><code>@dbwiddis</code></a>.</li> </ul> <p><a href="https://github.com/oshi/oshi/blob/master/CHANGELOG.md";>Full change log</a></p> <h2>Release 7.5.0</h2> <h5>New Features</h5> <ul> <li><a href="https://redirect.github.com/oshi/oshi/pull/3614";>#3614</a> - <a href="https://redirect.github.com/oshi/oshi/pull/3636";>#3636</a>: Adopt <a href="https://jspecify.dev/";>JSpecify</a> nullability annotations project-wide and enforce them in continuous integration with <a href="https://github.com/uber/NullAway";>NullAway</a>, so every type in a signature is non-null unless it is annotated <code>@Nullable</code>. A method not annotated <code>@Nullable</code> is now a checked guarantee rather than an aspiration, and a null check against one is dead code you can delete. The public API packages and the <code>oshi.util</code> tree carry the marking in their <code>package-info.java</code>, where every consumer sees it, including on a Java 8 or classpath build; the implementation packages are marked on their module descriptors; the native mapping packages under <code>oshi.jna</code> and <code>oshi.ffm.platform</code> opt out, because nullability there is the operating system's to state rather than OSHI's. The <code>org.jspecify:jspecify</code> dependency is optional and compile-time only, so it does not reach your runtime classpath. See the <a href="https://github.com/oshi/oshi/blob/HEAD/FAQ.md#nullability-nullmarked-nullable";>FAQ</a> for what this does and does not promise - <a href="https://github.com/dbwiddis";><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3615";>#3615</a>: Add <code>ParseUtil.getStringValueOrEmpty</code>, which normalizes a nullable string to <code>""</code>, alongside the existing <code>getStringValueOrUnknown</code> - <a href="https://github.com/dbwiddis";><code>@dbwiddis</code></a>.</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/oshi/oshi/blob/master/CHANGELOG.md";>com.github.oshi:oshi-core's changelog</a>.</em></p> <blockquote> <h1>7.6.0 (2026-08-23), 7.6.1 (2026-09-01)</h1> <p>The <code>oshi-dist</code> zip is no longer published to Maven Central; download it from the <a href="https://github.com/oshi/oshi/releases";>GitHub release</a> instead.</p> <h5>New Features</h5> <ul> <li><a href="https://redirect.github.com/oshi/oshi/pull/3652";>#3652</a>: <code>oshi-metrics</code> reports the OpenTelemetry <code>reserved</code> state for <code>system.filesystem.usage</code> and <code>system.filesystem.utilization</code>, alongside the existing <code>used</code> and <code>free</code>. The three states partition the filesystem, so the <code>usage</code> gauges sum to <code>system.filesystem.limit</code> and the <code>utilization</code> gauges sum to 1.0 - <a href="https://github.com/dbwiddis";><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3660";>#3660</a>, <a href="https://redirect.github.com/oshi/oshi/pull/3678";>#3678</a>: <code>Display.getDevicePort()</code> reports the port a display is attached to, and on systems with X RandR, <code>Display.getOutputName()</code> gives the name <code>xrandr --output</code> accepts for it - <a href="https://github.com/ayonization";><code>@ayonization</code></a>, <a href="https://github.com/dbwiddis";><code>@dbwiddis</code></a>.</li> </ul> <h5>Behavior Changes</h5> <ul> <li><a href="https://redirect.github.com/oshi/oshi/pull/3705";>#3705</a>: <code>OSDesktopWindow.getLocAndSize()</code> returns a copy of the window's <code>Rectangle</code> and the constructor copies the one it is given, so the class honors the immutability its documentation promises. <code>ApplicationInfo.getAdditionalInfo()</code> returns an unmodifiable map. Code that wrote through either return value silently mutated OSHI's own state; it now has no effect, or throws <code>UnsupportedOperationException</code> for the map - <a href="https://github.com/dbwiddis";><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3705";>#3705</a>: <code>UsbDevice.compareTo()</code> breaks ties on the unique device ID, vendor ID, product ID and serial number after comparing names, and <code>AbstractUsbDevice</code> implements <code>equals()</code> and <code>hashCode()</code> over the same fields. Two distinct devices sharing a name previously compared equal, so a <code>TreeSet</code> or <code>SortedSet</code> of them kept only one. The ordering is now a default method on <code>UsbDevice</code>, so every implementation shares it - <a href="https://github.com/dbwiddis";><code>@dbwiddis</code></a>.</li> </ul> <h5>Bug Fixes and Improvements</h5> <ul> <li><a href="https://redirect.github.com/oshi/oshi/pull/3651";>#3651</a>: <code>OSFileStore</code> now guarantees <code>0 <= getUsableSpace() <= getFreeSpace() <= getTotalSpace()</code> on every platform. The three values are read by separate queries, so on a ZFS dataset or a swap-backed <code>tmpfs</code> they could previously contradict each other; they are now clamped downward to restore the ordering - <a href="https://github.com/dbwiddis";><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3657";>#3657</a>: Fix the <code>TcpState</code> for the FFM implementation of <code>InternetProtocolStats.getConnections()</code> on macOS and set the process cap from the kernel - <a href="https://github.com/dbwiddis";><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3661";>#3661</a>: Setting <code>oshi.os.windows.hkeyperfdata</code> to <code>false</code> now also skips the registry when fetching thread counters, matching its documented behavior and the existing handling for processes - <a href="https://github.com/dbwiddis";><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3662";>#3662</a>: Reading the processor description from the registry no longer throws when a value is missing. <code>CentralProcessor.getFeatureFlags()</code> on Windows now reports every processor feature <code>IsProcessorFeaturePresent()</code> accepts, matching the <code>PF_</code> defines in <code>winnt.h</code> - <a href="https://github.com/dbwiddis";><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3665";>#3665</a>: <code>NetworkParams.getRoutes()</code> reads the routing table from the kernel through a <code>NET_RT_DUMP</code> sysctl on macOS, FreeBSD, DragonFly BSD and OpenBSD, rather than by running <code>netstat</code> twice - <a href="https://github.com/dbwiddis";><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3670";>#3670</a>: <code>NetworkParams.getHostName()</code> on Linux reads the kernel host name from <code>/proc/sys/kernel/hostname</code> in every backend, fixing the native-free implementation, which truncated a fully qualified name at the first dot and reported <code>localhost</code> when the name did not resolve - <a href="https://github.com/dbwiddis";><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3671";>#3671</a>: <code>NetworkParams.getHostName()</code> and <code>getDomainName()</code> report the empty-string sentinel when the local host name does not resolve, rather than the loopback address's <code>localhost</code>. NetBSD is the most affected platform, having no native host name query of its own - <a href="https://github.com/dbwiddis";><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3672";>#3672</a>, <a href="https://redirect.github.com/oshi/oshi/pull/3674";>#3674</a>: <code>CentralProcessor</code> frequencies and <code>PhysicalProcessor.getEfficiency()</code> on Apple Silicon are correct regardless of call order and on the M4 and M5 generations. Frequencies previously fell back to a 2.4 GHz placeholder unless <code>getProcessorIdentifier()</code> happened to be called first, were reported a thousand times too low on the M4 and later, and a chip with more or fewer than two kinds of core was misclassified - <a href="https://github.com/dbwiddis";><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3675";>#3675</a>: <code>CentralProcessor.getCurrentFreq()</code> on Apple Silicon can report the frequency the hardware actually ran at, rather than a nominal maximum that never changes. Set <code>oshi.os.mac.cpu.frequency.ioreport</code> to <code>true</code>; it is opt-in because it holds a subscription to a private framework for the lifetime of the process - <a href="https://github.com/dbwiddis";><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3680";>#3680</a>: <code>oshi-metrics</code> reads a disk or network interface once per memoizer expiration window rather than once per meter, so a scrape makes one query where it previously made five or seven, and the meters of one device report the same reading. A rate computed across two of them, such as errors per packet, is now comparable - <a href="https://github.com/dbwiddis";><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3681";>#3681</a>: <code>GpuStats.getGpuUtilization()</code> on Linux reads NVIDIA GPU utilization from NVML. It previously read only the amdgpu/i915/xe sysfs paths, none of which the NVIDIA driver exposes, so an NVIDIA card always returned the -1 sentinel - <a href="https://github.com/Krillsson";><code>@Krillsson</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3686";>#3686</a>: <code>GpuStats.getGpuUtilization()</code> on Windows reads NVIDIA utilization from NVML and AMD utilization from ADL, matching the source order of every other metric on the class. It previously ran only LibreHardwareMonitor and a PDH engine-tick delta, which needs two samples, so the first call returned the -1 sentinel - <a href="https://github.com/dbwiddis";><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3687";>#3687</a>: <code>GpuStats.getSharedMemoryUsed()</code> on Linux reports the amdgpu GTT memory in use rather than always returning -1, and <code>GraphicsCard.getVRam()</code> on an amdgpu card reports the driver's own figure rather than the memory BAR size parsed from <code>lspci</code> or <code>lshw</code>. Several <code>GpuStats</code> metrics on Linux also now return the -1 sentinel when the sysfs file behind them is absent; they previously reported 0, so a card whose hwmon directory omits <code>power1_average</code> read as drawing 0.0 W - <a href="https://github.com/dbwiddis";><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3698";>#3698</a>: <code>OSProcess.getCurrentWorkingDirectory()</code> on macOS returns the directory rather than an empty string in the FFM implementation, and <code>NetworkParams.getDomainName()</code> on macOS and the BSDs returns the canonical name rather than an empty string in both implementations - <a href="https://github.com/dbwiddis";><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3705";>#3705</a>: An AIX process or thread that exits between enumeration and the <code>/proc</code> read is now reported as invalid rather than as a live process owned by root - <a href="https://github.com/dbwiddis";><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3705";>#3705</a>: A failure of <code>kstat_open()</code> on Solaris throws rather than releasing no lock and passing a null control structure to the kernel. The chain lock is static, so a failed open previously blocked every later kstat query on any thread - <a href="https://github.com/dbwiddis";><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3710";>#3710</a>: Fix the bnd imports for <code>oshi-core</code> and <code>oshi-core-ffm</code> to make the JSpecify annotations optional, so both bundles resolve in an OSGi container without JSpecify - <a href="https://github.com/dbwiddis";><code>@dbwiddis</code></a>.</li> </ul> <h1>7.5.0 (2026-08-16)</h1> <h5>New Features</h5> <ul> <li><a href="https://redirect.github.com/oshi/oshi/pull/3614";>#3614</a>, <a href="https://redirect.github.com/oshi/oshi/pull/3615";>#3615</a>, <a href="https://redirect.github.com/oshi/oshi/pull/3618";>#3618</a>, <a href="https://redirect.github.com/oshi/oshi/pull/3619";>#3619</a>, <a href="https://redirect.github.com/oshi/oshi/pull/3620";>#3620</a>, <a href="https://redirect.github.com/oshi/oshi/pull/3621";>#3621</a>, <a href="https://redirect.github.com/oshi/oshi/pull/3622";>#3622</a>, <a href="https://redirect.github.com/oshi/oshi/pull/3623";>#3623</a>, <a href="https://redirect.github.com/oshi/oshi/pull/3624";>#3624</a>, <a href="https://redirect.github.com/oshi/oshi/pull/3625";>#3625</a>,</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/oshi/oshi/commit/25f0879377f9e5c54ed26e3b549b8e22a4e5717f";><code>25f0879</code></a> [maven-release-plugin] prepare release oshi-parent-7.6.1</li> <li><a href="https://github.com/oshi/oshi/commit/6e133947d2d8a892ab5cd98dbb3c3d037e71f58d";><code>6e13394</code></a> 7.6.1 Release</li> <li><a href="https://github.com/oshi/oshi/commit/210e5d8a14c390dd9cc12f035a89bcc8d073c1c2";><code>210e5d8</code></a> Update vmactions/netbsd-vm digest to 07366ff (<a href="https://redirect.github.com/oshi/oshi/issues/3721";>#3721</a>)</li> <li><a href="https://github.com/oshi/oshi/commit/64b059fb956eb57b7d9343c9b5ca244263361537";><code>64b059f</code></a> Update dependency com.puppycrawl.tools:checkstyle to v14.1.0 (<a href="https://redirect.github.com/oshi/oshi/issues/3722";>#3722</a>)</li> <li><a href="https://github.com/oshi/oshi/commit/03a7c19bb829f58b2b756745f00c13def29da1f5";><code>03a7c19</code></a> Update dependency com.uber.nullaway:nullaway to v0.14.1 (<a href="https://redirect.github.com/oshi/oshi/issues/3720";>#3720</a>)</li> <li><a href="https://github.com/oshi/oshi/commit/6587c9ee6e504c806d16f5c3af9fe87464f8e440";><code>6587c9e</code></a> Update dependency de.skuzzle.enforcer:restrict-imports-enforcer-rule to v3.0....</li> <li><a href="https://github.com/oshi/oshi/commit/8f54587d7cbf3b9b9da342e6e28c561b6e433b9e";><code>8f54587</code></a> Update dependency com.diffplug.spotless:spotless-maven-plugin to v3.10.1 (<a href="https://redirect.github.com/oshi/oshi/issues/3718";>#3718</a>)</li> <li><a href="https://github.com/oshi/oshi/commit/afdde977a052e66f784a4469c7dc87c30067d661";><code>afdde97</code></a> Update github/codeql-action digest to cdf488f (<a href="https://redirect.github.com/oshi/oshi/issues/3712";>#3712</a>)</li> <li><a href="https://github.com/oshi/oshi/commit/4d275a8cf3b8699e717e1b49b1b8ac246069b076";><code>4d275a8</code></a> Update vmactions/openindiana-vm digest to 21e57a4 (<a href="https://redirect.github.com/oshi/oshi/issues/3717";>#3717</a>)</li> <li><a href="https://github.com/oshi/oshi/commit/683b91b8ae33d5761590beeb04c889722eb97734";><code>683b91b</code></a> Update vmactions/openbsd-vm digest to 86cdc08 (<a href="https://redirect.github.com/oshi/oshi/issues/3716";>#3716</a>)</li> <li>Additional commits viewable in <a href="https://github.com/oshi/oshi/compare/oshi-parent-6.12.0...oshi-parent-7.6.1";>compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
