Repository navigation
Prepare the 2.0.1 patch release - #95
Merged
Merged
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configuration
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. Comment |
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



Summary
Prepare the
2.0.1patch release. Move completed security and malformed-input fixes from Unreleased into the dated release section, add its release link, and document the outstanding Q02-Q10/Q40/Q41 qualification limits. The exact package version comes from the subsequentv2.0.1tag through MinVer.Correct release guidance that still described the 2.0 line as unpublished. During the local release rehearsal, the callback-admission test exposed a synchronization race: it waited for registration closure before testing callback closure. It now waits for the existing per-subscription drain signal and verifies the admitted callback completed without a captured exception. Production code is unchanged in this PR.
Scope and ownership
Release notes, release guidance, and one existing callback test. There is no new public API, native ABI, shipping dependency, package layout, runtime policy, or SDK/Client ownership change. The patch includes the already-merged fixes since 2.0.0. The existing 2.0 MinVer floor remains appropriate for this patch tag.
Validation
f149403cb099907165a07d214abd1c4fe6993dd0; all jobs, Sonar and CodeQL passed.dotnet pack src/CheatEngine.SDK -c Release -p:MinVerVersionOverride=2.0.1; Release tests consumed that exact local rehearsal package. The release workflow will rebuild and attest its own package on the tag.Requirement coverage:
Disable_admission_waits_for_an_entered_callback_and_rejects_a_late_onewaits for actual callback closure, rejects the late call, drains the entered callback without exception, and checks lifecycle unregister. All 9LuaHostSubscriptionTestspassed in Debug and Release with zero failures/skips.Compatibility and release impact
Release 2.0.1 is a patch on the published 2.0.0 contract. No version tag is moved or reused. Publication uses the existing draft-first trusted-publishing workflow and its exact tested artifact. No locally packed nupkg will be published.
Checklist