Skip to content

V5.2.3/service update - #38

Merged
gimlichael merged 9 commits into
mainfrom
v5.2.3/service-update
Oct 18, 2026
Merged

gimlichael merged 9 commits into
mainfrom
v5.2.3/service-update

Conversation

@codebelt-aicia

Copy link
Copy Markdown
Contributor

This is a service update that focuses on package dependencies.

Automated changes:

  • Codebelt/Cuemon package versions bumped to latest compatible
  • PackageReleaseNotes.txt updated for v5.2.3
  • CHANGELOG.md entry added for v5.2.3

Note: Third-party packages (Microsoft.Extensions.*, BenchmarkDotNet, etc.) are not auto-updated.
Use Dependabot or manual updates for those.

Generated by codebelt-aicia
Triggered by: swashbuckle-aspnetcore @ 10.3.0

@greptile-apps

greptile-apps Bot commented Oct 18, 2026 •

Copy link
Copy Markdown

RetriggerView in GreptileConfidence Score: 4/5

[Medium impact] The changes reach shared project dependencies, documentation publishing, and release automation.

The PR still needs the version check fixed before merging because dependency updates can fail before the release is tagged.

Fix All in CodexFindings

  1. P1 Updates fail before release tagging ▶
Fix with agent prompt
### Issue 1
.github/workflows/service-update.yml:86-89
If another dependency update runs after this PR merges but before `v5.2.3` is tagged, the dated `5.2.3` heading fails both allowed branches. The workflow exits before updating packages or opening a PR. Its own changelog writer creates this dated-but-untagged state.

Allow the pending next version with a date too, or keep it marked `TBD` until release.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

This service update refreshes dependencies, documentation hosting, and contributor guidance.

  • Shared packages use updated dependencies and test tools.
  • The DocFX site uses a new nginx setup and documentation layout.
  • Service updates choose their release number from stable Git tags.
  • Contributor guidance now lives in AGENTS.md.

Reviews (3) · Last reviewed commit: "🔧 stop caching missing docfx assets" · Reviewed by Greptile

Test, benchmark, and XML documentation guidance now lives in AGENTS.md so agents read one source of truth. The separate copilot-instructions file is retired and references point to AGENTS.md.
The DocFX image now uses DHI nginx and copies a dedicated nginx configuration. Fingerprinted DocFX assets are cached immutably, while pages and navigation data keep stable URLs without stale validators.
API members now render on separate pages, the Microsoft-style template is included, and a monthly sitemap is generated for the published site.
The service update workflow now reads the latest stable Git tag instead of the changelog heading. It reuses a pending TBD release and updates an existing matching changelog section rather than duplicating it.
Shared test projects now use Codebelt.Coverlet.MTP and Microsoft.Testing.Extensions.HangDump instead of the CodeCoverage package. Test SDK, xUnit, and .NET 9 and 10 framework baselines move to their latest stable releases.
The per-project test loop passes the test project through the --project option so each project runs on its own.
The 5.2.3 changelog entry now lists the dependency, DocFX hosting, and contributor guidance changes that shipped in this service update, and the Unreleased section is folded into the versioned release.
Comment on lines +86 to +89
if current_version == next_version and current_status.upper() == "TBD":
# Reuse an already pending next release, such as [5.0.13] - TBD.
new_version = next_version
elif current_version == latest_version and current_status.upper() != "TBD":

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Updates fail before release tagging

If another dependency update runs after this PR merges but before v5.2.3 is tagged, the dated 5.2.3 heading fails both allowed branches. The workflow exits before updating packages or opening a PR. Its own changelog writer creates this dated-but-untagged state.

Allow the pending next version with a date too, or keep it marked TBD until release.

Prompt To Fix With AI
This is a comment left during a code review.
Path: .github/workflows/service-update.yml
Line: 86-89

Comment:
**Updates fail before release tagging**

If another dependency update runs after this PR merges but before `v5.2.3` is tagged, the dated `5.2.3` heading fails both allowed branches. The workflow exits before updating packages or opening a PR. Its own changelog writer creates this dated-but-untagged state.

Allow the pending next version with a date too, or keep it marked `TBD` until release.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Fix in Codex

Comment thread .docfx/nginx.conf Outdated
Missing fingerprinted DocFX assets were returned with the immutable one-year cache policy, so clients could keep a 404 cached for a year. Route those misses through a no-store error location and keep the immutable policy only for successful responses.
@codecov

codecov Bot commented Oct 18, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (1f08b10) to head (bf697b9).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #38   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           22        22           
  Lines          308       300    -8     
  Branches        29        24    -5     
=========================================
- Hits           308       300    -8     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@sonarqubecloud

Copy link
Copy Markdown

@github-advanced-security

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

@gimlichael
gimlichael merged commit e014e39 into main Oct 18, 2026
26 checks passed
@gimlichael
gimlichael deleted the v5.2.3/service-update branch October 18, 2026 18:49
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.

3 participants