Update 1 NuGet dependencies

[nfbot]

Bumps nanoFramework.Iot.Device.Common.GnssDevice from 1.0.88 to 1.0.110

[version update]

⚠️ This is an automated update. ⚠️

Summary by CodeRabbit

• Chores
  • Updated dependency version for nanoFramework.Iot.Device.Common.GnssDevice from 1.0.88 to 1.0.110

[coderabbitai]

Walkthrough

This pull request updates the packages.lock.json file for the AtModem device, specifically upgrading the nanoFramework.Iot.Device.Common.GnssDevice dependency from version 1.0.88 to 1.0.110. The change involves updating the version-related fields in the lock file, ensuring the project uses the newer version of the GNSS device dependency while maintaining the integrity of other package dependencies.

Changes

File	Change Summary
devices/AtModem/packages.lock.json	Updated nanoFramework.Iot.Device.Common.GnssDevice dependency from 1.0.88 to 1.0.110

Possibly related PRs

• Update 1 NuGet dependencies #1152: Updates the same nanoFramework.Iot.Device.Common.GnssDevice dependency from 1.0.43 to 1.0.48
• Update 2 NuGet dependencies #1170: Continues the dependency version progression by updating from 1.0.48 to 1.0.65

---

📜 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 0b2c6c8 and 9e543b6.

⛔ Files ignored due to path filters (5)

• devices/AtModem/AtModem.nfproj is excluded by none and included by none
• devices/AtModem/AtModem.nuspec is excluded by none and included by none
• devices/AtModem/packages.config is excluded by none and included by none
• devices/AtModem/samples/AtModem.Sample.nfproj is excluded by none and included by none
• devices/AtModem/samples/packages.config is excluded by none and included by none

📒 Files selected for processing (1)

• devices/AtModem/packages.lock.json (1 hunks)

🔇 Additional comments (1)

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

13-15: LGTM! Version update is consistent and properly formatted.

The dependency update for nanoFramework.Iot.Device.Common.GnssDevice is correctly specified:

• Version range is properly formatted as exact version: [1.0.110, 1.0.110]
• Resolved version matches the requested version: 1.0.110
• ContentHash is updated accordingly

Let's verify this is the latest stable version:

✅ Verification successful

Version update is safe and up-to-date

The update to version 1.0.110 of nanoFramework.Iot.Device.Common.GnssDevice is verified to be:

• The latest available stable version in the NuGet feed
• Free from any known security vulnerabilities
• Properly specified in the lock file with consistent version numbers

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the latest stable version of nanoFramework.Iot.Device.Common.GnssDevice
# and check for any recent security advisories

# Check NuGet feed for latest versions
curl -s https://api.nuget.org/v3-flatcontainer/nanoframework.iot.device.common.gnssdevice/index.json | jq '.versions[]' | sort -V

# Check for security advisories
gh api graphql -f query='
{
  securityVulnerabilities(first: 5, ecosystem: NUGET, package: "nanoFramework.Iot.Device.Common.GnssDevice") {
    nodes {
      advisory {
        summary
        severity
        publishedAt
      }
      vulnerableVersionRange
      firstPatchedVersion {
        identifier
      }
    }
  }
}'

Length of output: 615

---

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.