Updated build versions

[mitchelsellers]

Summary by CodeRabbit

Chores

• Updated build system and continuous integration infrastructure with latest dependency versions for enhanced stability and improved performance.
• Enhanced the automated release process with refined changelog generation capabilities and improved categorization of release notes.
• Streamlined pull request processing by removing legacy configuration patterns.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Warning

Rate limit exceeded

@mitchelsellers has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 10 minutes and 9 seconds before requesting another review.

⌛ 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.

📥 Commits

Reviewing files that changed from the base of the PR and between 5789e38 and 416c5fc.

📒 Files selected for processing (2)

• .github/release.yml (1 hunks)
• .github/workflows/ci-build.yml (2 hunks)

Walkthrough

Updates CI/CD workflows and versioning configuration: adds release-drafter configuration for automated changelog generation, upgrades GitVersion actions from v3.0.0 to v4.2.0 across multiple workflows with versionSpec 6.0.5 to 6.4.0, migrates SonarQube token reference from secrets to environment variables, and removes label-number-pattern from GitVersion configuration.

Changes

Cohort / File(s)	Summary
Release Automation .github/release.yml	New release-drafter configuration with changelog categories (features, bugs, administrative, other) and excluded labels (question, wontfix, invalid).
CI/CD Workflow Updates .github/workflows/ci-build.yml, .github/workflows/release-build.yml	Upgraded GitVersion setup and execute actions from v3.0.0 to v4.2.0; updated versionSpec from 6.0.5 to 6.4.0; removed useConfigFile flag from workflow steps.
SonarQube Token Migration .github/workflows/ci-build.yml	Changed SonarQube token reference from secrets.SONAR_TOKEN to env.SONAR_TOKEN in build analysis steps.
GitVersion Configuration GitVersion.yml	Removed label-number-pattern configuration from pull-request branch settings.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

• Consistency verification: Confirm GitVersion action upgrades are uniformly applied across both CI and release workflows
• Token migration impact: Verify that environment variable substitution for SonarQube token is properly configured in CI/CD environment setup
• Compatibility validation: Ensure removal of label-number-pattern and useConfigFile flag don't break existing version determination logic
• Release configuration testing: Review release-drafter categories and label mappings for proper changelog generation

Poem

🐰 Hop, skip, through the workflows we go,
GitVersion bumps to v4—see how we grow!
Tokens now flow from the env so bright,
Release notes draft themselves just right,
Configurations cleaned with a magical touch,
CI/CD pipeline improving so much! 🚀

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Updated build versions' is overly broad and generic. While it partially relates to some changes (GitVersion and action upgrades), it misses the main changes: adding release-drafter configuration, updating CI/CD workflows, and removing GitVersion config patterns.	Consider a more specific title that captures the primary changes, such as 'Add release-drafter config and update CI/CD dependencies' or 'Update GitVersion actions and add release workflow automation'.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

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

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 47ba990 and 5789e38.

📒 Files selected for processing (4)

• .github/release.yml (1 hunks)
• .github/workflows/ci-build.yml (2 hunks)
• .github/workflows/release-build.yml (1 hunks)
• GitVersion.yml (0 hunks)

💤 Files with no reviewable changes (1)

• GitVersion.yml

🔇 Additional comments (3)

.github/workflows/release-build.yml (1)

26-26: Verify GitVersion v4.2.0 compatibility with project.

GitVersion actions are being upgraded from v3.0.0 to v4.2.0 alongside a versionSpec bump from 6.0.5 to 6.4.0. This is a major version upgrade that may introduce breaking changes or behavioral differences in version determination.

To ensure compatibility, please:

1. Verify the GitVersion v4.2.0 release notes for breaking changes relative to v3.0.0
2. Run a test build on the release branch to confirm the generated version matches expectations
3. Confirm that removing the useConfigFile flag (mentioned in the summary) does not affect version calculation given your .github/workflows/GitVersion.yml configuration

Also applies to: 28-28, 32-32

.github/workflows/ci-build.yml (2)

32-32: Verify GitVersion v4.2.0 compatibility (consistent with release-build.yml).

GitVersion actions upgraded from v3.0.0 to v4.2.0 with versionSpec 6.0.5 → 6.4.0. This mirrors the release workflow changes and carries the same compatibility verification requirements.

See the verification steps noted in the release-build.yml review comment above.

Also applies to: 34-34, 38-38

---

63-63: Verify SonarQube token environment variable is properly configured.

The SonarQube token reference has been migrated from secrets.SONAR_TOKEN to env.SONAR_TOKEN. While the env var is correctly declared at line 63, ensure that:

1. The SONAR_TOKEN secret is properly configured in your GitHub repository settings
2. The environment variable is correctly exposed to the powershell script context
3. There are no scoping or visibility issues with passing the secret through the environment

To verify this works as intended, confirm that a test CI run completes successfully with SonarQube analysis executing without authentication failures.

Also applies to: 66-66, 69-69

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud