Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update 11 NuGet dependencies #370

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

nfbot
Copy link
Member

@nfbot nfbot commented Jan 15, 2025

Bumps nanoFramework.Iot.Device.Button from 1.2.718 to 1.2.737
Bumps nanoFramework.Iot.Device.Ws28xx.Esp32 from 1.2.696 to 1.2.737
Bumps Nerdbank.GitVersioning from 3.7.112 to 3.7.115
Bumps nanoFramework.Iot.Device.Mpu6886 from 1.2.718 to 1.2.737
Bumps nanoFramework.Iot.Device.Buzzer from 1.2.718 to 1.2.737
Bumps nanoFramework.Iot.Device.ePaper from 1.0.558 to 1.0.573
Bumps nanoFramework.Iot.Device.Rtc from 1.2.718 to 1.2.737
Bumps nanoFramework.Iot.Device.Bmm150 from 1.2.704 to 1.2.737
Bumps nanoFramework.Iot.Device.Ip5306 from 1.2.718 to 1.2.737
Bumps nanoFramework.Iot.Device.Axp192 from 1.2.718 to 1.2.737
Bumps nanoFramework.Iot.Device.Chsc6540 from 1.1.696 to 1.1.737

[version update]

⚠️ This is an automated update. ⚠️

Summary by CodeRabbit

  • Dependency Updates
    • Multiple nanoFramework IoT device dependencies updated across various projects
    • Most dependencies upgraded from versions like 1.2.718 to 1.2.737
    • Nerdbank.GitVersioning updated from 3.7.112 to 3.7.115
    • Updates span multiple device libraries including Button, Mpu6886, Axp192, Bmm150, and others

Bumps nanoFramework.Iot.Device.Button from 1.2.718 to 1.2.737</br>Bumps nanoFramework.Iot.Device.Ws28xx.Esp32 from 1.2.696 to 1.2.737</br>Bumps Nerdbank.GitVersioning from 3.7.112 to 3.7.115</br>Bumps nanoFramework.Iot.Device.Mpu6886 from 1.2.718 to 1.2.737</br>Bumps nanoFramework.Iot.Device.Buzzer from 1.2.718 to 1.2.737</br>Bumps nanoFramework.Iot.Device.ePaper from 1.0.558 to 1.0.573</br>Bumps nanoFramework.Iot.Device.Rtc from 1.2.718 to 1.2.737</br>Bumps nanoFramework.Iot.Device.Bmm150 from 1.2.704 to 1.2.737</br>Bumps nanoFramework.Iot.Device.Ip5306 from 1.2.718 to 1.2.737</br>Bumps nanoFramework.Iot.Device.Axp192 from 1.2.718 to 1.2.737</br>Bumps nanoFramework.Iot.Device.Chsc6540 from 1.1.696 to 1.1.737</br>
[version update]

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

coderabbitai bot commented Jan 15, 2025

Walkthrough

This pull request involves updating dependency versions across multiple packages.lock.json files in various nanoFramework projects. The updates primarily focus on incrementing versions of IoT device-related dependencies and the Nerdbank.GitVersioning tool. Most dependencies are being upgraded from versions around 1.2.718 to 1.2.737, with some specific variations. These updates span multiple project configurations, including AtomLite, AtomMatrix, Fire, M5Core, M5Core2, M5StickC, and others.

Changes

File Path Change Summary
Tests/*/packages.lock.json Updated multiple dependencies like nanoFramework.Iot.Device.Button, nanoFramework.Iot.Device.Ws28xx.Esp32, nanoFramework.Iot.Device.Bmm150, etc. from versions 1.2.718 to 1.2.737
nanoFramework.*/packages.lock.json Updated dependencies including nanoFramework.Iot.Device.* and Nerdbank.GitVersioning from versions like 1.2.718 to 1.2.737 and 3.7.112 to 3.7.115

Possibly related PRs

Suggested Labels

CI: Publish Release

Suggested Reviewers

  • Ellerbach

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?

❤️ 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. (Beta)
  • @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.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
Tests/M5Core2TestApp/packages.lock.json (1)

25-27: LGTM! Consistent version updates across dependencies.

All IoT Device dependencies have been updated to version 1.2.737, maintaining consistency with other projects.

Summary of changes across all files:

  1. IoT Device packages updated from various versions (1.2.718, 1.2.704, 1.2.696) to 1.2.737
  2. Nerdbank.GitVersioning updated from 3.7.112 to 3.7.115
  3. All version ranges are strictly pinned using [x.y.z, x.y.z] format

