Skip to content

Conversation

@nfbot
Copy link
Member

@nfbot nfbot commented Mar 12, 2025

Bumps nanoFramework.CoreLibrary from 1.17.1 to 1.17.7
Bumps nanoFramework.Graphics.Core from 1.2.39 to 1.2.42
Bumps nanoFramework.Hardware.Esp32 from 1.6.31 to 1.6.33
Bumps nanoFramework.Hardware.Esp32.Rmt from 2.0.29 to 2.0.32
Bumps nanoFramework.Iot.Device.Button from 1.2.822 to 1.2.852
Bumps nanoFramework.Iot.Device.Ws28xx.Esp32 from 1.2.835 to 1.2.852
Bumps nanoFramework.Runtime.Events from 1.11.30 to 1.11.31
Bumps nanoFramework.System.Device.Adc from 1.1.22 to 1.1.23
Bumps nanoFramework.System.Device.Dac from 1.5.24 to 1.5.25
Bumps nanoFramework.System.Device.Gpio from 1.1.55 to 1.1.56
Bumps nanoFramework.System.Device.I2c from 1.1.27 to 1.1.28
Bumps nanoFramework.System.Device.Spi from 1.3.77 to 1.3.79
Bumps nanoFramework.Iot.Device.Mpu6886 from 1.2.846 to 1.2.852
Bumps nanoFramework.System.Buffers.Binary.BinaryPrimitives from 1.2.807 to 1.2.848
Bumps nanoFramework.System.Device.Model from 1.2.807 to 1.2.848
Bumps nanoFramework.System.Math from 1.5.102 to 1.5.112
Bumps nanoFramework.System.Numerics from 1.2.807 to 1.2.848
Bumps UnitsNet.nanoFramework.Temperature from 5.71.0 to 5.73.0
Bumps nanoFramework.Iot.Device.Buzzer from 1.2.846 to 1.2.852
Bumps nanoFramework.Iot.Device.Common.NumberHelper from 1.2.807 to 1.2.848
Bumps nanoFramework.Iot.Device.ePaper from 1.0.665 to 1.0.688
Bumps nanoFramework.Iot.Device.Rtc from 1.2.846 to 1.2.852
Bumps nanoFramework.System.Device.Pwm from 1.1.21 to 1.1.22
Bumps nanoFramework.System.Threading from 1.1.49 to 1.1.50
Bumps UnitsNet.nanoFramework.Frequency from 5.71.0 to 5.73.0
Bumps nanoFramework.Graphics from 1.2.39 to 1.2.42
Bumps nanoFramework.Iot.Device.Bmm150 from 1.2.822 to 1.2.852
Bumps nanoFramework.Iot.Device.Ip5306 from 1.2.846 to 1.2.852
Bumps nanoFramework.ResourceManager from 1.2.30 to 1.2.31
Bumps nanoFramework.Runtime.Native from 1.7.9 to 1.7.10
Bumps nanoFramework.System.Collections from 1.5.62 to 1.5.63
Bumps nanoFramework.System.IO.FileSystem from 1.1.81 to 1.1.83
Bumps nanoFramework.System.IO.Ports from 1.1.125 to 1.1.127
Bumps nanoFramework.System.IO.Streams from 1.1.89 to 1.1.91
Bumps nanoFramework.System.Text from 1.3.29 to 1.3.36
Bumps UnitsNet.nanoFramework.ElectricCurrent from 5.71.0 to 5.73.0
Bumps nanoFramework.System.Diagnostics.Stopwatch from 1.2.815 to 1.2.848
Bumps nanoFramework.Iot.Device.Axp192 from 1.2.846 to 1.2.852
Bumps nanoFramework.Iot.Device.Ft6xx6x from 1.2.814 to 1.2.855
Bumps UnitsNet.nanoFramework.ElectricPotential from 5.71.0 to 5.73.0
Bumps UnitsNet.nanoFramework.Power from 5.71.0 to 5.73.0
Bumps nanoFramework.Iot.Device.Chsc6540 from 1.1.822 to 1.1.852
Bumps nanoFramework.System.Device.Wifi from 1.5.124 to 1.5.128
Bumps nanoFramework.System.Net from 1.11.34 to 1.11.37

[version update]

