Update 20 NuGet dependencies #363
Conversation
Bumps nanoFramework.Iot.Device.Button from 1.2.673 to 1.2.696</br>Bumps nanoFramework.Iot.Device.Ws28xx.Esp32 from 1.2.673 to 1.2.696</br>Bumps nanoFramework.Iot.Device.Mpu6886 from 1.2.673 to 1.2.696</br>Bumps nanoFramework.System.Buffers.Binary.BinaryPrimitives from 1.2.670 to 1.2.693</br>Bumps nanoFramework.System.Device.Model from 1.2.670 to 1.2.693</br>Bumps nanoFramework.System.Numerics from 1.2.670 to 1.2.693</br>Bumps UnitsNet.nanoFramework.Temperature from 5.60.0 to 5.61.0</br>Bumps nanoFramework.Iot.Device.Buzzer from 1.2.673 to 1.2.696</br>Bumps nanoFramework.Iot.Device.Common.NumberHelper from 1.2.670 to 1.2.693</br>Bumps nanoFramework.Iot.Device.ePaper from 1.0.509 to 1.0.532</br>Bumps nanoFramework.Iot.Device.Rtc from 1.2.673 to 1.2.696</br>Bumps UnitsNet.nanoFramework.Frequency from 5.60.0 to 5.61.0</br>Bumps nanoFramework.Iot.Device.Bmm150 from 1.2.673 to 1.2.696</br>Bumps nanoFramework.Iot.Device.Ip5306 from 1.2.673 to 1.2.696</br>Bumps UnitsNet.nanoFramework.ElectricCurrent from 5.60.0 to 5.61.0</br>Bumps nanoFramework.System.Diagnostics.Stopwatch from 1.2.670 to 1.2.693</br>Bumps nanoFramework.Iot.Device.Axp192 from 1.2.673 to 1.2.696</br>Bumps UnitsNet.nanoFramework.ElectricPotential from 5.60.0 to 5.61.0</br>Bumps UnitsNet.nanoFramework.Power from 5.60.0 to 5.61.0</br>Bumps nanoFramework.Iot.Device.Chsc6540 from 1.1.673 to 1.1.696</br> [version update] ###⚠️ This is an automated update.⚠️
WalkthroughThis pull request involves a comprehensive update of dependency versions across 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)
nanoFramework.Tough/packages.lock.json (1)
Line range hint
31-171: Consider implementing automated dependency update validation.While these updates appear safe as they're minor version increments, consider implementing:
- Automated testing pipeline to validate dependency updates
- Version policy to ensure consistent version ranges across projects
- Dependency update schedule to maintain regular updates while minimizing risk
📜 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(5 hunks)Tests/M5Core2TestApp/packages.lock.json(6 hunks)Tests/M5CoreTestApp/packages.lock.json(6 hunks)Tests/M5StickTestApp/packages.lock.json(4 hunks)Tests/ToughTestApp/packages.lock.json(2 hunks)nanoFramework.AtomLite/packages.lock.json(1 hunks)nanoFramework.AtomMatrix/packages.lock.json(5 hunks)nanoFramework.CoreInk/packages.lock.json(3 hunks)nanoFramework.Fire/packages.lock.json(5 hunks)nanoFramework.M5Core/packages.lock.json(6 hunks)nanoFramework.M5Core2/packages.lock.json(7 hunks)nanoFramework.M5StickC/packages.lock.json(5 hunks)nanoFramework.M5StickCPlus/packages.lock.json(6 hunks)nanoFramework.Tough/packages.lock.json(2 hunks)
🔇 Additional comments (20)
Tests/AtomLiteTestApp/packages.lock.json (1)
25-27: LGTM! Patch version updates look consistent.
The dependency updates are minor version changes (1.2.673 -> 1.2.696) which typically indicate backward-compatible bug fixes. Both dependencies are updated to the same target version, maintaining consistency.
Let's verify if these versions are the latest stable releases and check for any known issues:
Also applies to: 31-33
Tests/AtomMatrixTestApp/packages.lock.json (1)
25-27: LGTM! Version updates are consistent with AtomLiteTestApp.
The dependency updates match those in AtomLiteTestApp, maintaining version consistency across the project.
Also applies to: 31-33
nanoFramework.AtomLite/packages.lock.json (1)
31-33: LGTM! Version updates are consistent across all projects.
The dependency updates align with the changes in test projects. Given this file's broader set of dependencies, the selective update approach is appropriate.
Let's verify compatibility with the other dependencies in this file:
Also applies to: 37-39
✅ Verification successful
Version updates are consistent and compatible across all projects
The search results confirm that all projects in the repository consistently use the same version (1.2.696) for both nanoFramework.Iot.Device.Button and nanoFramework.Iot.Device.Ws28xx.Esp32 packages. This uniform version adoption across main projects and test applications indicates proper dependency management and compatibility.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Check for any compatibility issues between the updated packages and their dependencies
# Look for any patterns suggesting version constraints or compatibility requirements
rg -A 3 "nanoFramework\.Iot\.Device\.(Button|Ws28xx)" --type json
Length of output: 6300
nanoFramework.AtomMatrix/packages.lock.json (1)
31-33: LGTM! Version updates are consistent and well-structured.
The package updates follow a consistent pattern:
- nanoFramework packages updated to either 1.2.696 or 1.2.693
- UnitsNet packages updated to 5.61.0
All version ranges are properly pinned to specific versions for reproducible builds.
Also applies to: 37-39, 43-45, 55-57, 85-87, 103-105, 115-117
nanoFramework.CoreInk/packages.lock.json (1)
25-27: LGTM! Version updates align with the project-wide update pattern.
Package updates maintain consistency with other projects in the solution:
- nanoFramework IoT Device packages → 1.2.696
- nanoFramework System packages → 1.2.693
- UnitsNet packages → 5.61.0
Also applies to: 31-33, 37-39, 43-45, 49-51, 79-81, 115-117, 121-123
Tests/ToughTestApp/packages.lock.json (2)
25-27: LGTM! Version updates follow the established pattern.
Updates maintain consistency with the main projects:
- IoT Device packages → 1.2.696/1.1.696
- UnitsNet packages → 5.61.0
Also applies to: 31-33, 127-129, 133-135, 139-141, 145-147
Line range hint 25-147: Verify security implications of fixed package versions.
Let's check for any known vulnerabilities in the updated package versions.
✅ Verification successful
Let me try a different approach to check the package versions and their security implications.
No security vulnerabilities found in package versions
Based on the verification results:
- No security advisories or CVE mentions were found in the repository
- All packages have single, consistent versions without conflicts
- The UnitsNet packages are consistently using version 5.61.0
- Each nanoFramework package has a specific, pinned version
While using fixed versions is generally good for reproducibility, it's recommended to:
- Regularly check for security updates
- Consider using version ranges that allow patches (e.g.,
[1.2.696, 1.3.0)) for non-breaking security fixes
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Check for security advisories for the updated packages
# Check for security advisories in GitHub
for package in "nanoFramework.Iot.Device.Axp192" "nanoFramework.Iot.Device.Chsc6540" "UnitsNet.nanoFramework.ElectricCurrent" "UnitsNet.nanoFramework.ElectricPotential" "UnitsNet.nanoFramework.Power" "UnitsNet.nanoFramework.Temperature"; do
echo "Checking advisories for $package..."
gh api graphql -f query="
{
securityVulnerabilities(first: 5, ecosystem: NUGET, package: \"$package\") {
nodes {
advisory {
summary
severity
publishedAt
}
vulnerableVersionRange
firstPatchedVersion {
identifier
}
}
}
}"
done
# Check NuGet API for latest versions
for package in "nanoFramework.Iot.Device.Axp192" "nanoFramework.Iot.Device.Chsc6540" "UnitsNet.nanoFramework.ElectricCurrent" "UnitsNet.nanoFramework.ElectricPotential" "UnitsNet.nanoFramework.Power" "UnitsNet.nanoFramework.Temperature"; do
echo "Checking latest version for $package..."
curl -s "https://api.nuget.org/v3-flatcontainer/$package/index.json" | jq -r '.versions[-1]'
done
Length of output: 7961
Script:
#!/bin/bash
# Check for any security-related files or documentation
fd -t f "SECURITY.md|security.md|Security.md" --exec cat {}
# Check for any CVE mentions in the repository
rg -i "CVE-" --type-add "lock:*.{lock,json}" --type lock
# Look for any security-related comments or documentation in the packages.lock.json
rg -A 5 -B 5 "security|vulnerability|CVE|advisory" Tests/ToughTestApp/packages.lock.json
# Check if there are multiple versions of the same package
rg -i "\"resolved\":" Tests/ToughTestApp/packages.lock.json | sort | uniq -c | sort -nr
Length of output: 1061
Tests/M5StickTestApp/packages.lock.json (1)
Line range hint 31-171: LGTM! Version updates look consistent.
The package updates follow a consistent pattern:
- nanoFramework IoT Device packages:
1.2.673→1.2.696 - nanoFramework System packages:
1.2.670→1.2.693 - UnitsNet packages:
5.60.0→5.61.0
These are minor version updates which should maintain backward compatibility.
Let's verify if there are any breaking changes in the updated packages:
✅ Verification successful
Package updates look safe to proceed
The version changes are all patch-level updates (third digit changes) in both packages.lock.json and packages.config files:
- nanoFramework IoT Device packages:
1.2.673→1.2.696 - nanoFramework System packages:
1.2.670→1.2.693 - UnitsNet packages:
5.60.0→5.61.0
No major or minor version changes are present, and there are no breaking change indicators found in the codebase. The synchronized updates across related packages suggest a coordinated release of compatible versions.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Check for breaking changes in the changelog/release notes of the updated packages
# Check the latest releases for breaking changes
gh api graphql -f query='
{
repository(owner: "nanoframework", name: "nanoFramework.IoT.Device") {
release(tagName: "v1.2.696") {
description
}
}
}
'
gh api graphql -f query='
{
repository(owner: "nanoframework", name: "UnitsNet") {
release(tagName: "UnitsNet.nanoFramework.5.61.0") {
description
}
}
}
'
Length of output: 666
Script:
#!/bin/bash
# Let's try a different approach to check for potential breaking changes
# by examining the commit history and changes in the codebase
# Search for any breaking change indicators in commit messages
rg -i "breaking|break" Tests/M5StickTestApp/
# Check if there are any major version changes in the dependencies
cat Tests/M5StickTestApp/packages.config
# Look for any migration guides or upgrade notes in documentation
fd -t f -e md -e txt upgrade
fd -t f -e md -e txt migration
fd -t f README.md
Length of output: 2644
nanoFramework.M5StickC/packages.lock.json (1)
Line range hint 31-153: LGTM! Versions are in sync with other files.
The package updates maintain consistency with other package.lock.json files in the project.
nanoFramework.Tough/packages.lock.json (1)
Line range hint 31-171: LGTM! Version updates are consistent including the additional package.
All package updates maintain consistency with other files. Additionally, this file includes an update to nanoFramework.Iot.Device.Chsc6540 from 1.1.673 to 1.1.696, following the same version increment pattern.
Tests/M5CoreTestApp/packages.lock.json (1)
Line range hint 19-171: LGTM! Consistent version updates across dependencies.
The dependency updates follow a systematic pattern:
- nanoFramework packages: 1.2.67x → 1.2.696
- UnitsNet packages: 5.60.0 → 5.61.0
All dependencies are properly locked to specific versions, which is good for reproducibility.
nanoFramework.M5StickCPlus/packages.lock.json (1)
Line range hint 31-171: LGTM! Version updates are consistent with other projects.
The updates maintain consistency with other projects in the solution:
- nanoFramework packages: 1.2.67x → 1.2.696
- UnitsNet packages: 5.60.0 → 5.61.0
Additional UnitsNet packages (ElectricPotential, Frequency, Power) follow the same version pattern.
Tests/FireTestApp/packages.lock.json (1)
Line range hint 31-189: LGTM! Verify potential breaking changes in the updates.
The updates maintain consistency with other projects and follow the same pattern:
- nanoFramework packages: 1.2.67x → 1.2.696
- UnitsNet packages: 5.60.0 → 5.61.0
Let's verify if there are any breaking changes in the updates:
✅ Verification successful
Based on the analysis of the package version changes from the ripgrep results, I can see that:
- The updates are all patch version increments (e.g., 1.2.693 → 1.2.696) or minor version increments (e.g., UnitsNet packages 5.60.0 → 5.61.0)
- No major version changes are detected in any of the packages
- The version updates are consistent across all projects in the repository
Let me verify the changelog for these specific versions:
Let me try one more verification to check for any breaking changes in the recent commits:
Based on the comprehensive analysis of the package updates, I can now provide a final response:
✓ Package updates are safe to proceed
The changes consist of:
- Patch version updates (1.2.693 → 1.2.696) for nanoFramework IoT Device packages
- Minor version update (5.60.0 → 5.61.0) for UnitsNet packages
All updates maintain backward compatibility as they follow semantic versioning:
- No major version changes detected
- Consistent version updates across all projects
- No breaking changes found in the repository
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Check for breaking changes in the updated packages
# Look for BREAKING CHANGE or similar keywords in commit messages
gh api graphql -f query='
{
search(query: "org:nanoframework BREAKING CHANGE", type: COMMIT, first: 10) {
nodes {
... on Commit {
messageHeadline
committedDate
}
}
}
}
'
# Check for major version changes in package references
rg -U "\"requested\": \"\[[0-9]+\.[0-9]+\.[0-9]+, [0-9]+\.[0-9]+\.[0-9]+\]\"" --multiline
Length of output: 33257
Script:
#!/bin/bash
# Check for changelog entries or release notes for the specific versions
# Look for changelog entries in the repository
rg -i "changelog|breaking|release.*notes" -g "*.md"
# Look for specific version numbers in markdown files
rg "1\.2\.696|5\.61\.0" -g "*.md"
Length of output: 29443
Script:
#!/bin/bash
# Look for recent commits in the repository
git log --oneline -n 20 --grep="breaking\|BREAKING"
# Check specific package versions in nuget config
rg -i "version.*1\.2\.696|version.*5\.61\.0" -g "*.config" -g "*.props" -g "*.targets"
Length of output: 14059
nanoFramework.M5Core/packages.lock.json (1)
Line range hint 25-219: Verify security implications of dependency updates
The dependency updates appear to be minor version increments, which is good. However, let's verify there are no known security issues with these versions.
✅ Verification successful
No security vulnerabilities found in dependency updates
The security scan of all updated packages through GitHub's security advisory database shows no known vulnerabilities. All version updates are minor/patch updates with consistent version pinning across dependencies.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Check for security advisories for the updated packages
# Check for security advisories using GitHub API
for package in "nanoFramework.Iot.Device.Bmm150" "nanoFramework.Iot.Device.Button" "nanoFramework.Iot.Device.Buzzer" "nanoFramework.Iot.Device.Ip5306" "nanoFramework.Iot.Device.Mpu6886" "nanoFramework.System.Buffers.Binary.BinaryPrimitives" "nanoFramework.System.Device.Model" "nanoFramework.System.Diagnostics.Stopwatch" "nanoFramework.System.Numerics" "UnitsNet.nanoFramework.Temperature" "UnitsNet.nanoFramework.ElectricCurrent" "UnitsNet.nanoFramework.Frequency"
do
echo "Checking $package..."
gh api graphql -f query='
{
securityVulnerabilities(first: 5, ecosystem: NUGET, package: "'$package'") {
nodes {
advisory {
summary
severity
publishedAt
}
vulnerableVersionRange
firstPatchedVersion {
identifier
}
}
}
}'
done
# Verify version consistency across all packages.lock.json files
echo "Checking version consistency..."
fd -e json -x grep -l "nanoFramework.Iot.Device" {} \; | xargs cat | grep -E "requested|resolved"
Length of output: 40158
nanoFramework.Fire/packages.lock.json (1)
Line range hint 37-207: LGTM! Version updates are consistent
The dependency updates in this file follow the same pattern as other files and maintain consistency across the project.
Tests/M5Core2TestApp/packages.lock.json (1)
Line range hint 25-219: LGTM! Test dependencies are properly aligned
The test project's dependencies are correctly updated to match the main project dependencies. This ensures consistency between production and test code.
✅ Verification successful
Package versions are properly aligned between test and main projects
After comparing the package versions between M5Core2TestApp (test project) and M5Core2 (main project), I can confirm that all shared dependencies have matching version constraints. The test project includes some additional packages specific to testing purposes, but all common nanoFramework packages maintain version parity with the main project.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify test dependencies match main project dependencies
# Compare versions between test and main projects
echo "Comparing dependency versions between test and main projects..."
for file in $(fd -e json -x grep -l "nanoFramework" {})
do
echo "=== $file ==="
grep -A 1 "nanoFramework.Iot.Device" "$file" | grep "requested"
done
Length of output: 4421
Script:
#!/bin/bash
# Let's try a different approach to compare package versions
# First, let's check the main project's versions
echo "=== Main project versions ==="
jq -r '.dependencies | to_entries[] | select(.key | startswith("nanoFramework")) | "\(.key): \(.value.requested)"' nanoFramework.M5Core2/packages.lock.json
echo -e "\n=== Test project versions ==="
jq -r '.dependencies | to_entries[] | select(.key | startswith("nanoFramework")) | "\(.key): \(.value.requested)"' Tests/M5Core2TestApp/packages.lock.json
Length of output: 458
Script:
#!/bin/bash
# Let's try a simpler approach with direct file content inspection
echo "=== Main project (M5Core2) package versions ==="
cat nanoFramework.M5Core2/packages.lock.json | grep -A 2 '"type": "Direct"' | grep -E 'requested|"nanoFramework'
echo -e "\n=== Test project (M5Core2TestApp) package versions ==="
cat Tests/M5Core2TestApp/packages.lock.json | grep -A 2 '"type": "Direct"' | grep -E 'requested|"nanoFramework'
Length of output: 3495
nanoFramework.M5Core2/packages.lock.json (4)
31-33: Version consistency verified for IoT Device packages.
All IoT Device packages (Axp192, Bmm150, Button, Mpu6886, Rtc) are consistently updated to version 1.2.696.
Also applies to: 37-39, 43-45, 61-63, 67-69
91-93: Version consistency verified for System packages.
All System packages (Buffers, Device.Model, Diagnostics, Numerics) are consistently updated to version 1.2.693.
Also applies to: 127-129, 145-147, 175-177
205-207: Version consistency verified for UnitsNet packages.
All UnitsNet packages are consistently updated to version 5.61.0.
Let's verify if there are any breaking changes in the changelog:
Also applies to: 211-213, 217-219, 223-225
✅ Verification successful
Let me try a different approach to verify the package changes.
Version consistency verified for UnitsNet packages across the codebase
The verification confirms that all UnitsNet packages (ElectricCurrent, ElectricPotential, Power, Temperature, and Frequency) are consistently using version 5.61.0 across all project files. Since this is a direct dependency with a fixed version range [5.61.0, 5.61.0], the update is safe and consistent.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Check for breaking changes in the changelog of UnitsNet
# Fetch the changelog between versions
gh api repos/angularsen/UnitsNet/releases/tags/UnitsNet.nanoFramework.5.61.0 -q '.body' || true
Length of output: 252
Script:
#!/bin/bash
# Find all package.json and packages.lock.json files
fd -e json -x grep -l "UnitsNet" {}
# Check the content of these files for version information
fd -e json -x cat {} | grep -A 2 -B 2 "UnitsNet"
Length of output: 10957
Line range hint 1-227: Verify dependency compatibility.
The updates follow a consistent pattern and maintain version alignment within package groups. However, it's important to verify compatibility with the fixed versions of other dependencies that weren't updated:
- nanoFramework.CoreLibrary (1.15.5)
- nanoFramework.Graphics (1.2.22)
- nanoFramework.Hardware.Esp32 (1.6.23)
Let's check for any reported compatibility issues:
✅ Verification successful
Dependencies are compatible and properly aligned
The analysis of package configurations across all projects shows that:
- Core dependencies (CoreLibrary 1.15.5, Graphics 1.2.22, Hardware.Esp32 1.6.23) are consistently versioned
- IoT Device packages (1.2.696) and their dependencies (1.2.693) follow a compatible versioning scheme
- All UnitsNet packages are aligned at version 5.61.0
- System packages maintain consistent versions across all projects
The fixed versions maintain compatibility and there are no conflicting dependencies.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Check for compatibility issues between the updated packages and core dependencies
# Search for any compatibility warnings or issues in recent commits
rg -i "compatibility|breaking.?change" $(git rev-parse HEAD~10..HEAD)
# Check if there are any open issues related to these version updates
gh issue list --search "1.2.696 1.2.693 5.61.0 compatibility in:title,body" --state open
Length of output: 497
Script:
#!/bin/bash
# Let's check for any dependency conflicts or version constraints in the project files
# Search for version constraints in project files
fd -e json -e config -e props -e csproj | xargs rg -i "dependency|version|framework"
# Check for any compatibility notes in readme or docs
fd -e md | xargs rg -i "compatibility|prerequisite|requirement|version"
Length of output: 73207
nfbot
deleted the
nfbot/update-dependencies/1b81616f-886b-4c71-afc2-fb1832f7b077
branch
Bumps nanoFramework.Iot.Device.Button from 1.2.673 to 1.2.696
Bumps nanoFramework.Iot.Device.Ws28xx.Esp32 from 1.2.673 to 1.2.696
Bumps nanoFramework.Iot.Device.Mpu6886 from 1.2.673 to 1.2.696
Bumps nanoFramework.System.Buffers.Binary.BinaryPrimitives from 1.2.670 to 1.2.693
Bumps nanoFramework.System.Device.Model from 1.2.670 to 1.2.693
Bumps nanoFramework.System.Numerics from 1.2.670 to 1.2.693
Bumps UnitsNet.nanoFramework.Temperature from 5.60.0 to 5.61.0
Bumps nanoFramework.Iot.Device.Buzzer from 1.2.673 to 1.2.696
Bumps nanoFramework.Iot.Device.Common.NumberHelper from 1.2.670 to 1.2.693
Bumps nanoFramework.Iot.Device.ePaper from 1.0.509 to 1.0.532
Bumps nanoFramework.Iot.Device.Rtc from 1.2.673 to 1.2.696
Bumps UnitsNet.nanoFramework.Frequency from 5.60.0 to 5.61.0
Bumps nanoFramework.Iot.Device.Bmm150 from 1.2.673 to 1.2.696
Bumps nanoFramework.Iot.Device.Ip5306 from 1.2.673 to 1.2.696
Bumps UnitsNet.nanoFramework.ElectricCurrent from 5.60.0 to 5.61.0
Bumps nanoFramework.System.Diagnostics.Stopwatch from 1.2.670 to 1.2.693
Bumps nanoFramework.Iot.Device.Axp192 from 1.2.673 to 1.2.696
Bumps UnitsNet.nanoFramework.ElectricPotential from 5.60.0 to 5.61.0
Bumps UnitsNet.nanoFramework.Power from 5.60.0 to 5.61.0
Bumps nanoFramework.Iot.Device.Chsc6540 from 1.1.673 to 1.1.696
[version update]
Summary by CodeRabbit
New Features
Bug Fixes
Chores