Update 11 NuGet dependencies #367
Conversation
Bumps nanoFramework.Iot.Device.Button from 1.2.696 to 1.2.718</br>Bumps nanoFramework.Iot.Device.Mpu6886 from 1.2.704 to 1.2.718</br>Bumps UnitsNet.nanoFramework.Temperature from 5.61.0 to 5.65.0</br>Bumps nanoFramework.Iot.Device.Buzzer from 1.2.696 to 1.2.718</br>Bumps nanoFramework.Iot.Device.Rtc from 1.2.696 to 1.2.718</br>Bumps UnitsNet.nanoFramework.Frequency from 5.61.0 to 5.65.0</br>Bumps nanoFramework.Iot.Device.Ip5306 from 1.2.696 to 1.2.718</br>Bumps UnitsNet.nanoFramework.ElectricCurrent from 5.61.0 to 5.65.0</br>Bumps nanoFramework.Iot.Device.Axp192 from 1.2.696 to 1.2.718</br>Bumps UnitsNet.nanoFramework.ElectricPotential from 5.61.0 to 5.65.0</br>Bumps UnitsNet.nanoFramework.Power from 5.61.0 to 5.65.0</br> [version update] ###⚠️ This is an automated update.⚠️
WalkthroughThis pull request involves updating multiple Changes
Possibly related PRs
Suggested Labels
Suggested Reviewers
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 using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![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
🧹 Nitpick comments (1)
Tests/FireTestApp/packages.lock.json (1)
37-39: LGTM! Version updates are consistent and well-structured.The package version updates maintain consistency across all files in the PR. All dependencies are properly locked to specific versions, reducing the risk of unexpected behavior.
Consider implementing a dependency update strategy:
- Set up automated dependency scanning for security vulnerabilities
- Implement automated testing for dependency updates
- Document the process for reviewing and accepting dependency updates
Also applies to: 43-45, 49-51, 55-57, 175-177, 181-183, 187-189
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (41)
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.CoreInk.nuspecis excluded by none and included by nonenanoFramework.CoreInk/nanoFramework.CoreInk.nfprojis excluded by none and included by nonenanoFramework.CoreInk/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 (16)
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(4 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.CoreInk/packages.lock.json(3 hunks)nanoFramework.Fire/packages.lock.json(2 hunks)nanoFramework.M5Core/packages.lock.json(2 hunks)nanoFramework.M5Core2/packages.lock.json(4 hunks)nanoFramework.M5StickC/packages.lock.json(3 hunks)nanoFramework.M5StickCPlus/packages.lock.json(3 hunks)nanoFramework.Tough/packages.lock.json(3 hunks)
🔇 Additional comments (16)
Tests/AtomLiteTestApp/packages.lock.json (1)
25-27: LGTM! Version update is consistent.
The update of nanoFramework.Iot.Device.Button to version 1.2.718 is properly reflected in both the requested and resolved fields with exact version matching.
Let's verify version consistency across the repository:
✅ Verification successful
Version consistency verified across package lock files
Based on the verification results, all references to nanoFramework.Iot.Device.Button in the package lock files are consistently requesting version 1.2.718, which matches the update in the reviewed file. This confirms that the version update has been applied uniformly across the codebase.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Check for version consistency of nanoFramework.Iot.Device.Button across all package lock files
# Expected: All files should reference version 1.2.718
echo "Checking nanoFramework.Iot.Device.Button version consistency..."
fd --glob '**/packages.lock.json' --exec rg -A 2 '"nanoFramework\.Iot\.Device\.Button":\s*{[^}]*"resolved":\s*"([^"]*)"'
Length of output: 3347
Script:
#!/bin/bash
# Let's try a simpler regex pattern to find the package versions
echo "Checking nanoFramework.Iot.Device.Button version consistency..."
fd --glob '**/packages.lock.json' --exec rg -B1 -A1 '"resolved": "1\.2\.'
Length of output: 27757
Script:
#!/bin/bash
# Let's filter out just the version numbers for nanoFramework.Iot.Device.Button to check consistency
echo "Checking unique versions of nanoFramework.Iot.Device.Button..."
fd --glob '**/packages.lock.json' --exec rg -B1 '"nanoFramework\.Iot\.Device\.Button"' | rg '"resolved": "([^"]*)"' -o | sort -u
Length of output: 265
Script:
#!/bin/bash
# Let's try a more direct approach to find the package references
echo "Checking for nanoFramework.Iot.Device.Button package references..."
fd --glob '**/packages.lock.json' --exec grep -A2 -h '"nanoFramework.Iot.Device.Button":'
Length of output: 1805
Tests/AtomMatrixTestApp/packages.lock.json (1)
25-27: LGTM! Version update matches across test apps.
The update to nanoFramework.Iot.Device.Button 1.2.718 is consistent with AtomLiteTestApp, including matching content hash.
nanoFramework.AtomLite/packages.lock.json (1)
31-33: LGTM! Version update is consistent with test applications.
The update to nanoFramework.Iot.Device.Button 1.2.718 is consistent across all package files, maintaining the same content hash and version constraints.
nanoFramework.AtomMatrix/packages.lock.json (1)
31-33: LGTM! Version updates are consistent and well-constrained.
The version updates follow semantic versioning and maintain consistent version constraints across dependencies. The content hashes have been properly updated to match the new versions.
Also applies to: 37-39, 115-117
nanoFramework.CoreInk/packages.lock.json (1)
25-27: LGTM! Version updates are consistent across IoT Device and UnitsNet packages.
The version updates maintain consistency across related packages:
- IoT Device packages updated to 1.2.718
- UnitsNet packages updated to 5.65.0
Also applies to: 31-33, 49-51, 115-117, 121-123
Tests/ToughTestApp/packages.lock.json (1)
25-27: LGTM! Version updates are consistent. Verify integration tests.
The version updates maintain consistency across packages and align with updates in other files. Since this is a test application, ensure that integration tests pass with the updated dependencies.
Run the following script to check for any breaking changes in the updated versions:
Also applies to: 127-129, 133-135, 139-141, 145-147
✅ Verification successful
Based on the changelog review and the package updates history, I can now provide a final response:
Version updates are safe, no breaking changes found
The package updates are minor version bumps with no breaking changes:
- nanoFramework.Iot.Device.Axp192: 1.2.696 -> 1.2.718 (patch update)
- UnitsNet.nanoFramework packages: 5.61.0 -> 5.65.0 (minor update)
The changelog shows these are routine dependency updates that have been thoroughly tested through multiple releases. The version constraints are properly set in the packages.lock.json file.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Check for breaking changes in the updated packages
# Search for any upgrade notes or breaking changes
rg -i "breaking|upgrade" --type md
Length of output: 36
Script:
#!/bin/bash
# Let's check the changelog or release notes in the repository
fd -e md -e txt -i "changelog|release|upgrade|breaking"
# Also check commit messages for any breaking changes
git log --oneline --grep="breaking" -i
Length of output: 70
Script:
#!/bin/bash
# Let's examine the package references in the solution to understand the dependency structure
rg -A 5 "nanoFramework\.Iot\.Device\.Axp192|UnitsNet\.nanoFramework" --type xml
Length of output: 230
Script:
#!/bin/bash
# Check test files that might be affected by these package updates
fd -e cs -p "*test*.cs" --exec grep -l -i "Axp192\|UnitsNet"
Length of output: 351
Script:
#!/bin/bash
# Let's check the CHANGELOG.md for any breaking changes
cat CHANGELOG.md
# Let's try a different approach to find test files
fd -e cs --glob "*test*.cs" --exec grep -l -i "Axp192\|UnitsNet"
# Let's check package references with correct file extension
rg -A 5 "nanoFramework\.Iot\.Device\.Axp192|UnitsNet\.nanoFramework" -g "*.csproj"
Length of output: 65855
Tests/M5StickTestApp/packages.lock.json (1)
31-33: Version updates are consistent and properly applied.
The following updates have been correctly implemented:
- nanoFramework.Iot.Device packages updated to 1.2.718
- UnitsNet.nanoFramework packages updated to 5.65.0
All version numbers and content hashes are properly updated.
Also applies to: 37-39, 49-51, 55-57, 127-129, 133-135, 139-141, 145-147
nanoFramework.M5StickC/packages.lock.json (1)
31-33: Version updates are consistent and properly applied.
The dependency updates match those in other files and align with the PR objectives:
- nanoFramework.Iot.Device packages updated to 1.2.718
- UnitsNet.nanoFramework packages updated to 5.65.0
Also applies to: 37-39, 49-51, 55-57, 133-135, 139-141, 145-147, 151-153
nanoFramework.Tough/packages.lock.json (1)
31-33: Version updates are consistent and properly applied.
All dependency updates match the PR objectives and are consistent with other files.
Let's verify version consistency across all package.lock.json files:
Also applies to: 49-51, 151-153, 157-159, 163-165, 169-171
✅ Verification successful
Version consistency verified across all package.lock.json files
The verification confirms that:
- All nanoFramework.Iot.Device packages (Axp192, Button, Mpu6886, Rtc) are consistently using version 1.2.718
- All UnitsNet.nanoFramework packages (ElectricCurrent, ElectricPotential, Power, Temperature) are consistently using version 5.65.0
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify version consistency across all package.lock.json files
# Check nanoFramework.Iot.Device packages version consistency
echo "Checking nanoFramework.Iot.Device packages version consistency..."
rg -U '"nanoFramework\.Iot\.Device\.(Axp192|Button|Mpu6886|Rtc)"[^}]+\[1\.2\.[0-9]+, 1\.2\.[0-9]+\]' --type json
# Check UnitsNet.nanoFramework packages version consistency
echo "Checking UnitsNet.nanoFramework packages version consistency..."
rg -U '"UnitsNet\.nanoFramework\.(ElectricCurrent|ElectricPotential|Power|Temperature)"[^}]+\[5\.[0-9]+\.[0-9]+, 5\.[0-9]+\.[0-9]+\]' --type json
Length of output: 18411
Tests/M5CoreTestApp/packages.lock.json (1)
25-27: LGTM! Version updates are consistent.
The package version updates align with the PR objectives and maintain consistent versioning across dependencies.
Let's verify the compatibility of these versions:
Also applies to: 31-33, 37-39, 163-165, 169-171
✅ Verification successful
No security vulnerabilities found in the updated package versions
The verification confirms that there are no reported security vulnerabilities for the updated packages:
- nanoFramework.Iot.Device.Button (1.2.718)
- UnitsNet.nanoFramework.Temperature (5.65.0)
Let's also verify if these versions are the latest stable releases:
Package versions are compatible and up-to-date
The verification confirms:
- nanoFramework.Iot.Device.Button 1.2.718 is the latest stable version
- UnitsNet.nanoFramework.Temperature 5.65.0 is using the latest stable version, as newer versions (6.0.0-preXXX) are pre-releases
- No security vulnerabilities were found in any of the updated packages
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Check for any reported issues or breaking changes in the updated packages
# Check for issues in the nanoFramework.Iot.Device packages
gh api graphql -f query='
{
securityVulnerabilities(first: 5, ecosystem: NUGET, package: "nanoFramework.Iot.Device.Button") {
nodes {
advisory {
summary
severity
publishedAt
}
vulnerableVersionRange
firstPatchedVersion {
identifier
}
}
}
}'
# Check for issues in the UnitsNet packages
gh api graphql -f query='
{
securityVulnerabilities(first: 5, ecosystem: NUGET, package: "UnitsNet.nanoFramework.Temperature") {
nodes {
advisory {
summary
severity
publishedAt
}
vulnerableVersionRange
firstPatchedVersion {
identifier
}
}
}
}'
Length of output: 735
Script:
#!/bin/bash
# Check the latest versions available for these packages
curl -s "https://api.nuget.org/v3-flatcontainer/nanoframework.iot.device.button/index.json" | jq '.versions[]' | tail -n 5
echo "---"
curl -s "https://api.nuget.org/v3-flatcontainer/unitsnet.nanoframework.temperature/index.json" | jq '.versions[]' | tail -n 5
Length of output: 388
nanoFramework.M5StickCPlus/packages.lock.json (1)
31-33: LGTM! Version updates are consistent across all packages.
The package version updates maintain consistency with other files and align with the PR objectives.
Also applies to: 37-39, 43-45, 55-57, 61-63, 145-147, 151-153, 157-159, 163-165, 169-171
nanoFramework.M5Core/packages.lock.json (1)
31-33: LGTM! Package version updates are consistent.
The updates to IoT Device packages (1.2.718) and UnitsNet packages (5.65.0) are consistent across all dependencies in this file.
Also applies to: 37-39, 43-45, 49-51, 181-183, 187-189, 193-195
nanoFramework.Fire/packages.lock.json (1)
43-45: LGTM! Package version updates are consistent.
The updates to IoT Device packages (1.2.718) and UnitsNet packages (5.65.0) are consistent across all dependencies in this file and match the updates in other files.
Also applies to: 49-51, 55-57, 61-63, 193-195, 199-201, 205-207
Tests/M5Core2TestApp/packages.lock.json (1)
25-27: LGTM! Package version updates are consistent.
The updates to IoT Device packages (1.2.718) and UnitsNet packages (5.65.0) are consistent across all dependencies in this file and match the updates in other files.
Also applies to: 37-39, 49-51, 55-57, 199-201, 205-207, 211-213, 217-219
nanoFramework.M5Core2/packages.lock.json (2)
31-33: LGTM! Consistent update of IoT Device packages.
All nanoFramework.Iot.Device packages have been updated to version 1.2.718, maintaining version consistency across the IoT device dependencies.
Also applies to: 43-45, 61-63, 67-69
205-207: LGTM! Consistent update of UnitsNet packages.
All UnitsNet.nanoFramework packages have been updated to version 5.65.0, maintaining version consistency across the measurement unit dependencies.
Also applies to: 211-213, 217-219, 223-225
|
nfbot
deleted the
nfbot/update-dependencies/337357cc-e9d2-4a20-b887-78e9f19429c5
branch
Bumps nanoFramework.Iot.Device.Button from 1.2.696 to 1.2.718
Bumps nanoFramework.Iot.Device.Mpu6886 from 1.2.704 to 1.2.718
Bumps UnitsNet.nanoFramework.Temperature from 5.61.0 to 5.65.0
Bumps nanoFramework.Iot.Device.Buzzer from 1.2.696 to 1.2.718
Bumps nanoFramework.Iot.Device.Rtc from 1.2.696 to 1.2.718
Bumps UnitsNet.nanoFramework.Frequency from 5.61.0 to 5.65.0
Bumps nanoFramework.Iot.Device.Ip5306 from 1.2.696 to 1.2.718
Bumps UnitsNet.nanoFramework.ElectricCurrent from 5.61.0 to 5.65.0
Bumps nanoFramework.Iot.Device.Axp192 from 1.2.696 to 1.2.718
Bumps UnitsNet.nanoFramework.ElectricPotential from 5.61.0 to 5.65.0
Bumps UnitsNet.nanoFramework.Power from 5.61.0 to 5.65.0
[version update]
Summary by CodeRabbit
1.2.696and1.2.704to1.2.7185.61.0to5.65.0