⚠️ This is an automated update. ⚠️

Summary by CodeRabbit

  • Chores
    • Upgraded numerous dependency versions across projects to the latest releases. These updates improve overall stability, performance, and security while ensuring enhanced compatibility with underlying hardware features.

Bumps nanoFramework.CoreLibrary from 1.17.1 to 1.17.7</br>Bumps nanoFramework.Graphics.Core from 1.2.39 to 1.2.42</br>Bumps nanoFramework.Hardware.Esp32 from 1.6.31 to 1.6.33</br>Bumps nanoFramework.Hardware.Esp32.Rmt from 2.0.29 to 2.0.32</br>Bumps nanoFramework.Iot.Device.Button from 1.2.822 to 1.2.852</br>Bumps nanoFramework.Iot.Device.Ws28xx.Esp32 from 1.2.835 to 1.2.852</br>Bumps nanoFramework.Runtime.Events from 1.11.30 to 1.11.31</br>Bumps nanoFramework.System.Device.Adc from 1.1.22 to 1.1.23</br>Bumps nanoFramework.System.Device.Dac from 1.5.24 to 1.5.25</br>Bumps nanoFramework.System.Device.Gpio from 1.1.55 to 1.1.56</br>Bumps nanoFramework.System.Device.I2c from 1.1.27 to 1.1.28</br>Bumps nanoFramework.System.Device.Spi from 1.3.77 to 1.3.79</br>Bumps nanoFramework.Iot.Device.Mpu6886 from 1.2.846 to 1.2.852</br>Bumps nanoFramework.System.Buffers.Binary.BinaryPrimitives from 1.2.807 to 1.2.848</br>Bumps nanoFramework.System.Device.Model from 1.2.807 to 1.2.848</br>Bumps nanoFramework.System.Math from 1.5.102 to 1.5.112</br>Bumps nanoFramework.System.Numerics from 1.2.807 to 1.2.848</br>Bumps UnitsNet.nanoFramework.Temperature from 5.71.0 to 5.73.0</br>Bumps nanoFramework.Iot.Device.Buzzer from 1.2.846 to 1.2.852</br>Bumps nanoFramework.Iot.Device.Common.NumberHelper from 1.2.807 to 1.2.848</br>Bumps nanoFramework.Iot.Device.ePaper from 1.0.665 to 1.0.688</br>Bumps nanoFramework.Iot.Device.Rtc from 1.2.846 to 1.2.852</br>Bumps nanoFramework.System.Device.Pwm from 1.1.21 to 1.1.22</br>Bumps nanoFramework.System.Threading from 1.1.49 to 1.1.50</br>Bumps UnitsNet.nanoFramework.Frequency from 5.71.0 to 5.73.0</br>Bumps nanoFramework.Graphics from 1.2.39 to 1.2.42</br>Bumps nanoFramework.Iot.Device.Bmm150 from 1.2.822 to 1.2.852</br>Bumps nanoFramework.Iot.Device.Ip5306 from 1.2.846 to 1.2.852</br>Bumps nanoFramework.ResourceManager from 1.2.30 to 1.2.31</br>Bumps nanoFramework.Runtime.Native from 1.7.9 to 1.7.10</br>Bumps nanoFramework.System.Collections from 1.5.62 to 1.5.63</br>Bumps nanoFramework.System.IO.FileSystem from 1.1.81 to 1.1.83</br>Bumps nanoFramework.System.IO.Ports from 1.1.125 to 1.1.127</br>Bumps nanoFramework.System.IO.Streams from 1.1.89 to 1.1.91</br>Bumps nanoFramework.System.Text from 1.3.29 to 1.3.36</br>Bumps UnitsNet.nanoFramework.ElectricCurrent from 5.71.0 to 5.73.0</br>Bumps nanoFramework.System.Diagnostics.Stopwatch from 1.2.815 to 1.2.848</br>Bumps nanoFramework.Iot.Device.Axp192 from 1.2.846 to 1.2.852</br>Bumps nanoFramework.Iot.Device.Ft6xx6x from 1.2.814 to 1.2.855</br>Bumps UnitsNet.nanoFramework.ElectricPotential from 5.71.0 to 5.73.0</br>Bumps UnitsNet.nanoFramework.Power from 5.71.0 to 5.73.0</br>Bumps nanoFramework.Iot.Device.Chsc6540 from 1.1.822 to 1.1.852</br>Bumps nanoFramework.System.Device.Wifi from 1.5.124 to 1.5.128</br>Bumps nanoFramework.System.Net from 1.11.34 to 1.11.37</br>
[version update]