Consider adding a centralized version management system (like Directory.Packages.props) to maintain consistent versions across all projects and simplify future updates.

Also applies to: 31-33, 37-39, 49-51, 55-57

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 72ee5af and d02a4b8.

⛔ 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 (2 hunks)
  • Tests/M5CoreTestApp/packages.lock.json (1 hunks)
  • Tests/M5StickTestApp/packages.lock.json (2 hunks)
  • Tests/ToughTestApp/packages.lock.json (1 hunks)
  • nanoFramework.AtomLite/packages.lock.json (2 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 (3 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 updates are consistent.

The dependency updates are patch version increments, which typically indicate backward-compatible bug fixes:

  • nanoFramework.Iot.Device.Button: 1.2.718 → 1.2.737
  • nanoFramework.Iot.Device.Ws28xx.Esp32: 1.2.696 → 1.2.737

Let's verify version consistency across projects:

Also applies to: 31-33

✅ Verification successful

Version consistency verified across all projects

Both packages are consistently updated to version 1.2.737 in all package configurations, lock files, and NuGet specifications.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check version consistency of updated packages across all projects.
# Test: Search for these package versions in all packages.lock.json files.
# Expect: All occurrences should use the same version.

echo "Checking nanoFramework.Iot.Device.Button versions:"
rg '"nanoFramework\.Iot\.Device\.Button"' -A 2

echo "Checking nanoFramework.Iot.Device.Ws28xx.Esp32 versions:"
rg '"nanoFramework\.Iot\.Device\.Ws28xx\.Esp32"' -A 2

Length of output: 16738

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

25-27: Same version updates as in AtomLiteTestApp.

The changes are identical to those in AtomLiteTestApp/packages.lock.json.

Also applies to: 31-33

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

79-81: LGTM! Nerdbank.GitVersioning update looks good.

The update from 3.7.112 to 3.7.115 is a patch version increment, which typically indicates backward-compatible bug fixes.

Let's verify version consistency for this package:

✅ Verification successful

Version consistency verified for Nerdbank.GitVersioning

All projects in the codebase are using version 3.7.115 consistently.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check version consistency of Nerdbank.GitVersioning across projects.
# Test: Search for this package version in all packages.lock.json files.
# Expect: All occurrences should use version 3.7.115.

echo "Checking Nerdbank.GitVersioning versions:"
rg '"Nerdbank\.GitVersioning"' -A 2

Length of output: 5860

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

37-39: LGTM! Mpu6886 update follows the same pattern.

The update of nanoFramework.Iot.Device.Mpu6886 from 1.2.718 to 1.2.737 is consistent with other IoT device library updates.

Let's verify version consistency:

✅ Verification successful

Version consistency verified for nanoFramework.Iot.Device.Mpu6886

All projects in the codebase consistently use version 1.2.737 of the package.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check version consistency of Mpu6886 across projects.
# Test: Search for this package version in all packages.lock.json files.
# Expect: All occurrences should use version 1.2.737.

echo "Checking nanoFramework.Iot.Device.Mpu6886 versions:"
rg '"nanoFramework\.Iot\.Device\.Mpu6886"' -A 2

Length of output: 8553

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

31-33: LGTM! New IoT device library updates follow consistent patterns.

New updates are all patch version increments:

  • nanoFramework.Iot.Device.Buzzer: 1.2.718 → 1.2.737
  • nanoFramework.Iot.Device.ePaper: 1.0.558 → 1.0.573
  • nanoFramework.Iot.Device.Rtc: 1.2.718 → 1.2.737

Let's verify version consistency:

Also applies to: 43-45, 49-51

✅ Verification successful

✓ Version consistency verified across all IoT device library dependencies

All updated packages show perfect version alignment across the entire codebase:

  • nanoFramework.Iot.Device.Buzzer (1.2.737)
  • nanoFramework.Iot.Device.ePaper (1.0.573)
  • nanoFramework.Iot.Device.Rtc (1.2.737)
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check version consistency of new IoT device libraries.
# Test: Search for these package versions in all packages.lock.json files.
# Expect: All occurrences should use the specified versions.

echo "Checking nanoFramework.Iot.Device.Buzzer versions:"
rg '"nanoFramework\.Iot\.Device\.Buzzer"' -A 2

echo "Checking nanoFramework.Iot.Device.ePaper versions:"
rg '"nanoFramework\.Iot\.Device\.ePaper"' -A 2

echo "Checking nanoFramework.Iot.Device.Rtc versions:"
rg '"nanoFramework\.Iot\.Device\.Rtc"' -A 2

Length of output: 11945

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

25-27: LGTM! Dependency updates look good.

The version updates for both dependencies follow semantic versioning with patch version increments, maintaining backward compatibility.

Also applies to: 31-33

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

31-33: LGTM! Consistent dependency updates.

All IoT device dependencies have been updated to version 1.2.737, maintaining consistency across the package ecosystem.

Also applies to: 37-39, 49-51, 55-57

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

31-33: LGTM! Version updates are consistent.

All dependencies have been updated to their latest patch versions:

  • IoT device packages to 1.2.737
  • Nerdbank.GitVersioning to 3.7.115

Also applies to: 37-39, 49-51, 55-57, 127-129

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

31-33: LGTM! Version updates are aligned.

Dependencies have been consistently updated across the project:

  • IoT device packages to 1.2.737
  • Nerdbank.GitVersioning to 3.7.115

Also applies to: 37-39, 49-51, 145-147

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

19-21: LGTM! Dependency versions are in sync.

All IoT device packages have been updated to version 1.2.737, maintaining consistency with other projects in the solution.

Also applies to: 25-27, 31-33, 37-39

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

31-33: Verify compatibility of updated dependencies.

The following dependencies have been updated:

  • IoT Device packages from 1.2.718 to 1.2.737
  • Nerdbank.GitVersioning from 3.7.112 to 3.7.115

Run the following script to check for any breaking changes or known issues:

Also applies to: 37-39, 43-45, 55-57, 61-63, 139-141

✅ Verification successful

Dependencies update verified as compatible

The update from 1.2.718 to 1.2.737 consists of routine maintenance changes with no breaking changes or reported issues. All IoT Device packages are consistently updated to the same version.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for breaking changes in the updated dependencies

# Search for any BREAKING CHANGE markers in commit messages
echo "Checking for breaking changes in IoT Device packages..."
gh api graphql -f query='
{
  search(query: "org:nanoframework BREAKING CHANGE", type: COMMIT, first: 10) {
    nodes {
      ... on Commit {
        messageHeadline
        message
        committedDate
      }
    }
  }
}'

# Check for any reported issues related to these versions
echo "Checking for reported issues..."
gh api graphql -f query='
{
  search(query: "org:nanoframework 1.2.737 is:issue", type: ISSUE, first: 10) {
    nodes {
      ... on Issue {
        title
        url
        state
      }
    }
  }
}'

Length of output: 1378


Script:

#!/bin/bash
# Search for changelog files and relevant version information
echo "Searching for changelog files..."
fd -i changelog

echo -e "\nSearching for version-related commits..."
gh search commits --repo="nanoframework/nf-interpreter" "bump version 1.2.7" --limit 20

echo -e "\nChecking for compatibility documentation..."
fd -e md | xargs rg -l "1\.2\.(718|737)"

Length of output: 436


Script:

#!/bin/bash
# Check changelog contents
echo "Reading CHANGELOG.md..."
cat CHANGELOG.md

echo -e "\nSearching for version bumps with different pattern..."
gh search commits --repo="nanoframework/nf-interpreter" "update version" --limit 10

echo -e "\nChecking documentation with broader version pattern..."
rg -l "## \[?1\.2\." CHANGELOG.md README.md 2>/dev/null || true

Length of output: 65987

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

31-33: LGTM! Consistent version updates across IoT Device dependencies.

All IoT Device dependencies have been updated to version 1.2.737, maintaining consistency across the package versions.

Also applies to: 37-39, 43-45, 49-51, 55-57, 61-63

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

25-27: LGTM! Consistent version updates across dependencies.

All IoT Device dependencies have been updated to version 1.2.737 and Nerdbank.GitVersioning to 3.7.115, maintaining consistency with other projects.

Also applies to: 31-33, 37-39, 43-45, 49-51, 175-177

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

37-39: LGTM! Consistent version updates across dependencies.

All IoT Device dependencies have been updated to version 1.2.737 and Nerdbank.GitVersioning to 3.7.115, maintaining consistency with other projects.

Also applies to: 43-45, 49-51, 55-57, 61-63, 67-69, 187-189

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

199-201: Build Tool Update Looks Good!

The Nerdbank.GitVersioning tool has been updated to version 3.7.115, which is a minor version bump focusing on build improvements.


Line range hint 31-69: IoT Device Package Updates Look Good!

The IoT device packages have been consistently updated to version 1.2.737, which aligns with the PR objectives. This coordinated update ensures compatibility between the IoT device packages.

Let's verify that all IoT device packages are on the same version:

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.

1 participant