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 5 NuGet dependencies #331

Merged

Conversation

nfbot
Copy link
Member

@nfbot nfbot commented May 31, 2024

Bumps nanoFramework.Iot.Device.Button from 1.2.552 to 1.2.560
Bumps nanoFramework.System.Device.Gpio from 1.1.38 to 1.1.41
Bumps nanoFramework.System.Device.Spi from 1.3.48 to 1.3.52
Bumps nanoFramework.Iot.Device.Bmm150 from 1.2.552 to 1.2.560
Bumps nanoFramework.Iot.Device.Axp192 from 1.2.548 to 1.2.560

[version update]

⚠️ This is an automated update. ⚠️

Summary by CodeRabbit

  • Chores
    • Updated various nanoFramework package versions and content hashes across multiple test applications and frameworks to ensure compatibility and stability.

Bumps nanoFramework.Iot.Device.Button from 1.2.552 to 1.2.560</br>Bumps nanoFramework.System.Device.Gpio from 1.1.38 to 1.1.41</br>Bumps nanoFramework.System.Device.Spi from 1.3.48 to 1.3.52</br>Bumps nanoFramework.Iot.Device.Bmm150 from 1.2.552 to 1.2.560</br>Bumps nanoFramework.Iot.Device.Axp192 from 1.2.548 to 1.2.560</br>
[version update]

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

coderabbitai bot commented May 31, 2024

Walkthrough

The changes involve updating the versions and content hashes of various nanoFramework packages across multiple projects. These updates primarily affect packages related to device interaction, such as Button, Gpio, I2c, and Spi. The updates ensure that all projects use the latest versions of these packages, improving compatibility and potentially fixing bugs or adding new features.

Changes

Files/Paths Change Summary
Tests/AtomLiteTestApp/packages.lock.json
Tests/AtomMatrixTestApp/packages.lock.json
Tests/FireTestApp/packages.lock.json
Tests/M5Core2TestApp/packages.lock.json
Tests/M5CoreTestApp/packages.lock.json
Tests/M5StickTestApp/packages.lock.json
Tests/ToughTestApp/packages.lock.json
Updated versions and content hashes for nanoFramework packages, specifically Button, Gpio, I2c, Spi, and others.
nanoFramework.AtomLite/packages.lock.json
nanoFramework.AtomMatrix/packages.lock.json
nanoFramework.Fire/packages.lock.json
nanoFramework.M5Core/packages.lock.json
nanoFramework.M5Core2/packages.lock.json
nanoFramework.M5StickC/packages.lock.json
nanoFramework.M5StickCPlus/packages.lock.json
nanoFramework.Tough/packages.lock.json
Updated versions and content hashes for nanoFramework packages, including Axp192, Bmm150, Button, Gpio, I2c, Spi, and others.

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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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 as 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 resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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: 1

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 2e54ea9 and 5ec60a3.

Files ignored due to path filters (38)
  • 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.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 (15)
  • Tests/AtomLiteTestApp/packages.lock.json (2 hunks)
  • Tests/AtomMatrixTestApp/packages.lock.json (2 hunks)
  • Tests/FireTestApp/packages.lock.json (3 hunks)
  • Tests/M5Core2TestApp/packages.lock.json (3 hunks)
  • Tests/M5CoreTestApp/packages.lock.json (3 hunks)
  • Tests/M5StickTestApp/packages.lock.json (2 hunks)
  • Tests/ToughTestApp/packages.lock.json (2 hunks)
  • nanoFramework.AtomLite/packages.lock.json (3 hunks)
  • nanoFramework.AtomMatrix/packages.lock.json (3 hunks)
  • nanoFramework.Fire/packages.lock.json (3 hunks)
  • nanoFramework.M5Core/packages.lock.json (3 hunks)
  • nanoFramework.M5Core2/packages.lock.json (3 hunks)
  • nanoFramework.M5StickC/packages.lock.json (2 hunks)
  • nanoFramework.M5StickCPlus/packages.lock.json (2 hunks)
  • nanoFramework.Tough/packages.lock.json (3 hunks)
Files skipped from review due to trivial changes (6)
  • Tests/AtomLiteTestApp/packages.lock.json
  • Tests/AtomMatrixTestApp/packages.lock.json
  • Tests/FireTestApp/packages.lock.json
  • Tests/ToughTestApp/packages.lock.json
  • nanoFramework.M5Core2/packages.lock.json
  • nanoFramework.Tough/packages.lock.json
Additional comments not posted (33)
nanoFramework.AtomLite/packages.lock.json (3)

31-33: Update to nanoFramework.Iot.Device.Button version 1.2.560 is correctly reflected with the appropriate content hash.


61-63: Update to nanoFramework.System.Device.Gpio version 1.1.41 is correctly reflected with the appropriate content hash.


73-75: Update to nanoFramework.System.Device.Spi version 1.3.52 is correctly reflected with the appropriate content hash.

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

31-33: Update to nanoFramework.Iot.Device.Button version 1.2.560 is correctly reflected with the appropriate content hash.


73-75: Update to nanoFramework.System.Device.Gpio version 1.1.41 is correctly reflected with the appropriate content hash.


91-93: Update to nanoFramework.System.Device.Spi version 1.3.52 is correctly reflected with the appropriate content hash.

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

31-33: Update to nanoFramework.Iot.Device.Axp192 version 1.2.560 is correctly reflected with the appropriate content hash.


37-39: Update to nanoFramework.Iot.Device.Button version 1.2.560 is correctly reflected with the appropriate content hash.


91-93: Update to nanoFramework.System.Device.Gpio version 1.1.41 is correctly reflected with the appropriate content hash.

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

31-33: Update to nanoFramework.Iot.Device.Axp192 version 1.2.560 is correctly reflected with the appropriate content hash.


37-39: Update to nanoFramework.Iot.Device.Button version 1.2.560 is correctly reflected with the appropriate content hash.


91-93: Update to nanoFramework.System.Device.Gpio version 1.1.41 is correctly reflected with the appropriate content hash.

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

19-21: Update to nanoFramework.Iot.Device.Bmm150 version 1.2.560 is correctly reflected with the appropriate content hash.


25-27: Update to nanoFramework.Iot.Device.Button version 1.2.560 is correctly reflected with the appropriate content hash.


85-87: Update to nanoFramework.System.Device.Gpio version 1.1.41 is correctly reflected with the appropriate content hash.


109-111: Update to nanoFramework.System.Device.Spi version 1.3.52 is correctly reflected with the appropriate content hash.

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

31-33: Version and content hash update for nanoFramework.Iot.Device.Axp192 are correct and consistent with the PR objectives.


37-39: Version and content hash update for nanoFramework.Iot.Device.Button are correct and consistent with the PR objectives.


97-99: Version and content hash update for nanoFramework.System.Device.Gpio are correct and consistent with the PR objectives.


97-99: Version update for nanoFramework.System.Device.Spi is correct and consistent with the PR objectives. Please ensure the content hash is also updated accordingly.

Verification successful

The content hash for all dependencies in the packages.lock.json files is consistently null, indicating that this might be the expected state for these files. Therefore, the absence of a non-null contentHash for nanoFramework.System.Device.Spi is not an issue.

Scripts executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify the content hash for `nanoFramework.System.Device.Spi` is updated.

# Test: Search for the content hash in the file. Expect: Updated content hash.
rg --type json $'nanoFramework.System.Device.Spi'

Length of output: 795



Script:

#!/bin/bash
# Description: Extract and compare the content hash for `nanoFramework.System.Device.Spi` in the relevant `packages.lock.json` files.

# Extract the content hash for `nanoFramework.System.Device.Spi` from each `packages.lock.json` file.
for file in $(rg --files-with-matches 'nanoFramework.System.Device.Spi' --type json); do
  echo "File: $file"
  jq -r '.dependencies["nanoFramework.System.Device.Spi"].contentHash' "$file"
done

Length of output: 2806



Script:

#!/bin/bash
# Description: Check the presence of the `contentHash` field for other dependencies in the same `packages.lock.json` files.

# Extract the content hash for other dependencies from each `packages.lock.json` file.
for file in $(rg --files-with-matches 'nanoFramework.System.Device.Spi' --type json); do
  echo "File: $file"
  jq -r '.dependencies | to_entries[] | select(.key != "nanoFramework.System.Device.Spi") | .value.contentHash' "$file"
done

Length of output: 3175

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

25-27: The version and content hash for nanoFramework.Iot.Device.Bmm150 have been updated correctly to 1.2.560.


31-33: The version and content hash for nanoFramework.Iot.Device.Button have been updated correctly to 1.2.560.


97-99: The version and content hash for nanoFramework.System.Device.Gpio have been updated correctly to 1.1.41.


121-123: The version and content hash for nanoFramework.System.Device.Spi have been updated correctly to 1.3.52.

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

37-39: The version and content hash for nanoFramework.Iot.Device.Bmm150 have been updated correctly to 1.2.560.


43-45: The version and content hash for nanoFramework.Iot.Device.Button have been updated correctly to 1.2.560.


115-117: The version and content hash for nanoFramework.System.Device.Gpio have been updated correctly to 1.1.41.


139-141: The version and content hash for nanoFramework.System.Device.Spi have been updated correctly to 1.3.52.

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

25-27: The version and content hash for nanoFramework.Iot.Device.Axp192 have been updated correctly to 1.2.560.


31-33: The version and content hash for nanoFramework.Iot.Device.Bmm150 have been updated correctly to 1.2.560.


37-39: The version and content hash for nanoFramework.Iot.Device.Button have been updated correctly to 1.2.560.


103-105: The version and content hash for nanoFramework.System.Device.Gpio have been updated correctly to 1.1.41.


127-129: The version and content hash for nanoFramework.System.Device.Spi have been updated correctly to 1.3.52.

Comment on lines +97 to +99
"requested": "[1.1.41, 1.1.41]",
"resolved": "1.1.41",
"contentHash": "5QnpdfvjxOvka2S5IHSdKudWmkH+CDQ3TFFuXOGuNlgZJFsAx0/k5zuwgJYkxIyGbL8kdcjBWLyDNdihjA1pUg=="
Copy link

Choose a reason for hiding this comment

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

Tip

Codebase Verification

The content hash for nanoFramework.Iot.Device.Bmm150 is null in all relevant packages.lock.json files. This indicates a potential issue with the dependency resolution or lock file generation.

  • nanoFramework.M5Core2/packages.lock.json
  • nanoFramework.Fire/packages.lock.json
  • nanoFramework.M5Core/packages.lock.json
  • Tests/FireTestApp/packages.lock.json
  • Tests/M5CoreTestApp/packages.lock.json
  • Tests/M5Core2TestApp/packages.lock.json

Please investigate and ensure that the dependency is correctly resolved and the content hash is properly generated.

Analysis chain

Version update for nanoFramework.Iot.Device.Bmm150 is correct and consistent with the PR objectives. Please ensure the content hash is also updated accordingly.

Scripts executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify the content hash for `nanoFramework.Iot.Device.Bmm150` is updated.

# Test: Search for the content hash in the file. Expect: Updated content hash.
rg --type json $'nanoFramework.Iot.Device.Bmm150'

Length of output: 541



Script:

#!/bin/bash
# Description: Verify the content hash for `nanoFramework.Iot.Device.Bmm150` is updated in all relevant packages.lock.json files.

# Extract and display the content hash for `nanoFramework.Iot.Device.Bmm150` in each packages.lock.json file.
for file in $(rg --files-with-matches --type json $'nanoFramework.Iot.Device.Bmm150'); do
  echo "File: $file"
  jq -r '.dependencies["nanoFramework.Iot.Device.Bmm150"].contentHash' "$file"
done

Length of output: 1879

Copy link

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@nfbot nfbot merged commit d79ebfe into main May 31, 2024
5 checks passed
@nfbot nfbot deleted the nfbot/update-dependencies/a12bed33-b445-4396-a157-2d6c22a95b8e branch May 31, 2024 03:36
This was referenced Sep 27, 2024
This was referenced Oct 11, 2024
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