Skip to content

Update 7 NuGet dependencies #227

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Mar 13, 2025
Merged

Update 7 NuGet dependencies #227

merged 1 commit into from
Mar 13, 2025

Conversation

@nfbot
Copy link
Member

@nfbot nfbot commented Mar 13, 2025 •
edited by coderabbitai bot
Loading

Bumps nanoFramework.Hardware.Esp32 from 1.6.32 to 1.6.33
Bumps nanoFramework.Iot.Device.Button from 1.2.822 to 1.2.852
Bumps nanoFramework.Iot.Device.Buzzer from 1.2.846 to 1.2.852
Bumps nanoFramework.Iot.Device.DCMotor from 1.2.822 to 1.2.852
Bumps nanoFramework.Iot.Device.ServoMotor from 1.2.822 to 1.2.852
Bumps nanoFramework.Iot.Device.Ssd13xx from 1.3.636 to 1.3.666
Bumps UnitsNet.nanoFramework.Frequency from 5.71.0 to 5.73.0

[version update]

⚠️ This is an automated update. ⚠️

Summary by CodeRabbit

  • Chores
    • Updated underlying dependency versions to leverage improved stability and performance throughout the system. These enhancements pave the way for a more reliable user experience without any noticeable changes to the interface.

@nfbot
Update 7 NuGet dependencies
eb12547 
Bumps nanoFramework.Hardware.Esp32 from 1.6.32 to 1.6.33</br>Bumps nanoFramework.Iot.Device.Button from 1.2.822 to 1.2.852</br>Bumps nanoFramework.Iot.Device.Buzzer from 1.2.846 to 1.2.852</br>Bumps nanoFramework.Iot.Device.DCMotor from 1.2.822 to 1.2.852</br>Bumps nanoFramework.Iot.Device.ServoMotor from 1.2.822 to 1.2.852</br>Bumps nanoFramework.Iot.Device.Ssd13xx from 1.3.636 to 1.3.666</br>Bumps UnitsNet.nanoFramework.Frequency from 5.71.0 to 5.73.0</br>
[version update]

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

coderabbitai bot commented Mar 13, 2025 •
edited
Loading

Walkthrough

The changes update dependency versions across two projects. In both the Tests/MagicBitTestApp and nanoFramework.MagicBit projects, multiple nanoFramework Iot Device packages (Button, Buzzer, DCMotor, ServoMotor, Ssd13xx) and the UnitsNet.nanoFramework.Frequency package have their requested and resolved versions updated along with new content hashes. Additionally, the nanoFramework.MagicBit project updates the nanoFramework.Hardware.Esp32 package version.

Changes

File Path Change Summary
Tests/MagicBitTestApp/.../packages.lock.json Updated versions for:
• nanoFramework.Iot.Device.Button from 1.2.822 → 1.2.852
• nanoFramework.Iot.Device.Buzzer from 1.2.846 → 1.2.852
• nanoFramework.Iot.Device.DCMotor from 1.2.822 → 1.2.852
• nanoFramework.Iot.Device.ServoMotor from 1.2.822 → 1.2.852
• nanoFramework.Iot.Device.Ssd13xx from 1.3.636 → 1.3.666
• UnitsNet.nanoFramework.Frequency from 5.71.0 → 5.73.0
nanoFramework.MagicBit/.../packages.lock.json Updated versions for:
• nanoFramework.Hardware.Esp32 from 1.6.32 → 1.6.33
• nanoFramework.Iot.Device.Button from 1.2.822 → 1.2.852
• nanoFramework.Iot.Device.Buzzer from 1.2.846 → 1.2.852
• nanoFramework.Iot.Device.DCMotor from 1.2.822 → 1.2.852
• nanoFramework.Iot.Device.ServoMotor from 1.2.822 → 1.2.852
• nanoFramework.Iot.Device.Ssd13xx from 1.3.636 → 1.3.666
• UnitsNet.nanoFramework.Frequency from 5.71.0 → 5.73.0

Possibly related PRs

Suggested labels

CI: Publish Release

Tip

⚡🧪 Multi-step agentic review comment chat (experimental)
  • We're introducing multi-step agentic chat in review comments. This experimental feature enhances review discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments.
    - To enable this feature, set early_access to true under in the settings.
📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 4021032 and eb12547.

⛔ Files ignored due to path filters (5)
  • Tests/MagicBitTestApp/MagicBitTestApp.nfproj is excluded by none and included by none
  • Tests/MagicBitTestApp/packages.config is excluded by none and included by none
  • nanoFramework.MagicBit.nuspec is excluded by none and included by none
  • nanoFramework.MagicBit/nanoFramework.MagicBit.nfproj is excluded by none and included by none
  • nanoFramework.MagicBit/packages.config is excluded by none and included by none
📒 Files selected for processing (2)
  • Tests/MagicBitTestApp/packages.lock.json (2 hunks)
  • nanoFramework.MagicBit/packages.lock.json (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: nanoFramework / NuGets using latest version
🔇 Additional comments (13)
Tests/MagicBitTestApp/packages.lock.json (6)

13-15: Dependency Update – nanoFramework.Iot.Device.Button
The requested version has been updated from 1.2.822 to 1.2.852 and the content hash has been adjusted accordingly. This change appears consistent with the coordinated update strategy.

19-21: Dependency Update – nanoFramework.Iot.Device.Buzzer
The package version has been updated from 1.2.846 to 1.2.852 with the corresponding content hash update. Ensure that downstream consumers are compatible with this new version.

25-27: Dependency Update – nanoFramework.Iot.Device.DCMotor
The update changes the version from 1.2.822 to 1.2.852 and updates the content hash. This looks correct—please confirm with integration tests that rely on this dependency.

31-33: Dependency Update – nanoFramework.Iot.Device.ServoMotor
The version update from 1.2.822 to 1.2.852 (with an updated content hash) aligns with the overall dependency upgrade. Verify that no API-breaking changes affect the project.

37-39: Dependency Update – nanoFramework.Iot.Device.Ssd13xx
The dependency has been updated from version 1.3.636 to 1.3.666 with a new content hash. Please confirm that the device functionalities remain intact with this update.

91-93: Dependency Update – UnitsNet.nanoFramework.Frequency
The version has been changed from 5.71.0 to 5.73.0 and the content hash has been updated accordingly. This update is consistent and appears correct; ensure that tests reflect compatibility with this new version.

nanoFramework.MagicBit/packages.lock.json (7)

13-15: Dependency Update – nanoFramework.Hardware.Esp32
The dependency has been updated from version 1.6.32 to 1.6.33 with a new content hash. This change should be verified against your hardware integration tests to ensure smooth operation.

19-21: Dependency Update – nanoFramework.Iot.Device.Button
The version bump to 1.2.852 with an updated content hash is consistent with similar changes in related projects. No issues noted.

25-27: Dependency Update – nanoFramework.Iot.Device.Buzzer
The update from 1.2.846 to 1.2.852, including the revised content hash, aligns with the overall dependency refresh. Please verify integration scenarios as needed.

31-33: Dependency Update – nanoFramework.Iot.Device.DCMotor
The dependency version has been updated to 1.2.852 with a corresponding content hash change. This update appears standard; ensure that any binary dependencies or API expectations are met.

37-39: Dependency Update – nanoFramework.Iot.Device.ServoMotor
The updated version 1.2.852 (with an updated content hash) is in line with the other Iot Device packages. Confirm that API changes (if any) are properly handled in the codebase.

43-45: Dependency Update – nanoFramework.Iot.Device.Ssd13xx
The update from version 1.3.636 to 1.3.666, along with the new content hash, appears consistent. It is recommended to run any device-specific tests to ensure continued functionality.

97-99: Dependency Update – UnitsNet.nanoFramework.Frequency
The dependency version change to 5.73.0 with its updated content hash maintains consistency across projects. Validate that consumers of this package work as expected.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

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

@nfbot nfbot merged commit 9484089 into main Mar 13, 2025
6 checks passed
@nfbot nfbot deleted the nfbot/update-dependencies/32eab58c-fe87-429d-bab0-9ccdd0526d49 branch March 13, 2025 01:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

CI: Publish Release Type: dependencies

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@nfbot