### ⚠️ This is an automated update. ⚠️
@coderabbitai
Copy link

coderabbitai bot commented Mar 12, 2025

Walkthrough

This pull request updates dependency versions across multiple projects. In various packages.lock.json files for test applications and nanoFramework projects, the versions for several libraries—such as nanoFramework.CoreLibrary, nanoFramework.Graphics(Core), nanoFramework.Hardware.Esp32 (and its Rmt variant), several nanoFramework.Iot.Device packages, nanoFramework.Runtime.Events, various nanoFramework.System components, and UnitsNet.nanoFramework libraries—have been incremented. Corresponding content hash values have also been revised to reflect the new versions. No new functionality or modifications to public APIs were introduced.

Changes

Files Change Summary
Tests/AtomLiteTestApp/..., Tests/AtomMatrixTestApp/..., Tests/FireTestApp/..., Tests/M5Core2TestApp/..., Tests/M5CoreTestApp/..., Tests/M5StickTestApp/..., Tests/ToughTestApp/... Upgraded dependency versions (e.g. nanoFramework.CoreLibrary from 1.17.1 to 1.17.7, nanoFramework.Graphics(Core) to 1.2.42, updated nanoFramework.Iot.Device and nanoFramework.System packages) with updated content hashes.
nanoFramework.AtomLite/..., nanoFramework.AtomMatrix/..., nanoFramework.CoreInk/..., nanoFramework.Fire/..., nanoFramework.M5Core/..., nanoFramework.M5Core2/..., nanoFramework.M5StickC/..., nanoFramework.M5StickCPlus/..., nanoFramework.Tough/... Systematic updates of dependency versions and content hashes across nanoFramework projects affecting libraries such as nanoFramework.CoreLibrary, nanoFramework.Graphics, nanoFramework.Hardware.Esp32, various nanoFramework.Iot.Device packages, nanoFramework.Runtime, and UnitsNet.nanoFramework libraries.

Possibly related PRs

Suggested labels

CI: Publish Release


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2000e87 and 2196054.

⛔ Files ignored due to path filters (41)
  • Tests/AtomLiteTestApp/AtomLiteTestApp.nfproj is excluded by none and included by none
  • Tests/AtomLiteTestApp/packages.config is excluded by none and included by none
  • Tests/AtomMatrixTestApp/AtomMatrixTestApp.nfproj is excluded by none and included by none
  • Tests/AtomMatrixTestApp/packages.config is excluded by none and included by none
  • Tests/FireTestApp/FireTestApp.nfproj is excluded by none and included by none
  • Tests/FireTestApp/packages.config is excluded by none and included by none
  • Tests/M5Core2TestApp/M5Core2TestApp.nfproj is excluded by none and included by none
  • Tests/M5Core2TestApp/packages.config is excluded by none and included by none
  • Tests/M5CoreTestApp/M5CoreTestApp.nfproj is excluded by none and included by none
  • Tests/M5CoreTestApp/packages.config is excluded by none and included by none
  • Tests/M5StickTestApp/M5StickTestApp.nfproj is excluded by none and included by none
  • Tests/M5StickTestApp/packages.config is excluded by none and included by none
  • Tests/ToughTestApp/ToughTestApp.nfproj is excluded by none and included by none
  • Tests/ToughTestApp/packages.config is excluded by none and included by none
  • nanoFramework.AtomLite.nuspec is excluded by none and included by none
  • nanoFramework.AtomLite/nanoFramework.AtomLite.nfproj is excluded by none and included by none
  • nanoFramework.AtomLite/packages.config is excluded by none and included by none
  • nanoFramework.AtomMatrix.nuspec is excluded by none and included by none
  • nanoFramework.AtomMatrix/nanoFramework.AtomMatrix.nfproj is excluded by none and included by none
  • nanoFramework.AtomMatrix/packages.config is excluded by none and included by none
  • nanoFramework.CoreInk.nuspec is excluded by none and included by none
  • nanoFramework.CoreInk/nanoFramework.CoreInk.nfproj is excluded by none and included by none
  • nanoFramework.CoreInk/packages.config is excluded by none and included by none
  • nanoFramework.Fire.nuspec is excluded by none and included by none
  • nanoFramework.Fire/nanoFramework.Fire.nfproj is excluded by none and included by none
  • nanoFramework.Fire/packages.config is excluded by none and included by none
  • nanoFramework.M5Core.nuspec is excluded by none and included by none
  • nanoFramework.M5Core/nanoFramework.M5Core.nfproj is excluded by none and included by none
  • nanoFramework.M5Core/packages.config is excluded by none and included by none
  • nanoFramework.M5Core2.nuspec is excluded by none and included by none
  • nanoFramework.M5Core2/nanoFramework.M5Core2.nfproj is excluded by none and included by none
  • nanoFramework.M5Core2/packages.config is excluded by none and included by none
  • nanoFramework.M5StickC.nuspec is excluded by none and included by none
  • nanoFramework.M5StickC/nanoFramework.M5StickC.nfproj is excluded by none and included by none
  • nanoFramework.M5StickC/packages.config is excluded by none and included by none
  • nanoFramework.M5StickCPlus.nuspec is excluded by none and included by none
  • nanoFramework.M5StickCPlus/nanoFramework.M5StickCPlus.nfproj is excluded by none and included by none
  • nanoFramework.M5StickCPlus/packages.config is excluded by none and included by none
  • nanoFramework.Tough.nuspec is excluded by none and included by none
  • nanoFramework.Tough/nanoFramework.Tough.nfproj is excluded by none and included by none
  • nanoFramework.Tough/packages.config is excluded by none and included by none
📒 Files selected for processing (16)
  • Tests/AtomLiteTestApp/packages.lock.json (1 hunks)
  • Tests/AtomMatrixTestApp/packages.lock.json (1 hunks)
  • Tests/FireTestApp/packages.lock.json (1 hunks)
  • Tests/M5Core2TestApp/packages.lock.json (1 hunks)
  • Tests/M5CoreTestApp/packages.lock.json (1 hunks)
  • Tests/M5StickTestApp/packages.lock.json (1 hunks)
  • Tests/ToughTestApp/packages.lock.json (1 hunks)
  • nanoFramework.AtomLite/packages.lock.json (1 hunks)
  • nanoFramework.AtomMatrix/packages.lock.json (2 hunks)
  • nanoFramework.CoreInk/packages.lock.json (2 hunks)
  • nanoFramework.Fire/packages.lock.json (2 hunks)
  • nanoFramework.M5Core/packages.lock.json (2 hunks)
  • nanoFramework.M5Core2/packages.lock.json (2 hunks)
  • nanoFramework.M5StickC/packages.lock.json (2 hunks)
  • nanoFramework.M5StickCPlus/packages.lock.json (2 hunks)
  • nanoFramework.Tough/packages.lock.json (2 hunks)
🔇 Additional comments (38)
nanoFramework.AtomLite/packages.lock.json (1)

7-75: Dependency Version Updates in AtomLite Lock File

All dependency entries—such as for nanoFramework.CoreLibrary, nanoFramework.Graphics.Core, nanoFramework.Hardware.Esp32, nanoFramework.Hardware.Esp32.Rmt, nanoFramework.Iot.Device.Button, nanoFramework.Iot.Device.Ws28xx.Esp32, nanoFramework.Runtime.Events, nanoFramework.System.Device.Adc, nanoFramework.System.Device.Dac, nanoFramework.System.Device.Gpio, nanoFramework.System.Device.I2c, and nanoFramework.System.Device.Spi—have been updated to the new versions and corresponding content hashes as specified in the PR objectives. These automated updates appear consistent and correct.

nanoFramework.M5StickCPlus/packages.lock.json (1)

7-81: Confirmed Dependency Updates in M5StickCPlus Lock File

This lock file reflects updated dependency versions for components including nanoFramework.CoreLibrary, nanoFramework.Graphics, nanoFramework.Hardware.Esp32, nanoFramework.Hardware.Esp32.Rmt, nanoFramework.Iot.Device.Axp192, nanoFramework.Iot.Device.Button, nanoFramework.Iot.Device.Buzzer, nanoFramework.Iot.Device.Common.NumberHelper, nanoFramework.Iot.Device.Mpu6886, and nanoFramework.Iot.Device.Rtc. The new version strings and contentHash values are in full alignment with the intended NuGet updates.

nanoFramework.Tough/packages.lock.json (1)

7-65: Dependency Version Updates in Tough Project Lock File

The nanoFramework.Tough/packages.lock.json file shows systematic updates for multiple dependencies. Updated entries include nanoFramework.CoreLibrary, nanoFramework.Graphics, nanoFramework.Graphics.Core, nanoFramework.Hardware.Esp32, nanoFramework.Iot.Device.Axp192, nanoFramework.Iot.Device.Chsc6540, nanoFramework.Iot.Device.Common.NumberHelper, nanoFramework.Iot.Device.Rtc, nanoFramework.ResourceManager, nanoFramework.Runtime.Events, nanoFramework.Runtime.Native, nanoFramework.System.Collections, and several device-specific libraries. All version and contentHash modifications are consistent with the overall dependency upgrade plan.

nanoFramework.M5Core/packages.lock.json (1)

7-130: M5Core Project Dependency Updates

The dependencies in this lock file have been updated as expected. Changes cover updates for nanoFramework.CoreLibrary, nanoFramework.Graphics, nanoFramework.Hardware.Esp32, nanoFramework.Iot.Device.Bmm150, nanoFramework.Iot.Device.Button, nanoFramework.Iot.Device.Buzzer, nanoFramework.Iot.Device.Ip5306, nanoFramework.Iot.Device.Mpu6886, nanoFramework.ResourceManager, nanoFramework.Runtime.Events, nanoFramework.Runtime.Native, and various System libraries. The new version numbers and contentHash values correctly reflect the PR’s upgrade objectives.

nanoFramework.AtomMatrix/packages.lock.json (1)

7-51: AtomMatrix Project Dependency Updates Confirmed

This file shows the updated dependency versions and contentHash values for critical components including nanoFramework.CoreLibrary, nanoFramework.Graphics.Core, nanoFramework.Hardware.Esp32, nanoFramework.Hardware.Esp32.Rmt, nanoFramework.Iot.Device.Button, nanoFramework.Iot.Device.Mpu6886, nanoFramework.Iot.Device.Ws28xx.Esp32, and nanoFramework.Runtime.Events. The updates are in line with the coordinated upgrade efforts and appear correct.

nanoFramework.CoreInk/packages.lock.json (1)

1-127: Overall Dependency Update Consistency
All dependency entries in this file have been updated uniformly to the new versions (for example, nanoFramework.CoreLibrary is now 1.17.7, nanoFramework.Graphics.Core is 1.2.42, etc.). The “requested”, “resolved”, and “contentHash” fields are all consistent with these updates.

nanoFramework.M5StickC/packages.lock.json (1)

1-64: Uniform Version Upgrade Verification
This file shows a systematic upgrade for each dependency (for example, nanoFramework.CoreLibrary to 1.17.7, nanoFramework.Graphics to 1.2.42, nanoFramework.Hardware.Esp32.Rmt to 2.0.32, and so on). The changes in the “requested,” “resolved,” and “contentHash” fields are consistent throughout.

nanoFramework.M5Core2/packages.lock.json (1)

1-223: Comprehensive Dependency Revision Check
Every dependency in the file is updated to its new version. This includes updates to both nanoFramework.Graphics and nanoFramework.Graphics.Core as well as numerous nanoFramework.Iot.Device and nanoFramework.System.* packages. The updated “requested” and “resolved” version numbers and new content hashes indicate that the upgrade has been applied uniformly.

Tests/AtomMatrixTestApp/packages.lock.json (1)

1-181: Overall Dependency Version Updates Verified
All dependency version updates—including those for nanoFramework.CoreLibrary, nanoFramework.Graphics.Core, nanoFramework.Hardware.Esp32.Rmt, and others—have been updated consistently. The revised content hash values further confirm that the updates are correctly applied.

Tests/AtomLiteTestApp/packages.lock.json (1)

