Skip to content

global sdk update#65

Merged
yilmaztayfun merged 1 commit into
masterfrom
60-enhancement-add-opentelemetry-tracing-spans-to-distributed-event-bus-pipeline
May 18, 2026
Merged

global sdk update#65
yilmaztayfun merged 1 commit into
masterfrom
60-enhancement-add-opentelemetry-tracing-spans-to-distributed-event-bus-pipeline

Conversation

@yilmaztayfun

@yilmaztayfun yilmaztayfun commented May 18, 2026

Copy link
Copy Markdown
Contributor

Summary by Sourcery

Update .NET SDK configuration and align the SonarCloud CI workflow with the new SDK usage.

Build:

  • Update global.json to use .NET SDK version 10.0.103.
  • Configure the SonarCloud GitHub Actions workflow to install .NET 10.0.x, restore solution dependencies, and build without restoring during analysis.

@yilmaztayfun yilmaztayfun self-assigned this May 18, 2026
@yilmaztayfun yilmaztayfun requested review from a team May 18, 2026 08:41
@sourcery-ai

sourcery-ai Bot commented May 18, 2026

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

.github workflow is updated to install .NET 10 SDK, split restore from build, and reuse restore in build with --no-restore, while global.json SDK version is bumped from 10.0.101 to 10.0.103.

File-Level Changes

Change Details Files
Configure SonarCloud GitHub Action to install .NET 10 SDK and separate restore from build.
  • Add actions/setup-dotnet@v4 step to install .NET 10.0.x SDK before Sonar scanner setup.
  • Introduce explicit dotnet restore step for framework/BBT.Aether.slnx prior to analysis build.
  • Change the build command to dotnet build ... --no-restore to rely on the dedicated restore step.
.github/workflows/check-sonar.yml
Align repository SDK pin to newer .NET 10 patch version.
  • Update global.json SDK version from 10.0.101 to 10.0.103 while keeping rollForward as latestFeature.
global.json

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@coderabbitai

coderabbitai Bot commented May 18, 2026

Copy link
Copy Markdown

Warning

Rate limit exceeded

@yilmaztayfun has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 49 minutes and 17 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 7b52baf1-3281-42a7-89c7-d6b6fcaa7477

📥 Commits

Reviewing files that changed from the base of the PR and between e34c3b8 and 782be03.

📒 Files selected for processing (2)
  • .github/workflows/check-sonar.yml
  • global.json
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch 60-enhancement-add-opentelemetry-tracing-spans-to-distributed-event-bus-pipeline

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

Comment @coderabbitai help to get the list of available commands and usage tips.

@yilmaztayfun yilmaztayfun merged commit 29511af into master May 18, 2026
5 of 6 checks passed
@codacy-production

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've left some high level feedback:

  • The workflow hardcodes dotnet-version: 10.0.x while global.json pins 10.0.103; consider configuring setup-dotnet to use global.json (or otherwise tying these together) to avoid version drift between CI and local development.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- The workflow hardcodes `dotnet-version: 10.0.x` while `global.json` pins `10.0.103`; consider configuring `setup-dotnet` to use `global.json` (or otherwise tying these together) to avoid version drift between CI and local development.

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the .NET SDK version in global.json. Feedback from the reviewer includes recommendations to align the SDK version with the feature bands of other project dependencies for compatibility, fix formatting issues such as inconsistent indentation and a missing trailing newline, and consider a more restrictive rollForward policy to ensure build reproducibility.

Comment thread global.json
{
"sdk": {
"version": "10.0.101",
"version": "10.0.103",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The SDK version 10.0.103 appears to be inconsistent with the 10.2.0 version specified for Microsoft.AspNetCore.Diagnostics.Middleware in Directory.Packages.props (line 63). Typically, using a package from a higher minor version requires a corresponding SDK feature band (e.g., 10.2.xxx). Additionally, Microsoft.SourceLink.GitHub is at 10.0.102. Consider aligning the SDK version with the highest feature band used in the project to ensure build compatibility and consistency.

Comment thread global.json
{
"sdk": {
"version": "10.0.101",
"version": "10.0.103",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The global.json file has inconsistent indentation (mixing 0, 2, 4, and 6 spaces) and is missing a trailing newline. For better maintainability and adherence to standard JSON formatting, it is recommended to use a consistent indentation (e.g., 2 spaces) throughout the file and ensure it ends with a newline character.

Comment thread global.json
{
"sdk": {
"version": "10.0.101",
"version": "10.0.103",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The rollForward policy is set to latestFeature. For better build reproducibility and to ensure all developers and CI environments use the same SDK feature band, consider using latestPatch or disable. latestFeature allows the SDK to roll forward to newer minor versions, which may introduce unexpected changes in the build process.

@sonarqubecloud

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant