Update 1 NuGet dependencies

[nfbot]

Bumps nanoFramework.Logging from 1.1.135 to 1.1.140

[version update]

⚠️ This is an automated update. ⚠️

Summary by CodeRabbit

• Chores
  • Updated the logging dependency to version 1.1.140 across multiple areas for improved dependency management.

[coderabbitai]

Walkthrough

This pull request updates the version of the nanoFramework.Logging dependency from 1.1.135 to 1.1.140 in three separate packages.lock.json files under the Card device directories. The associated content hashes have been updated to match the new dependency versions. No other dependency modifications have been made.

Changes

File(s)	Change Summary
devices/Card/Mifare/packages.lock.json devices/Card/Ultralight/packages.lock.json devices/Card/packages.lock.json	Updated nanoFramework.Logging dependency version from 1.1.135 to 1.1.140 with corresponding content hash updates. Other dependencies remain unchanged.

Possibly related PRs

• Update 61 NuGet dependencies #1247: Updates the nanoFramework.Logging dependency from 1.1.135 to 1.1.140 in the packages.lock.json files.
• Update 7 NuGet dependencies #1236: Involves a direct code-level update of nanoFramework.Logging from 1.1.135 to 1.1.140, matching the change in this PR.
• Update 28 NuGet dependencies #1265: Also updates the nanoFramework.Logging dependency version from 1.1.135 to 1.1.140 in similar configuration files.

---

📜 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 fbe0a6a and 472d2bc.

⛔ Files ignored due to path filters (7)

• devices/Card/Card.nfproj is excluded by none and included by none
• devices/Card/Card.nuspec is excluded by none and included by none
• devices/Card/Mifare/Mifare.nfproj is excluded by none and included by none
• devices/Card/Mifare/packages.config is excluded by none and included by none
• devices/Card/Ultralight/Ultralight.nfproj is excluded by none and included by none
• devices/Card/Ultralight/packages.config is excluded by none and included by none
• devices/Card/packages.config is excluded by none and included by none

📒 Files selected for processing (3)

• devices/Card/Mifare/packages.lock.json (1 hunks)
• devices/Card/Ultralight/packages.lock.json (1 hunks)
• devices/Card/packages.lock.json (1 hunks)

🔇 Additional comments (3)

devices/Card/Mifare/packages.lock.json (1)

13-15: Dependency Version Update Verified

The update for nanoFramework.Logging from version 1.1.135 to 1.1.140 is correctly applied. The new "requested", "resolved", and "contentHash" values indicate that the dependency has been updated as expected. Ensure that any components relying on this dependency are revalidated after this update.

devices/Card/Ultralight/packages.lock.json (1)

13-15: Consistent Dependency Update

The nanoFramework.Logging dependency in this file is updated consistently with the other lock files: version 1.1.140 is now in place and the content hash has been refreshed. This coordinated update helps maintain consistency across projects.

devices/Card/packages.lock.json (1)

13-15: Unified Dependency Version Update

The changes here accurately reflect the updated dependency for nanoFramework.Logging to version 1.1.140, with a matching updated content hash. This update is in line with the other files in this PR, ensuring that the project dependency remains unified.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.