Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency com.pi4j:pi4j-core to v2.6.1 #31

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Sep 25, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
com.pi4j:pi4j-core (source) 2.1.1 -> 2.6.1 age adoption passing confidence

Release Notes

Pi4J/pi4j-v2 (com.pi4j:pi4j-core)

v2.6.1

Compare Source

v2.6.0: PWM and I2C Improvements

Compare Source

Thanks to contributions by @​fusetim, @​taartspi, @​eitch, @​fdelporte.

Make sure to also read the interviews with Robert von Burg and Tom Aarts.

All changes: Pi4J/pi4j-v2@2.5.1...2.6.0

v2.5.1: Correct native code for GpioD

Compare Source

Sorry! Because of a configuration error, the wrong native code is included in 2.5.0 for the new GpioD Provider. But thanks to the lightning fast action of Robert von Burg we have a fixed version for you to enjoy :-)`

For all other info about the changes in 2.5, see the release notes of 2.5.0.

v2.5.0: A lot of changes and... support for Raspberry Pi 5!

Compare Source

With over 100 commits from multiple branches, this is a major release with many improvements! With many thanks to the core team (Robert von Burg, Tom Aarts), and a major addition of Alexander Liggesmeyer, Pi4J is again lifted to a higher level!

Warning, the new GpioD Provider needs the latest Raspberry Pi OS version (Debian GNU/Linux 12 (bookworm))

Changes in 2.5.0

  • A new GpioD Provider adds support for the Raspberry Pi 5.
    • Issues #​321, #​320, #​317
    • This new GpioD provider interfaces directly with the Raspberry Pi's gpiochip device, located at /dev/gpiochip.... It leverages the native libgpiod library, which is developed as a part of the Linux kernel. Libgpiod is currently the recommended way to control GPIO pins. Therefore, using this provider is also recommended.
    • This new provider can be used without the need to start a Pi4J application with sudo, so also fixes #​212 when you only need DigitalInput and/or DigitalOutput.
  • Better handling of mock Plugins: Plugins can now define if they are mocks, and these are not auto-detected anymore. The default target for the Pi4J library is the Raspberry Pi, and thus auto-detecting mocks on the Pi, which are only for tests is counterintuitive.
  • Extended Providers with a priority: this priority helps to determine which Provider should be loaded, when multiple Providers with the same IOType are being loaded by different plugins. This change enforces that a given IOType can only have one Provider loaded at runtime preventing errors when, for instance, two I2C providers are loaded at the same time, concurrently writing to the I2C bus.
  • Fix for: LinuxFile reused scratch buffers ensuring size was usable. But the limit value cannot be modified so later usage failed as an intended overwrite. Pull request #​331, commit ed208f2.
  • Fix for: I2C interface should use a restart between the write and read operation. Pull request #​333.
  • Fix for: Shutting down pool executor too early. Commit 7909a2d.
  • ProviderProxyHandler got removed, simplifying provider loading, thus no more reflection on the instances.
  • You can now add and remove IO instances at runtime.
  • You can now easily switch a GPIO from output to an input and vice versa, see issue #​26, extending on the work by @​MEBoo, in pull request #​1.
  • A race condition got fixed in the default runtime registry.
  • Proper life cycle management got added for of all threads in Pi4J.

All changes: Pi4J/pi4j-v2@2.4.0...2.5.0

Known Issue

  • java.io.IOException: Remote I/O error java.base/java.io.RandomAccessFile.writeBytes(Native Method). Using linuxfs-i2c, dependent upon i2c operations this exception can occur: If the program initially uses read or write, and later uses readRegister or writeRegister there is no exception. However, if the program initially uses readRegister or writeRegister subsequent write or read may encounter this exception. For more info and the temporary fix, check #​335.

v2.4.0

Compare Source

Thanks to @​GeVanCo, @​MMMMMNG, @​IAmNickNack, @​savageautomate, @​eitch, @​taartspi, @​FDelporte

v2.3.0: - SPI and PiGPIO Improvements

Compare Source

v2.2.1: - SPI improvements

Compare Source

Multiple fixes by @​taartspi

  • Better error message when mixing 32- and 64-bit artifacts
  • SPI improvements:
    • Add missing initialization in constructor
    • Track weather the user set the mode or bus config values to improve the use of SPI flags

v2.2.0

Compare Source

Thanks to all contributors, multiple improvements were added:


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/com.pi4j-pi4j-core-2.x branch from 628a7e1 to 82c01f6 Compare November 20, 2022 21:24
@renovate renovate bot changed the title Update dependency com.pi4j:pi4j-core to v2.2.0 Update dependency com.pi4j:pi4j-core to v2.2.1 Nov 20, 2022
@renovate renovate bot force-pushed the renovate/com.pi4j-pi4j-core-2.x branch from 82c01f6 to 0ad4299 Compare March 17, 2023 12:10
@renovate renovate bot changed the title Update dependency com.pi4j:pi4j-core to v2.2.1 Update dependency com.pi4j:pi4j-core to v2.3.0 Mar 17, 2023
@renovate renovate bot changed the title Update dependency com.pi4j:pi4j-core to v2.3.0 Update dependency com.pi4j:pi4j-core to v2.4.0 Oct 24, 2023
@renovate renovate bot force-pushed the renovate/com.pi4j-pi4j-core-2.x branch from 0ad4299 to 1bd6643 Compare October 24, 2023 11:32
@renovate renovate bot force-pushed the renovate/com.pi4j-pi4j-core-2.x branch from 1bd6643 to 0ec5c9e Compare March 18, 2024 15:04
@renovate renovate bot changed the title Update dependency com.pi4j:pi4j-core to v2.4.0 Update dependency com.pi4j:pi4j-core to v2.5.0 Mar 18, 2024
@renovate renovate bot force-pushed the renovate/com.pi4j-pi4j-core-2.x branch from 0ec5c9e to 9d6246e Compare March 21, 2024 13:27
@renovate renovate bot changed the title Update dependency com.pi4j:pi4j-core to v2.5.0 Update dependency com.pi4j:pi4j-core to v2.5.1 Mar 21, 2024
@renovate renovate bot force-pushed the renovate/com.pi4j-pi4j-core-2.x branch from 9d6246e to abf88d3 Compare April 29, 2024 15:38
@renovate renovate bot changed the title Update dependency com.pi4j:pi4j-core to v2.5.1 Update dependency com.pi4j:pi4j-core to v2.6.0 Apr 29, 2024
@renovate renovate bot changed the title Update dependency com.pi4j:pi4j-core to v2.6.0 Update dependency com.pi4j:pi4j-core to v2.6.1 Jul 26, 2024
@renovate renovate bot force-pushed the renovate/com.pi4j-pi4j-core-2.x branch from abf88d3 to f127e2b Compare July 26, 2024 16:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants