Repository navigation
V5.0.14/service update - #63
Conversation
 [Medium impact] The PR reaches dependency use across the library and its release workflow. The PR still needs the service-update version check fixed before merging.
 |
Aligns shared test, data access, messaging, and Cuemon dependencies with their latest stable releases, including the EF Core 9 and 10 patch lines, so the service update ships on current baselines.
Copilot instructions duplicated the test and benchmark rules that agents read from AGENTS.md. Folding them into AGENTS.md with explicit path scopes leaves one source of truth, so the references in .bot/README.md now point only to AGENTS.md.
The published documentation site moved to savvyio.codebelt.net, so the sitemap base URL must match the live host for search engines to index the correct canonical URLs.
Records the 5.0.14 dependency updates, the sitemap host change, and the consolidated agent guidance so readers see what the patch release contains.
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #63 +/- ##
==========================================
+ Coverage 98.62% 98.70% +0.08%
==========================================
Files 177 177
Lines 3783 3643 -140
Branches 365 327 -38
==========================================
- Hits 3731 3596 -135
+ Misses 50 46 -4
+ Partials 2 1 -1 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
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:
For more information about GitHub Code Scanning, check out the documentation. |
Resolve the service update version from the latest stable Git tag and cross-check it against CHANGELOG.md, so the automation fails fast instead of branching and rewriting the changelog from an inconsistent release state.
Add explicit System.Security.Cryptography.Pkcs pins for the net9 and net10 groups so both target frameworks resolve the patched package version instead of the vulnerable transitive one.
| 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": |
There was a problem hiding this comment.
The new check rejects a dated release that has not been tagged yet. With the latest tag v5.0.12 and this PR's CHANGELOG.md heading [5.0.13] - 2026-10-18, neither branch matches. The next service update exits before updating packages or opening a PR.
The changelog writer also creates this state by replacing TBD with today's date. Allow a dated next release while its tag is pending, or keep it TBD until tagging.
Prompt To Fix With AI
This is a comment left during a code review.
Path: .github/workflows/service-update.yml
Line: 86-89
Comment:
**Dated releases block service updates**
The new check rejects a dated release that has not been tagged yet. With the latest tag `v5.0.12` and this PR's `CHANGELOG.md` heading `[5.0.13] - 2026-10-18`, neither branch matches. The next service update exits before updating packages or opening a PR.
The changelog writer also creates this state by replacing `TBD` with today's date. Allow a dated next release while its tag is pending, or keep it `TBD` until tagging.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.
The 5.0.14 header was set before the release existed, while CHANGELOG.md still lists 5.0.13 as the newest released section. Realigning every package's notes keeps them matching the version actually shipped until the service-update automation bumps them.
|
3 participants
This is a service update that focuses on package dependencies.
Automated changes:
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: yamldotnet @ 10.1.9