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.

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

Update 2 NuGet dependencies #199

Closed
wants to merge 1 commit into from
Closed

Update 2 NuGet dependencies #199

wants to merge 1 commit into from

Conversation

nfbot
Copy link
Member

@nfbot nfbot commented Jan 31, 2025 •
edited by coderabbitai bot
Loading

Bumps nanoFramework.Benchmark from 1.0.89 to 1.0.91
Bumps nanoFramework.System.Diagnostics.Stopwatch from 1.2.693 to 1.2.751

[version update]

⚠️ This is an automated update. ⚠️

Summary by CodeRabbit

  • Chores
    • Updated dependency versions:
      • nanoFramework.Benchmark upgraded to version 1.0.91
      • nanoFramework.System.Diagnostics.Stopwatch upgraded to version 1.2.751

@nfbot
Update 2 NuGet dependencies
bbf7912 
Bumps nanoFramework.Benchmark from 1.0.89 to 1.0.91</br>Bumps nanoFramework.System.Diagnostics.Stopwatch from 1.2.693 to 1.2.751</br>
[version update]

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

coderabbitai bot commented Jan 31, 2025 •
edited
Loading

Walkthrough

This pull request involves updating dependency versions in the packages.lock.json file for the nanoFramework.System.Text.Benchmark project. Specifically, two dependencies have been updated: nanoFramework.Benchmark is upgraded from version 1.0.89 to 1.0.91, and nanoFramework.System.Diagnostics.Stopwatch is updated from 1.2.693 to 1.2.751. The other dependencies remain unchanged, and the modifications are limited to version and content hash updates.

Changes

File Change Summary
nanoFramework.System.Text.Benchmark/packages.lock.json - Updated nanoFramework.Benchmark from 1.0.89 to 1.0.91
- Updated nanoFramework.System.Diagnostics.Stopwatch from 1.2.693 to 1.2.751

Possibly related PRs

📜 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 aa79f14 and bbf7912.

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

7-9: LGTM!

The version update for nanoFramework.Benchmark from 1.0.89 to 1.0.91 is consistent with the PR objectives. The version is correctly pinned and the content hash has been updated accordingly.

37-39: LGTM!

The version update for nanoFramework.System.Diagnostics.Stopwatch from 1.2.693 to 1.2.751 is consistent with the PR objectives. The version is correctly pinned and the content hash has been updated accordingly.

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.

@josesimoes
Copy link
Member

@nfbot updatedependencies

@sonarqubecloud SonarQubeCloud
Copy link

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

@nfbot nfbot closed this Jan 31, 2025
@nfbot nfbot deleted the nfbot/update-dependencies/f03d1e8d-0867-4cd0-9efd-fce82fc82497 branch January 31, 2025 13:47
@nfbot nfbot added invalid This doesn't seem right and removed Type: dependencies labels Jan 31, 2025
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
invalid This doesn't seem right
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@nfbot @josesimoes