1-49: Consistent Dependency Updates
This file’s dependency entries (e.g. nanoFramework.CoreLibrary, nanoFramework.Graphics.Core, nanoFramework.Hardware.Esp32.Rmt, etc.) have all been updated with the new version and corresponding content hash. The modifications are consistent with the updates seen in other parts of the project.

Tests/FireTestApp/packages.lock.json (1)

7-9: [Approve] Consistent dependency updates in FireTestApp lock file.
All the dependency entries—from nanoFramework.CoreLibrary up to UnitsNet.nanoFramework.Temperature—have been updated to the new versions (e.g. 1.17.7; 1.2.42; 2.0.32; 1.2.852; etc.) with matching new content hash values. These changes are entirely in line with the PR objectives.

Also applies to: 13-15, 19-21, 25-27, 31-33, 37-39, 43-45, 49-51, 55-57, 61-63, 67-69, 73-75, 79-81, 85-87, 91-93, 97-99, 103-105, 109-111, 115-117, 121-123, 127-129, 133-135, 161-165, 167-171, 173-177, 179-183

Tests/M5CoreTestApp/packages.lock.json (1)

7-9: [Approve] Systematic updates in M5CoreTestApp lock file.
Every dependency entry—from nanoFramework.CoreLibrary to UnitsNet.nanoFramework.Temperature—has been incremented as expected. The new version constraints and content hashes appear correct and consistent with the overall dependency upgrade strategy.

Also applies to: 13-15, 19-21, 25-27, 31-33, 37-39, 43-45, 49-51, 55-57, 61-63, 67-69, 73-75, 79-81, 85-87, 91-93, 97-99, 103-105, 109-111, 115-117, 121-123, 127-129, 131-135, 137-141

Tests/M5Core2TestApp/packages.lock.json (1)

7-9: [Approve] Dependency updates in M5Core2TestApp lock file.
The lock file shows the following updated dependencies: the core libraries (e.g. nanoFramework.CoreLibrary and nanoFramework.Graphics) as well as various IOT device and system components (including the update for nanoFramework.Hardware.Esp32 to 1.6.33 and nanoFramework.Iot.Device.Axp192 to 1.2.852). The updated “requested” and “resolved” values and new content hash values are all in agreement with the PR objectives.

Also applies to: 13-15, 19-21, 25-27, 31-33, 37-39, 43-45, 49-51, 55-57, 61-63, 67-69, 73-75, 79-81, 85-87, 91-93

nanoFramework.Fire/packages.lock.json (1)

7-9: [Approve] Updates in nanoFramework.Fire lock file are correct.
The dependency versions for key packages such as nanoFramework.CoreLibrary, nanoFramework.Graphics (plus its Core subcomponent), as well as updates for nanoFramework.Hardware.Esp32 (and its Rmt variant) and several IOT device packages have been updated properly. The new values (version numbers and content hashes) are in line with the incremental upgrade strategy.

Also applies to: 13-15, 19-21, 25-27, 31-33, 37-39, 43-45, 49-51, 55-57, 61-63, 67-69, 73-75, 79-81, 85-87

Tests/M5StickTestApp/packages.lock.json (1)

7-9: [Approve] Consistent dependency updates in M5StickTestApp lock file.
All dependency entries in this lock file (from nanoFramework.CoreLibrary to UnitsNet.nanoFramework.Temperature) have been upgraded to the new versions specified in the PR (for instance, nanoFramework.CoreLibrary 1.17.7, nanoFramework.Graphics 1.2.42, etc.). The updated “requested”, “resolved” and “contentHash” fields are correctly refreshed.

Also applies to: 13-15, 19-21, 25-27, 31-33, 37-39, 43-45, 49-51, 55-57, 61-63, 67-69, 73-75, 77-81, 85-87, 91-93, 97-99, 103-105, 109-111, 115-117, 121-123, 125-129, 131-135, 137-141

Tests/ToughTestApp/packages.lock.json (23)

7-9: Dependency Version Update: nanoFramework.CoreLibrary

The dependency version is updated to "1.17.7" along with the corresponding content hash. Ensure that all project files referencing this package are updated accordingly.


13-15: Dependency Version Update: nanoFramework.Graphics

The version is now "1.2.42" and the content hash has been updated. This update is consistent with similar changes in other modules.


19-21: Dependency Version Update: nanoFramework.Graphics.Core

The update to version "1.2.42" and its associated content hash appear correct. Please verify that the graphics core functionality is fully compatible.


25-27: Dependency Version Update: nanoFramework.Iot.Device.Axp192

The package version has been bumped to "1.2.852" with an updated contentHash. This aligns with the broader update of IoT device components.


31-33: Dependency Version Update: nanoFramework.Iot.Device.Chsc6540

The dependency is now at version "1.1.852" with its new content hash. Ensure that any hardware integrations using this package are tested after the upgrade.


37-39: Dependency Version Update: nanoFramework.ResourceManager

Updated to "1.2.31" with the revised content hash. This routine update should be compatible with existing resource management calls.


43-45: Dependency Version Update: nanoFramework.Runtime.Events

The version increment to "1.11.31" and the matching content hash indicate a proper update. It is advisable to run integration tests around event handling to confirm correct behavior.


49-51: Dependency Version Update: nanoFramework.Runtime.Native

Version updated to "1.7.10" with the corresponding content hash. This change should be cross-checked for any native interop adjustments.


55-57: Dependency Version Update: nanoFramework.System.Collections

The dependency is now at "1.5.63" with an updated content hash. Please verify that the collection APIs behave as expected.


61-63: Dependency Version Update: nanoFramework.System.Device.Adc

The ADC package has been updated to version "1.1.23". The new content hash confirms this change; ensure that analog-to-digital conversions are validated on target hardware.


67-69: Dependency Version Update: nanoFramework.System.Device.Gpio

The GPIO dependency now reflects version "1.1.56" with an updated content hash. It is recommended to recheck pin configuration and behavior on hardware.


73-75: Dependency Version Update: nanoFramework.System.Device.I2c

Version bumped to "1.1.28" along with the revised content hash. Confirm that I²C communications remain stable after the update.


79-81: Dependency Version Update: nanoFramework.System.Device.Wifi

The update to "1.5.128" and the accompanying content hash appear correct. Please ensure that WiFi connectivity and related tests pass successfully.


85-87: Dependency Version Update: nanoFramework.System.IO.FileSystem

Updated version "1.1.83" with a matching content hash. This routine update should be transparent, but verifying file system operations is still recommended.


91-93: Dependency Version Update: nanoFramework.System.IO.Ports

The package now reflects version "1.1.127" along with the associated content hash. Serial port communication should be tested to ensure no regressions.


97-99: Dependency Version Update: nanoFramework.System.IO.Streams

The Streams dependency has been updated to "1.1.91" with the new content hash. Verify that any stream I/O operations continue to function as expected.


103-105: Dependency Version Update: nanoFramework.System.Net

The dependency is now at "1.11.37" and the related content hash has been updated. It is advisable to test network connectivity after this update.


109-111: Dependency Version Update: nanoFramework.System.Text

Version updated to "1.3.36" with its revised content hash. Confirm that text processing and encoding/decoding functions are unaffected.


115-117: Dependency Version Update: nanoFramework.System.Threading

Updated to "1.1.50" along with an updated content hash. Pay close attention to any concurrency or timing issues during system tests.


121-123: Dependency Version Update: UnitsNet.nanoFramework.ElectricCurrent

The update to "5.73.0" with the new content hash puts this dependency in line with other UnitsNet components. Verification in physical measurements is recommended.


127-129: Dependency Version Update: UnitsNet.nanoFramework.ElectricPotential

Version "5.73.0" is now in effect and the content hash confirms the change. Ensure that electrical potential calculations remain accurate.


133-135: Dependency Version Update: UnitsNet.nanoFramework.Power

The dependency has been bumped to "5.73.0". The updated content hash is as expected; please confirm that power-related data processing remains correct.


139-141: Dependency Version Update: UnitsNet.nanoFramework.Temperature

Updated to version "5.73.0" with the corresponding content hash. Make sure that temperature sensor integrations and computations are validated.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@sonarqubecloud
Copy link

@nfbot nfbot merged commit 6d82d21 into main Mar 12, 2025
7 checks passed
@nfbot nfbot deleted the nfbot/update-dependencies/73537e3e-89f0-4cac-aa63-c4f51f7793d0 branch March 12, 2025 07:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants