Release MLVScan 2.1.3 with Core 1.8.0

[ifBars]

Summary

• bump the loader release to 2.1.3
• pin MLVScan.Core to the published 1.8.0 package instead of a floating version

Validation

Built against the public MLVScan.Core 1.8.0 NuGet package:

• MelonLoader
• BepInEx 5
• BepInEx 6 Mono
• BepInEx 6 IL2CPP

All four builds completed successfully and ILRepack consumed the 1.8.0 package path.

• Release MLVScan version 2.1.3.
• Pin MLVScan.Core to NuGet package version 1.8.0.
• Validate MelonLoader, BepInEx 5, BepInEx 6 Mono, and BepInEx 6 IL2CPP builds.
• Confirm ILRepack uses the 1.8.0 package for all builds.

Author	Lines added	Lines removed
Not available	2	2

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: c206dff0-aeee-4234-904f-8915153948f4

📥 Commits

Reviewing files that changed from the base of the PR and between af39b15 and 7ca6308.

📒 Files selected for processing (1)

• MLVScan.csproj

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The project version changed from 2.1.2 to 2.1.3. The non-local MLVScan.Core package reference changed from wildcard versioning to 1.8.0.

Changes

Project Metadata

Layer / File(s)	Summary
Version and dependency updates MLVScan.csproj	The project version is now 2.1.3. The non-local MLVScan.Core package reference is pinned to 1.8.0; the local project reference remains unchanged.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 7ca63

This localized release change updates the version and pins the Core dependency to 1.8.0; no actionable merge-blocking risk remains after normal checks and review.

Poem

A rabbit sees the version hop
From two-one-two to two-one-three atop
Core is pinned at one-eight-zero
The project file stays neat and clear
Soft paws approve the change this year

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title is concise, uses plain English, stays under 50 characters, and accurately describes the release and dependency update.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/loader-2.1.3

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}