Manual Dependency Update for all projects#431
Conversation
|
Warning Review limit reached
More reviews will be available in 29 minutes and 51 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Repository: nanoframework/coderabbit/.coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (9)
📝 WalkthroughWalkthroughBumps five nanoFramework NuGet package versions across all library and test projects by updating ChangesNuGet Package Version Bumps
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. 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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@nanoFramework.M5Core/packages.lock.json`:
- Around line 13-15: The package lock is already updated, but the nuspec
manifests still pin nanoFramework.Graphics and nanoFramework.Graphics.Core to
the older 1.2.45 versions. Update the dependency versions in
nanoFramework.M5Core.nuspec, nanoFramework.M5Core2.nuspec,
nanoFramework.M5StickC.nuspec, nanoFramework.M5StickCPlus.nuspec,
nanoFramework.Fire.nuspec, nanoFramework.Tough.nuspec, and
nanoFramework.CoreInk.nuspec to match the new package versions used by the
lockfile, using the existing package dependency entries in each nuspec as the
reference points.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository: nanoframework/coderabbit/.coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: 7f20326a-57c5-44b8-be64-6b9f7fd919e7
📒 Files selected for processing (48)
Tests/AtomLiteTestApp/AtomLiteTestApp.nfprojTests/AtomLiteTestApp/packages.configTests/AtomLiteTestApp/packages.lock.jsonTests/AtomMatrixTestApp/AtomMatrixTestApp.nfprojTests/AtomMatrixTestApp/packages.configTests/AtomMatrixTestApp/packages.lock.jsonTests/FireTestApp/FireTestApp.nfprojTests/FireTestApp/packages.configTests/FireTestApp/packages.lock.jsonTests/M5Core2TestApp/M5Core2TestApp.nfprojTests/M5Core2TestApp/packages.configTests/M5Core2TestApp/packages.lock.jsonTests/M5CoreTestApp/M5CoreTestApp.nfprojTests/M5CoreTestApp/packages.configTests/M5CoreTestApp/packages.lock.jsonTests/M5StickTestApp/M5StickTestApp.nfprojTests/M5StickTestApp/packages.configTests/M5StickTestApp/packages.lock.jsonTests/ToughTestApp/ToughTestApp.nfprojTests/ToughTestApp/packages.configTests/ToughTestApp/packages.lock.jsonnanoFramework.AtomLite/nanoFramework.AtomLite.nfprojnanoFramework.AtomLite/packages.confignanoFramework.AtomLite/packages.lock.jsonnanoFramework.AtomMatrix/nanoFramework.AtomMatrix.nfprojnanoFramework.AtomMatrix/packages.confignanoFramework.AtomMatrix/packages.lock.jsonnanoFramework.CoreInk/nanoFramework.CoreInk.nfprojnanoFramework.CoreInk/packages.confignanoFramework.CoreInk/packages.lock.jsonnanoFramework.Fire/nanoFramework.Fire.nfprojnanoFramework.Fire/packages.confignanoFramework.Fire/packages.lock.jsonnanoFramework.M5Core/nanoFramework.M5Core.nfprojnanoFramework.M5Core/packages.confignanoFramework.M5Core/packages.lock.jsonnanoFramework.M5Core2/nanoFramework.M5Core2.nfprojnanoFramework.M5Core2/packages.confignanoFramework.M5Core2/packages.lock.jsonnanoFramework.M5StickC/nanoFramework.M5StickC.nfprojnanoFramework.M5StickC/packages.confignanoFramework.M5StickC/packages.lock.jsonnanoFramework.M5StickCPlus/nanoFramework.M5StickCPlus.nfprojnanoFramework.M5StickCPlus/packages.confignanoFramework.M5StickCPlus/packages.lock.jsonnanoFramework.Tough/nanoFramework.Tough.nfprojnanoFramework.Tough/packages.confignanoFramework.Tough/packages.lock.json
|
2 participants
Description
Manual Dependency Update for all projects
Motivation and Context
How Has This Been Tested?
Screenshots
Types of changes
Checklist: