Bump nerves_runtime from 0.13.8 to 0.13.9 in /hello_gpio in the deps group

[dependabot]

Bumps the deps group in /hello_gpio with 1 update: nerves_runtime.

Updates nerves_runtime from 0.13.8 to 0.13.9

Release notes

Sourced from nerves_runtime's releases.

v0.13.9

• Changes

  • Document application config keys. These are now official. If you had been modifying the application config for regression tests, note that the :env key is now :fwup_env and :revert_fw_path is now ops_fw_path.

  • Add Nerves.Runtime.firmware_slots/0 to return a map indicating the currently running slot and the one that will be run on next boot. Please update any calls to get "nerves_fw_active" directly from Nerves.Runtime.KV since the new firmware_slots/0 is more accurate and handles more scenarios on Nerves devices.

  • Add firmware_validation_status/0 to allow callers to know whether the status is really unknown. This isn't possible with firmware_valid?/0 which is problematic since unknown could mean that the U-Boot environment is unreadable and a fix is needed. Instead firmware_valid?/0 returns true in that case since this could be an old Nerves device without validation.

  • Replace call to Busybox mount to determine filesystem read-only status with a module that reads /proc/self/mountinfo.

  • Expose mount information via Nerves.Runtime.MountInfo. If you had been using MountParser, please update your calls. MountParser was not intended to be public API (@​moduledoc false) and was removed.

  • Serialize calls to fwup to reduce chance of accidental eMMC/MicroSD corruption

  • Bulletproof many functions to return errors if the :nerves_runtime application stops. This can happen when the device is not in a good state and raising in NervesRuntime KV and FwupOps functions made things worse. This should be a rare case.

Changelog

Sourced from nerves_runtime's changelog.

v0.13.9 - 2025-09-18

• Changes

  • Document application config keys. These are now official. If you had been modifying the application config for regression tests, note that the :env key is now :fwup_env and :revert_fw_path is now ops_fw_path.

  • Add Nerves.Runtime.firmware_slots/0 to return a map indicating the currently running slot and the one that will be run on next boot. Please update any calls to get "nerves_fw_active" directly from Nerves.Runtime.KV since the new firmware_slots/0 is more accurate and handles more scenarios on Nerves devices.

  • Add firmware_validation_status/0 to allow callers to know whether the status is really unknown. This isn't possible with firmware_valid?/0 which is problematic since unknown could mean that the U-Boot environment is unreadable and a fix is needed. Instead firmware_valid?/0 returns true in that case since this could be an old Nerves device without validation.

  • Replace call to Busybox mount to determine filesystem read-only status with a module that reads /proc/self/mountinfo.

  • Expose mount information via Nerves.Runtime.MountInfo. If you had been using MountParser, please update your calls. MountParser was not intended to be public API (@​moduledoc false) and was removed.

  • Serialize calls to fwup to reduce chance of accidental eMMC/MicroSD corruption

  • Bulletproof many functions to return errors if the :nerves_runtime application stops. This can happen when the device is not in a good state and raising in NervesRuntime KV and FwupOps functions made things worse. This should be a rare case.

Commits

• b7daa82 v0.13.9 release
• 9a2731d Bump ex_doc
• 08e4a19 Add tests for returning errors when the app is stopped
• 6224951 Bulletproof KV calls to avoid surprises when Nerves.Runtime fails
• 93b2c5d Minor internal function rename
• ac1f6fd Run copyright header script
• e609443 Use mountinfo parsing for mount checks; add public parse/1 and read_only?/1 APIs
• 89ffb28 Bump dialyxir from 1.4.5 to 1.4.6
• dadd9be Add firmware_slots/0 to expose firmware slot info
• 9ce1b7e Serialize fwup ops.fw access via a GenServer
• Additional commits viewable in compare view

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 commands and options

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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions