V10.8.0/options enhancement - #172
Conversation
Connect Parameter Object post-configuration and validation conventions to Microsoft Options while exposing the primary configurator and cached default options instance.
Explain how Cuemon parameter object conventions participate in Microsoft Options lifecycles and provide a consumer-ready example for the new registration method.
Record the new options registration API and its Parameter Object integration in the package release metadata.
Document the surviving API and CI workflow changes for release review.
|
Align the documented Linux CI runner baseline with the workflows.
Move pull request and downstream release workflows to the current Ubuntu runner image.
| @@ -0,0 +1,10 @@ | |||
| # .bot Workspace | |||
There was a problem hiding this comment.
This adds a tracked guide for a local-only bot workspace. The repository’s public-API documentation directive limits new working-tree files to the managed AGENTS block, active DocFX configuration, an approved waiver, or DocFX namespace and type pages. This file is outside those categories, so the repository requirement must be satisfied before merging.
Context Used: AGENTS.md (source)
Prompt To Fix With AI
This is a comment left during a code review.
Path: .bot/README.md
Line: 1
Comment:
**Tracked bot workspace guide**
This adds a tracked guide for a local-only bot workspace. The repository’s public-API documentation directive limits new working-tree files to the managed AGENTS block, active DocFX configuration, an approved waiver, or DocFX namespace and type pages. This file is outside those categories, so the repository requirement must be satisfied before merging.
**Context Used:** AGENTS.md ([source](https://github.com/codebeltnet/cuemon/blob/main/AGENTS.md))
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
Let cancellation from options validation reach the caller so canceled work is not reported as an ordinary validation failure.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #172 +/- ##
==========================================
- Coverage 94.23% 94.18% -0.05%
==========================================
Files 604 605 +1
Lines 19707 19089 -618
Branches 2103 1831 -272
==========================================
- Hits 18570 17979 -591
- Misses 1073 1083 +10
+ Partials 64 27 -37 ☔ 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. |
Run unmanaged cleanup even when managed cleanup throws, while preserving the original exception and ensuring disposal remains idempotent.
Align the shared test coverage and SQL client dependencies with their updated patch and minor releases.
Move Codecov upload to the shared reusable workflow so pull request CI uses the centralized job definition.
Record the 10.8.0 package changes and compatible dependency updates in each affected package release note.
Update the release date and summarize the shipped options integration, disposal fix, dependency updates, and workflow changes for repository readers.
Local midnight can already be in the past when interpreted as UTC on runners west of UTC. Derive validity windows from one UTC timestamp so future-start and expiry rejection checks remain reliable while preserving signature and tampering assertions.
Scheduler overhead on loaded CI runners can exceed the shared 500 ms latency budget before retries complete. Use the default budget for retry behavior tests and reserve the strict limit for dedicated latency tests, preserving retry counts, results, and exception assertions.
Trigger releases from version tags and validate their identity and main history before publishing. This keeps the released commit tied to the tag that initiated the workflow.
Validate the published release assets and resolve the tag to its source commit before promoting the DocFX image. This ties the registry artifact to the verified release identity.
The 10.8.0 entry described workflows that no longer match the repository, so this corrects the summary to cover the tag-validated release workflow, DocFX image deployment, the pull-request pipeline rename, and the test timing fixes, and drops the stale Unreleased link now that the version is cut.
When managed and unmanaged cleanup both fail, preserve both exceptions while still invoking each cleanup hook once.
Publishing the draft must re-resolve the remote tag and match it to the SHA whose packages and image were validated.
Reusable Codecov workflows now get the upload token through an explicit secret mapping, keeping other workflow secrets out of those calls.
This documents the tag-driven package release and verified image handoff, including how maintainers can retry safely after partial publication.
This pull request adds
AddConfiguredOptions<TOptions>to connect Cuemon Parameter Object conventions with the Microsoft Options lifecycle. It exposes the primary configurator and cached default options instance, with expanded regression coverage for configuration, post-configuration, validation, and service lifetimes.Configured options integration:
Options documentation and release notes:
CI and repository workflow guidance: