Project updates

A lot of REUSE implementation being released in this batch. Frank did most of the drudging grunt work on this. Why? Because it standardizes copyright and license information in a compliant way and serves to help all SBOM efforts. This in turn serves Nerves and Elixir in making compliance easier in various industries and under recent legislation.

It also makes it more obvious when people fork repos in non-compliant ways as there are now copyright headers in every file, which should be retained.

Since REUSE isn't really a change to code typically these changes make it out as new releases are made for other reasons. As you can see below. Elixir 1.19 brought some warnings. There is also incoming work for making Erlang/OTP 28 ready to use with Nerves but it is not in this batch.

uboot_env, v1.0.2

• Fix Elixir 1.19 warning
• Update licensing and copyright for REUSE compliance

vintage_net_wifi, v0.12.7

This release makes VintageNet compliant with the REUSE Specification .

• Fixes

  • Removed dependency on GenStateMachine and use :gen_statem directly. There’s no change in functionality, but it will remove the compilation warnings when building the GenStateMachine dependency.
  • Fix Elixir 1.19 warning
    

• Changed

  • Only support Elixir 1.14 and later. It should work with Elixir 1.13 still, but this may change in the future without us noticing. Other libraries are requiring Elixir 1.14 and later, so please upgrade if this affects you.

nerves_system_br, v1.31.3

This is a bug fix update for 1.31.2.

• Package updates
  • erlinit 1.14.3
  • rpi-libcamera v0.5.0+rpt20250429
  • rpicam-apps 1.7.0

nerves_system_br, v1.31.2

This is a security/bug fix update for 1.31.1. It has the fix to CVE-2025-4748 .

• Package updates
  • Erlang/OTP 27.3.4.1
  • Raspberry Pi WiFi firmware 1:20240709-2~bpo12+1+rpt3

erlinit, v1.14.3

This release has many non-code affecting changes to make copyright and licensing information machine readable. Erlinit is now REUSE compliant.

• Bug fixes
  • Fix issue causing stdin to be incorrectly closed and causing Erlang to exit. This was a deterministic issue, so if you haven’t seen it, it doesn’t affect you.

nerves_uevent, v0.1.2

• Updates
  • Improve C compilation error message to help custom Nerves systems builders
  • Fix Elixir 1.19 warning

vintage_net, v0.13.7

This release makes VintageNet compliant with the REUSE Specification .

• Fixes

  • Removed dependency on GenStateMachine and use :gen_statem directly. There’s no change in functionality, but it will remove the compilation warnings when building the GenStateMachine dependency.
  • Fix Elixir 1.19 warnings
  • Improve the error message when host compilation fails
    

• Changed

  • Only support Elixir 1.14 and later. It should work with Elixir 1.13 still, but this may change in the future without us noticing. Other libraries are requiring Elixir 1.14 and later, so please upgrade if this affects you.

vintage_net_qmi, v0.4.4

Added

• Licensing and copyright clarifications for REUSE compliance

Changed

• Elixir 1.19 error and warning fixes

qmi, v0.10.1

• Update licensing and copyright for REUSE compliance
• Ignore invalid emergency access barred values that were seen in the wild

Participating in the community

The Nerves community is found wherever Elixirists gather. Try any of the following:

Questions are best asked on the Elixir Forum .

Social conversation and banter:

• Elixir Slack , #nerves channel
• Elixir Discord , #nerves channel

How you can help Nerves

Contribute in the way that works for you:

• Send corrections or improvements for documentation wherever it fails to help you.
• Write about Nerves, give talks about Nerves. Make videos about Nerves. It is all good.
• Write or port a new hardware library and include it in the Elixir Circuits collection .
• Get in touch about taking over maintenance duties for some libraries, we might be able to provide you hardware.
• Apply for an EEF stipend on something Nerves-related and build it. We can help if you have questions about this.

Finally, if you have questions about the newsletter or want to suggest something you can simply respond to this email.

- Lars