dependabot[bot] opened a new pull request, #755: URL: https://github.com/apache/karaf-decanter/pull/755
Bumps [com.github.oshi:oshi-core](https://github.com/oshi/oshi) from 6.12.0 to 7.7.0. <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.7.0</h2> <h5>New Features</h5> <ul> <li><a href="https://redirect.github.com/oshi/oshi/pull/3745">#3745</a>: The FFM implementation now reads NetBSD natively, through <code>sysctl</code>, <code>getloadavg</code>, <code>_lwp_self</code> and <code>getrlimit</code>, where it previously ran commands and parsed their output - <a href="https://github.com/dbwiddis"><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3709">#3709</a>, <a href="https://redirect.github.com/oshi/oshi/pull/3757">#3757</a>: <code>Display.getCurrentMode()</code> returns the mode a display is driven in: its logical and pixel resolution, refresh rate, rotation, and position on the desktop. <code>Display.isBuiltIn()</code> reports whether it is a built-in panel, and <code>Display.isPrimary()</code> whether it is the primary display. All three are available on Windows, macOS, and on Linux and the other UNIX platforms through X11 - <a href="https://github.com/ayonization"><code>@ayonization</code></a>, <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/3723">#3723</a>: Windows <code>Sensors</code> now reads CPU temperature, fan speed and voltage from the <code>ROOT\LibreHardwareMonitor</code> WMI namespace when the LibreHardwareMonitor application is running, in addition to the <code>ROOT\OpenHardwareMonitor</code> namespace it already read. Users running the maintained LibreHardwareMonitor previously got its GPU metrics but no CPU sensor data - <a href="https://github.com/dbwiddis"><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3727">#3727</a>: The <code>oshi.os.windows.ohm.disabled</code> and <code>oshi.os.windows.lhm.disabled</code> configuration properties now skip the Open Hardware Monitor and Libre Hardware Monitor WMI namespaces, which OSHI otherwise queries on each sensor read until one returns data. The latter also covers GPU metrics - <a href="https://github.com/dbwiddis"><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3730">#3730</a>: Fixed <code>Sensors.getCpuVoltage()</code> on Windows when using the voltage published by Open Hardware Monitor or LibreHardwareMonitor - <a href="https://github.com/dbwiddis"><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3742">#3742</a>: <code>NetworkParams.getRoutes()</code> on NetBSD now reads the routing table from the kernel where the JNA native library is available - <a href="https://github.com/dbwiddis"><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3743">#3743</a>: Fixed three <code>HWDiskStore</code> faults on NetBSD: read and write byte totals that could decrease between readings, a doubled <code>getTransferTime()</code>, and a 1-byte disk or 512-byte partition size where the size is unknown, which also affected OpenBSD - <a href="https://github.com/dbwiddis"><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3744">#3744</a>: Fixed <code>OSProcess</code> naming on NetBSD: <code>getPath()</code> and <code>getName()</code> were truncated to seven characters, and where the kernel withholds a process's arguments, <code>getCommandLine()</code> returned <code>ps</code>'s <code>(command)</code> placeholder and <code>getName()</code> kept its parentheses - <a href="https://github.com/dbwiddis"><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3754">#3754</a>: <code>OperatingSystem.getProcessId()</code> and <code>getThreadId()</code> return 0 when the ID is unknown on every platform. On NetBSD without JNA, <code>getThreadId()</code> returned a Java thread ID, and on failure some implementations returned -1, which led <code>getCurrentProcess()</code> to return an arbitrary process on the BSDs, Solaris and AIX. <code>getProcess()</code> with a negative PID now returns null on Solaris and AIX - <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.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> </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.7.0 (2026-09-29)</h1> <h5>New Features</h5> <ul> <li><a href="https://redirect.github.com/oshi/oshi/pull/3745">#3745</a>: The FFM implementation now reads NetBSD natively, through <code>sysctl</code>, <code>getloadavg</code>, <code>_lwp_self</code> and <code>getrlimit</code>, where it previously ran commands and parsed their output - <a href="https://github.com/dbwiddis"><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3709">#3709</a>, <a href="https://redirect.github.com/oshi/oshi/pull/3757">#3757</a>: <code>Display.getCurrentMode()</code> returns the mode a display is driven in: its logical and pixel resolution, refresh rate, rotation, and position on the desktop. <code>Display.isBuiltIn()</code> reports whether it is a built-in panel, and <code>Display.isPrimary()</code> whether it is the primary display. All three are available on Windows, macOS, and on Linux and the other UNIX platforms through X11 - <a href="https://github.com/ayonization"><code>@ayonization</code></a>, <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/3723">#3723</a>: Windows <code>Sensors</code> now reads CPU temperature, fan speed and voltage from the <code>ROOT\LibreHardwareMonitor</code> WMI namespace when the LibreHardwareMonitor application is running, in addition to the <code>ROOT\OpenHardwareMonitor</code> namespace it already read. Users running the maintained LibreHardwareMonitor previously got its GPU metrics but no CPU sensor data - <a href="https://github.com/dbwiddis"><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3727">#3727</a>: The <code>oshi.os.windows.ohm.disabled</code> and <code>oshi.os.windows.lhm.disabled</code> configuration properties now skip the Open Hardware Monitor and Libre Hardware Monitor WMI namespaces, which OSHI otherwise queries on each sensor read until one returns data. The latter also covers GPU metrics - <a href="https://github.com/dbwiddis"><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3730">#3730</a>: Fixed <code>Sensors.getCpuVoltage()</code> on Windows when using the voltage published by Open Hardware Monitor or LibreHardwareMonitor - <a href="https://github.com/dbwiddis"><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3742">#3742</a>: <code>NetworkParams.getRoutes()</code> on NetBSD now reads the routing table from the kernel where the JNA native library is available - <a href="https://github.com/dbwiddis"><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3743">#3743</a>: Fixed three <code>HWDiskStore</code> faults on NetBSD: read and write byte totals that could decrease between readings, a doubled <code>getTransferTime()</code>, and a 1-byte disk or 512-byte partition size where the size is unknown, which also affected OpenBSD - <a href="https://github.com/dbwiddis"><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3744">#3744</a>: Fixed <code>OSProcess</code> naming on NetBSD: <code>getPath()</code> and <code>getName()</code> were truncated to seven characters, and where the kernel withholds a process's arguments, <code>getCommandLine()</code> returned <code>ps</code>'s <code>(command)</code> placeholder and <code>getName()</code> kept its parentheses - <a href="https://github.com/dbwiddis"><code>@dbwiddis</code></a>.</li> <li><a href="https://redirect.github.com/oshi/oshi/pull/3754">#3754</a>: <code>OperatingSystem.getProcessId()</code> and <code>getThreadId()</code> return 0 when the ID is unknown on every platform. On NetBSD without JNA, <code>getThreadId()</code> returned a Java thread ID, and on failure some implementations returned -1, which led <code>getCurrentProcess()</code> to return an arbitrary process on the BSDs, Solaris and AIX. <code>getProcess()</code> with a negative PID now returns null on Solaris and AIX - <a href="https://github.com/dbwiddis"><code>@dbwiddis</code></a>.</li> </ul> <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> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/oshi/oshi/commit/fa2eb031882e3609f06770caaf9bb97688f104d2"><code>fa2eb03</code></a> [maven-release-plugin] prepare release oshi-parent-7.7.0</li> <li><a href="https://github.com/oshi/oshi/commit/4471a73a45b920feabc7d547d1f7a4b85f9cdebf"><code>4471a73</code></a> 7.7.0 Release</li> <li><a href="https://github.com/oshi/oshi/commit/f9b03d0cbef901d971fea7783e383e49469e11dd"><code>f9b03d0</code></a> Update vmactions/openbsd-vm digest to 5f7b2c9 (<a href="https://redirect.github.com/oshi/oshi/issues/3759">#3759</a>)</li> <li><a href="https://github.com/oshi/oshi/commit/698d32aca702b523a1e27de3c119ad7e31d7fece"><code>698d32a</code></a> Update vmactions/openindiana-vm digest to d82e630 (<a href="https://redirect.github.com/oshi/oshi/issues/3760">#3760</a>)</li> <li><a href="https://github.com/oshi/oshi/commit/5b4722aff641637bfdcb11361619c508296074d1"><code>5b4722a</code></a> Update dependency com.puppycrawl.tools:checkstyle to v14.3.0 (<a href="https://redirect.github.com/oshi/oshi/issues/3761">#3761</a>)</li> <li><a href="https://github.com/oshi/oshi/commit/0a4401b5670dd356f93b452a920b47c80294db4b"><code>0a4401b</code></a> Update vmactions/netbsd-vm digest to c8a0d7d (<a href="https://redirect.github.com/oshi/oshi/issues/3758">#3758</a>)</li> <li><a href="https://github.com/oshi/oshi/commit/171d674d66ba2f7446eb071f9efebfb2f0a1dd40"><code>171d674</code></a> Add isPrimary to the Display API (<a href="https://redirect.github.com/oshi/oshi/issues/3709">#3709</a>)</li> <li><a href="https://github.com/oshi/oshi/commit/b71fdfa9845763687377808c844bee11c26cc37d"><code>b71fdfa</code></a> Add Display.getCurrentMode() and isBuiltIn() (<a href="https://redirect.github.com/oshi/oshi/issues/3757">#3757</a>)</li> <li><a href="https://github.com/oshi/oshi/commit/7ad544508c2b5b35dd405ab8b8762338e065be92"><code>7ad5445</code></a> Update vmactions/freebsd-vm digest to a2f9a41 (<a href="https://redirect.github.com/oshi/oshi/issues/3756">#3756</a>)</li> <li><a href="https://github.com/oshi/oshi/commit/726d2d044ade5a01123ffa828fd751bda38429d0"><code>726d2d0</code></a> Update vmactions/dragonflybsd-vm digest to 4ab776f (<a href="https://redirect.github.com/oshi/oshi/issues/3755">#3755</a>)</li> <li>Additional commits viewable in <a href="https://github.com/oshi/oshi/compare/oshi-parent-6.12.0...oshi-parent-7.7.0">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]
