Align StyleCop.Analyzers package version declaration across project files

[snovak7]

Closes #32

Summary by CodeRabbit

• Chores
  • Updated package management to include a new analyzer package version.
  • Adjusted project configuration to rely on centralized package versioning.

[coderabbitai]

Walkthrough

The changes update the central package management configuration by adding a specific version for "StyleCop.Analyzers.Unstable" in Directory.Packages.props and remove the explicit version from the corresponding project file, relying on the central declaration for version resolution. Additionally, centralized package version management is enabled via ManagePackageVersionsCentrally in Directory.Build.props.

Changes

Cohort / File(s)	Change Summary
Central Package Version Declaration Directory.Packages.props	Added StyleCop.Analyzers.Unstable version "1.2.0.556" to the package versions.
Central Package Management Enablement Directory.Build.props	Added <ManagePackageVersionsCentrally> property set to true to enable centralized package version management.
Project Package Reference Update src/Escendit.Tools.CodeAnalysis.StyleCopAnalyzers/Escendit.Tools.CodeAnalysis.StyleCopAnalyzers.csproj	Removed explicit version from StyleCop.Analyzers.Unstable reference to use central version.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Assessment against linked issues

Objective	Addressed	Explanation
Consolidate StyleCop.Analyzers package version management (#32)	✅

Poem

A hop and a skip, a version aligned,
Centralized numbers, no more undefined!
The StyleCop rules now dance in sync,
With props in control, no need to rethink.
🐇✨

— A rabbit who loves tidy code

Note

🔌 MCP (Model Context Protocol) integration is now available in Early Access!

Pro users can now connect to remote MCP servers under the Integrations page to get reviews and chat conversations that understand additional development context.

---

📜 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 ad6fcdc and 0475a66.

📒 Files selected for processing (1)

• Directory.Build.props (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• Directory.Build.props

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch 32-consolidate-stylecopanalyzers-package

---

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
• 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 explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @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.

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

src/Escendit.Tools.CodeAnalysis.StyleCopAnalyzers/Escendit.Tools.CodeAnalysis.StyleCopAnalyzers.csproj (1)

12-15: Confirm intended transitivity of analyzers

Current settings allow analyzers to flow transitively (PrivateAssets excludes analyzers; IncludeAssets includes analyzers; buildtransitive). If you intend to prevent transitive exposure and control it only via your buildTransitive assets, change to PrivateAssets="all". Otherwise, keep as-is.

Possible adjustment if you want to avoid transitive analyzer leakage:

-    <PackageReference Include="StyleCop.Analyzers.Unstable">
-        <PrivateAssets>runtime; build; native; contentfiles</PrivateAssets>
-        <IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
-    </PackageReference>
+    <PackageReference Include="StyleCop.Analyzers.Unstable">
+        <PrivateAssets>all</PrivateAssets>
+        <IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
+    </PackageReference>

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between aae0201 and ad6fcdc.

📒 Files selected for processing (2)

• Directory.Packages.props (1 hunks)
• src/Escendit.Tools.CodeAnalysis.StyleCopAnalyzers/Escendit.Tools.CodeAnalysis.StyleCopAnalyzers.csproj (1 hunks)

🔇 Additional comments (2)

Directory.Packages.props (1)

4-4: Centralized version pin added — LGTM

Adding StyleCop.Analyzers.Unstable 1.2.0.556 to Directory.Packages.props aligns with CPM and the PR objective to consolidate versions.

src/Escendit.Tools.CodeAnalysis.StyleCopAnalyzers/Escendit.Tools.CodeAnalysis.StyleCopAnalyzers.csproj (1)

12-15: Switched to central package version — LGTM

Removing the Version attribute here correctly defers resolution to Directory.Packages.props.