Update 14 NuGet dependencies #333
Conversation
Bumps nanoFramework.Iot.Device.Button from 1.2.560 to 1.2.570</br>Bumps nanoFramework.Iot.Device.Ws28xx.Esp32 from 1.2.548 to 1.2.570</br>Bumps nanoFramework.Iot.Device.Mpu6886 from 1.2.536 to 1.2.573</br>Bumps UnitsNet.nanoFramework.Temperature from 5.50.0 to 5.52.0</br>Bumps nanoFramework.Iot.Device.Bmm150 from 1.2.560 to 1.2.570</br>Bumps nanoFramework.Iot.Device.Buzzer from 1.2.536 to 1.2.573</br>Bumps nanoFramework.Iot.Device.Ip5306 from 1.2.536 to 1.2.573</br>Bumps UnitsNet.nanoFramework.ElectricCurrent from 5.50.0 to 5.52.0</br>Bumps UnitsNet.nanoFramework.Frequency from 5.50.0 to 5.52.0</br>Bumps nanoFramework.Iot.Device.Axp192 from 1.2.560 to 1.2.573</br>Bumps nanoFramework.Iot.Device.Rtc from 1.2.536 to 1.2.573</br>Bumps UnitsNet.nanoFramework.ElectricPotential from 5.50.0 to 5.52.0</br>Bumps UnitsNet.nanoFramework.Power from 5.50.0 to 5.52.0</br>Bumps nanoFramework.Iot.Device.Chsc6540 from 1.1.548 to 1.1.570</br> [version update] ###⚠️ This is an automated update.⚠️
WalkthroughThe recent changes focused on updating package dependencies across several test applications within the repository. The updates mainly involved incrementing version numbers and corresponding content hashes for various nanoFramework and UnitsNet packages to their latest versions. These changes ensure consistency and potential performance improvements or bug fixes for the testing environments. Changes
Sequence DiagramsOmitted in this case as the changes are incremental updates to package versions and do not alter the control flow or introduce new features. Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
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 as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
|
nfbot
deleted the
nfbot/update-dependencies/63cebc1f-3b07-4282-bcc0-27f2b8a598f5
branch
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files ignored due to path filters (38)
Tests/AtomLiteTestApp/AtomLiteTestApp.nfprojis excluded by none and included by noneTests/AtomLiteTestApp/packages.configis excluded by none and included by noneTests/AtomMatrixTestApp/AtomMatrixTestApp.nfprojis excluded by none and included by noneTests/AtomMatrixTestApp/packages.configis excluded by none and included by noneTests/FireTestApp/FireTestApp.nfprojis excluded by none and included by noneTests/FireTestApp/packages.configis excluded by none and included by noneTests/M5Core2TestApp/M5Core2TestApp.nfprojis excluded by none and included by noneTests/M5Core2TestApp/packages.configis excluded by none and included by noneTests/M5CoreTestApp/M5CoreTestApp.nfprojis excluded by none and included by noneTests/M5CoreTestApp/packages.configis excluded by none and included by noneTests/M5StickTestApp/M5StickTestApp.nfprojis excluded by none and included by noneTests/M5StickTestApp/packages.configis excluded by none and included by noneTests/ToughTestApp/ToughTestApp.nfprojis excluded by none and included by noneTests/ToughTestApp/packages.configis excluded by none and included by nonenanoFramework.AtomLite.nuspecis excluded by none and included by nonenanoFramework.AtomLite/nanoFramework.AtomLite.nfprojis excluded by none and included by nonenanoFramework.AtomLite/packages.configis excluded by none and included by nonenanoFramework.AtomMatrix.nuspecis excluded by none and included by nonenanoFramework.AtomMatrix/nanoFramework.AtomMatrix.nfprojis excluded by none and included by nonenanoFramework.AtomMatrix/packages.configis excluded by none and included by nonenanoFramework.Fire.nuspecis excluded by none and included by nonenanoFramework.Fire/nanoFramework.Fire.nfprojis excluded by none and included by nonenanoFramework.Fire/packages.configis excluded by none and included by nonenanoFramework.M5Core.nuspecis excluded by none and included by nonenanoFramework.M5Core/nanoFramework.M5Core.nfprojis excluded by none and included by nonenanoFramework.M5Core/packages.configis excluded by none and included by nonenanoFramework.M5Core2.nuspecis excluded by none and included by nonenanoFramework.M5Core2/nanoFramework.M5Core2.nfprojis excluded by none and included by nonenanoFramework.M5Core2/packages.configis excluded by none and included by nonenanoFramework.M5StickC.nuspecis excluded by none and included by nonenanoFramework.M5StickC/nanoFramework.M5StickC.nfprojis excluded by none and included by nonenanoFramework.M5StickC/packages.configis excluded by none and included by nonenanoFramework.M5StickCPlus.nuspecis excluded by none and included by nonenanoFramework.M5StickCPlus/nanoFramework.M5StickCPlus.nfprojis excluded by none and included by nonenanoFramework.M5StickCPlus/packages.configis excluded by none and included by nonenanoFramework.Tough.nuspecis excluded by none and included by nonenanoFramework.Tough/nanoFramework.Tough.nfprojis excluded by none and included by nonenanoFramework.Tough/packages.configis excluded by none and included by none
Files selected for processing (15)
- Tests/AtomLiteTestApp/packages.lock.json (1 hunks)
- Tests/AtomMatrixTestApp/packages.lock.json (1 hunks)
- Tests/FireTestApp/packages.lock.json (2 hunks)
- Tests/M5Core2TestApp/packages.lock.json (3 hunks)
- Tests/M5CoreTestApp/packages.lock.json (2 hunks)
- Tests/M5StickTestApp/packages.lock.json (3 hunks)
- Tests/ToughTestApp/packages.lock.json (2 hunks)
- nanoFramework.AtomLite/packages.lock.json (1 hunks)
- nanoFramework.AtomMatrix/packages.lock.json (2 hunks)
- nanoFramework.Fire/packages.lock.json (2 hunks)
- nanoFramework.M5Core/packages.lock.json (2 hunks)
- nanoFramework.M5Core2/packages.lock.json (3 hunks)
- nanoFramework.M5StickC/packages.lock.json (3 hunks)
- nanoFramework.M5StickCPlus/packages.lock.json (3 hunks)
- nanoFramework.Tough/packages.lock.json (3 hunks)
Files skipped from review due to trivial changes (4)
- Tests/AtomMatrixTestApp/packages.lock.json
- Tests/M5CoreTestApp/packages.lock.json
- nanoFramework.AtomLite/packages.lock.json
- nanoFramework.M5Core2/packages.lock.json
Additional comments not posted (61)
Tests/AtomLiteTestApp/packages.lock.json (2)
25-27: The update tonanoFramework.Iot.Device.Buttonfrom version1.2.560to1.2.570is correctly reflected in therequested,resolved, andcontentHashfields.
31-33: The update tonanoFramework.Iot.Device.Ws28xx.Esp32from version1.2.548to1.2.570is correctly reflected in therequested,resolved, andcontentHashfields.nanoFramework.AtomMatrix/packages.lock.json (4)
31-33: The update tonanoFramework.Iot.Device.Buttonfrom version1.2.560to1.2.570is correctly reflected in therequested,resolved, andcontentHashfields.
37-39: The update tonanoFramework.Iot.Device.Mpu6886from version1.2.536to1.2.573is correctly reflected in therequested,resolved, andcontentHashfields.
43-45: The update tonanoFramework.Iot.Device.Ws28xx.Esp32from version1.2.548to1.2.570is correctly reflected in therequested,resolved, andcontentHashfields.
115-117: The update toUnitsNet.nanoFramework.Temperaturefrom version5.50.0to5.52.0is correctly reflected in therequested,resolved, andcontentHashfields.Tests/ToughTestApp/packages.lock.json (3)
25-27: The update tonanoFramework.Iot.Device.Axp192from version1.2.560to1.2.573is correctly reflected in therequested,resolved, andcontentHashfields.
31-33: The update tonanoFramework.Iot.Device.Chsc6540from version1.1.548to1.1.570is correctly reflected in therequested,resolved, andcontentHashfields.
127-129: Updates to theUnitsNet.nanoFrameworkpackages (ElectricCurrent,ElectricPotential,Power,Temperature) from version5.50.0to5.52.0are correctly reflected in therequested,resolved, andcontentHashfields.Also applies to: 133-135, 139-141, 145-147
Tests/M5StickTestApp/packages.lock.json (2)
31-33: Updates to thenanoFramework.Iot.Devicepackages (Axp192,Button,Mpu6886,Rtc) are correctly reflected in therequested,resolved, andcontentHashfields.Also applies to: 37-39, 49-51, 55-57
127-129: Updates to theUnitsNet.nanoFrameworkpackages (ElectricCurrent,ElectricPotential,Power,Temperature) from version5.50.0to5.52.0are correctly reflected in therequested,resolved, andcontentHashfields.Also applies to: 133-135, 139-141, 145-147
nanoFramework.M5StickC/packages.lock.json (5)
31-33: Update confirmed fornanoFramework.Iot.Device.Axp192to version1.2.573. Ensure compatibility with this version in the related application code.
37-39: Update confirmed fornanoFramework.Iot.Device.Buttonto version1.2.570. Verify that all button-related functionalities are tested with this new version.
55-57: Update confirmed fornanoFramework.Iot.Device.Rtcto version1.2.573. Confirm that all RTC functionalities behave as expected after this update.
133-135: Updates confirmed forUnitsNet.nanoFrameworkpackages to version5.52.0. Ensure that all dependent calculations and functionalities are re-validated to accommodate the new units definitions.Also applies to: 139-141, 145-147, 151-153
49-51: Update confirmed fornanoFramework.Iot.Device.Mpu6886to version1.2.573. It's crucial to check if the new sensor readings align with expected values.nanoFramework.Tough/packages.lock.json (4)
31-33: Update confirmed fornanoFramework.Iot.Device.Axp192to version1.2.573. Ensure compatibility with this version in the related application code.
49-51: Update confirmed fornanoFramework.Iot.Device.Rtcto version1.2.573. Confirm that all RTC functionalities behave as expected after this update.
151-153: Updates confirmed forUnitsNet.nanoFrameworkpackages to version5.52.0. Ensure that all dependent calculations and functionalities are re-validated to accommodate the new units definitions.Also applies to: 157-159, 163-165, 169-171
Verification successful
The search results indicate that the
UnitsNet.nanoFrameworkpackage is used in multiple project and test files across the codebase. To ensure all dependent calculations and functionalities are re-validated, we need to verify that the relevant tests cover the new definitions provided by version5.52.0.To proceed, we should search for references to the specific UnitsNet components (such as
ElectricCurrent,ElectricPotential,Power,Temperature, andFrequency) in the test files to confirm that tests exist and potentially validate the updated functionalities.
The search results confirm that references to the updated
UnitsNet.nanoFrameworkcomponents (ElectricCurrent, ElectricPotential, Power, Temperature, and Frequency) are present in various test projects. This indicates that the tests are likely covering the new definitions provided by version5.52.0.
- ElectricCurrent is referenced in multiple test project files.
- ElectricPotential is referenced in multiple test project files.
- Power is referenced in multiple test project files.
- Temperature is referenced in multiple test project files.
- Frequency is referenced in the
FireTestApptest project.Given this evidence, it is reasonable to conclude that the tests are in place and should cover the updated functionalities of the
UnitsNet.nanoFrameworkpackage.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify all functionalities dependent on updated UnitsNet packages. # Test: Search for usage of UnitsNet packages and ensure tests cover new definitions. rg --type json 'UnitsNet.nanoFramework' tests/Length of output: 93
Script:
#!/bin/bash # Search for usage of UnitsNet.nanoFramework across the entire codebase rg 'UnitsNet.nanoFramework'Length of output: 15850
Script:
#!/bin/bash # Search for references to UnitsNet components in test files to ensure tests cover new definitions # Define the components to search for components=("ElectricCurrent" "ElectricPotential" "Power" "Temperature" "Frequency") # Loop through each component and search in test files for component in "${components[@]}"; do echo "Searching for $component in test files..." rg "$component" Tests/ doneLength of output: 10582
37-39: Update confirmed fornanoFramework.Iot.Device.Chsc6540to version1.1.570. Verify compatibility and functionality with this new version.nanoFramework.M5StickCPlus/packages.lock.json (6)
31-33: Update confirmed fornanoFramework.Iot.Device.Axp192to version1.2.573. Ensure compatibility with this version in the related application code.
55-57: Update confirmed fornanoFramework.Iot.Device.Mpu6886to version1.2.573. It's crucial to check if the new sensor readings align with expected values.
61-63: Update confirmed fornanoFramework.Iot.Device.Rtcto version1.2.573. Confirm that all RTC functionalities behave as expected after this update.
145-147: Updates confirmed forUnitsNet.nanoFrameworkpackages to version5.52.0. Ensure that all dependent calculations and functionalities are re-validated to accommodate the new units definitions.Also applies to: 151-153, 157-159, 163-165, 169-171
37-39: Update confirmed fornanoFramework.Iot.Device.Buttonto version1.2.570. Verify that all button-related functionalities are tested with this new version.
43-45: Update confirmed fornanoFramework.Iot.Device.Buzzerto version1.2.573. Check for any required adjustments in buzzer control logic or tests due to this update.Tests/FireTestApp/packages.lock.json (9)
31-33: UpdatednanoFramework.Iot.Device.Bmm150to version 1.2.570 with a new content hash. Please ensure that the new version is compatible with the application requirements.
43-45: UpdatednanoFramework.Iot.Device.Buzzerto version 1.2.573 with a new content hash. Confirm that all buzzer functionalities are tested with the new library version.
49-51: UpdatednanoFramework.Iot.Device.Ip5306to version 1.2.573 with a new content hash. It's important to ensure that the device's power management interactions remain stable after this update.
55-57: UpdatednanoFramework.Iot.Device.Mpu6886to version 1.2.573 with a new content hash. Please verify that the motion processing unit functions correctly with the updated library.
61-63: UpdatednanoFramework.Iot.Device.Ws28xx.Esp32to version 1.2.570 with a new content hash. Check for any potential issues with LED control functionalities due to this update.
175-177: UpdatedUnitsNet.nanoFramework.ElectricCurrentto version 5.52.0 with a new content hash. Ensure that electrical current calculations are accurate with the new version.
181-183: UpdatedUnitsNet.nanoFramework.Frequencyto version 5.52.0 with a new content hash. Confirm that all frequency-related calculations and functionalities are correct.
187-189: UpdatedUnitsNet.nanoFramework.Temperatureto version 5.52.0 with a new content hash. Verify temperature measurements and related functionalities for accuracy and consistency.
37-39: UpdatednanoFramework.Iot.Device.Buttonto version 1.2.570 with a new content hash. Verify that this update does not introduce breaking changes in button-related functionalities.nanoFramework.M5Core/packages.lock.json (8)
25-27: Updated dependencynanoFramework.Iot.Device.Bmm150to version 1.2.570 with a new content hash.
31-33: Updated dependencynanoFramework.Iot.Device.Buttonto version 1.2.570 with a new content hash.
37-39: Updated dependencynanoFramework.Iot.Device.Buzzerto version 1.2.573 with a new content hash.
43-45: Updated dependencynanoFramework.Iot.Device.Ip5306to version 1.2.573 with a new content hash.
49-51: Updated dependencynanoFramework.Iot.Device.Mpu6886to version 1.2.573 with a new content hash.
181-183: Updated dependencyUnitsNet.nanoFramework.ElectricCurrentto version 5.52.0 with a new content hash.
187-189: Updated dependencyUnitsNet.nanoFramework.Frequencyto version 5.52.0 with a new content hash.
193-195: Updated dependencyUnitsNet.nanoFramework.Temperatureto version 5.52.0 with a new content hash.nanoFramework.Fire/packages.lock.json (9)
37-39: Updated dependencynanoFramework.Iot.Device.Bmm150to version 1.2.570 with a new content hash.
43-45: Updated dependencynanoFramework.Iot.Device.Buttonto version 1.2.570 with a new content hash.
49-51: Updated dependencynanoFramework.Iot.Device.Buzzerto version 1.2.573 with a new content hash.
55-57: Updated dependencynanoFramework.Iot.Device.Ip5306to version 1.2.573 with a new content hash.
61-63: Updated dependencynanoFramework.Iot.Device.Mpu6886to version 1.2.573 with a new content hash.
67-69: Updated dependencynanoFramework.Iot.Device.Ws28xx.Esp32to version 1.2.570 with a new content hash.
193-195: Updated dependencyUnitsNet.nanoFramework.ElectricCurrentto version 5.52.0 with a new content hash.
199-201: Updated dependencyUnitsNet.nanoFramework.Frequencyto version 5.52.0 with a new content hash.
205-207: Updated dependencyUnitsNet.nanoFramework.Temperatureto version 5.52.0 with a new content hash.Tests/M5Core2TestApp/packages.lock.json (9)
25-27: UpdatednanoFramework.Iot.Device.Axp192to version1.2.573with a new content hash.This update ensures compatibility with the latest device improvements and bug fixes.
31-33: UpdatednanoFramework.Iot.Device.Bmm150to version1.2.570with a new content hash.Ensure that the application's usage of Bmm150's features are compatible with the new version to prevent runtime issues.
37-39: UpdatednanoFramework.Iot.Device.Buttonto version1.2.570with a new content hash.Check if there are any breaking changes in the new version that might affect button handling in the application.
49-51: UpdatednanoFramework.Iot.Device.Mpu6886to version1.2.573with a new content hash.This update is crucial for ensuring the latest motion processing capabilities are available in the application.
55-57: UpdatednanoFramework.Iot.Device.Rtcto version1.2.573with a new content hash.Ensure that the real-time clock handling in the application is tested with this new version to avoid timing issues.
199-201: UpdatedUnitsNet.nanoFramework.ElectricCurrentto version5.52.0with a new content hash.This update may include new features or bug fixes related to electric current measurements. Verify that these changes integrate well with your application's current measurement functionalities.
205-207: UpdatedUnitsNet.nanoFramework.ElectricPotentialto version5.52.0with a new content hash.As with other UnitsNet updates, ensure the application's handling of electric potential calculations is compatible with this new version.
211-213: UpdatedUnitsNet.nanoFramework.Powerto version5.52.0with a new content hash.This update might affect how power calculations are handled in the application. It's recommended to perform integration testing to ensure no disruptions.
217-219: UpdatedUnitsNet.nanoFramework.Temperatureto version5.52.0with a new content hash.Check that all temperature-related functionalities in the application are still performing accurately with this updated package.
Bumps nanoFramework.Iot.Device.Button from 1.2.560 to 1.2.570
Bumps nanoFramework.Iot.Device.Ws28xx.Esp32 from 1.2.548 to 1.2.570
Bumps nanoFramework.Iot.Device.Mpu6886 from 1.2.536 to 1.2.573
Bumps UnitsNet.nanoFramework.Temperature from 5.50.0 to 5.52.0
Bumps nanoFramework.Iot.Device.Bmm150 from 1.2.560 to 1.2.570
Bumps nanoFramework.Iot.Device.Buzzer from 1.2.536 to 1.2.573
Bumps nanoFramework.Iot.Device.Ip5306 from 1.2.536 to 1.2.573
Bumps UnitsNet.nanoFramework.ElectricCurrent from 5.50.0 to 5.52.0
Bumps UnitsNet.nanoFramework.Frequency from 5.50.0 to 5.52.0
Bumps nanoFramework.Iot.Device.Axp192 from 1.2.560 to 1.2.573
Bumps nanoFramework.Iot.Device.Rtc from 1.2.536 to 1.2.573
Bumps UnitsNet.nanoFramework.ElectricPotential from 5.50.0 to 5.52.0
Bumps UnitsNet.nanoFramework.Power from 5.50.0 to 5.52.0
Bumps nanoFramework.Iot.Device.Chsc6540 from 1.1.548 to 1.1.570
[version update]
Summary by CodeRabbit
nanoFramework.Iot.Devicepackages to the latest versions.UnitsNet.nanoFrameworkpackages to the latest versions.These updates ensure compatibility and improved performance for various test applications.