chore(deps): Bump RestSharp from 112.1.0 to 114.0.0 - #45
Merged
Alexdev257 merged 1 commit intoMay 11, 2026
Conversation
--- updated-dependencies: - dependency-name: RestSharp dependency-version: 114.0.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
dependabot
Bot
deleted the
dependabot/nuget/services/AuthService/src/AuthService.Infrastructure/dev/RestSharp-114.0.0
branch
May 11, 2026 13:06
Alexdev257
added a commit
that referenced
this pull request
Sep 1, 2026
Fixes bugs #27, #28, #30, #36, #38, #39, #40, #45, #46, #48, #50 from the solars.io.vn 2026-08-29 QA write-flow sweep: - #40 NotificationPreference upsert 500'd on every second insert (PK left as Guid.Empty) - #45 MediatR registered twice in Battery/Ticket/AuditAggregator/FileStorage (Application AddMediatR + AddSharedInfrastructure), doubling every INotificationHandler execution incl. audit logs - #30 IoT calibration create 500'd when client omitted the UTC "Z" suffix (DateTimeKind.Unspecified into timestamptz) - #36 Firmware release creation always failed validation because the upload-binary fallback URL was relative, not absolute - #27 Audit logs and login history recorded the gateway's pod IP instead of the real client IP (wrong header read downstream of ApiGateway) - #28 TOTP QR issuer showed the API URL instead of a product name - #38 Wrong OTP/password on pre-login and 2FA flows returned 401, which the FE's axios interceptor treats as session-expired and silently logs out mid-flow; switched these business errors to 400 - #39 Failed 2FA attempts never appeared in the user's own login history (only in the admin audit log) - #46 FileAuditLog infrastructure existed end-to-end but no handler ever wrote to it; wired real audit writes into upload/download/delete/ presigned-url flows - #48 Battery admin audit log showed the actor's raw account GUID with no display name - #50 No safeguard against deleting/merging/demoting the last remaining Admin account, which would permanently lock the system out of admin access Verified against current dev (18 commits landed since the QA sweep) rather than assuming the report's file:line references still applied. Added regression tests for #30, #39, #46, and #50. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Alexdev257
added a commit
that referenced
this pull request
Sep 1, 2026
Fixes bugs #27, #28, #30, #36, #38, #39, #40, #45, #46, #48, #50 from the solars.io.vn 2026-08-29 QA write-flow sweep: - #40 NotificationPreference upsert 500'd on every second insert (PK left as Guid.Empty) - #45 MediatR registered twice in Battery/Ticket/AuditAggregator/FileStorage (Application AddMediatR + AddSharedInfrastructure), doubling every INotificationHandler execution incl. audit logs - #30 IoT calibration create 500'd when client omitted the UTC "Z" suffix (DateTimeKind.Unspecified into timestamptz) - #36 Firmware release creation always failed validation because the upload-binary fallback URL was relative, not absolute - #27 Audit logs and login history recorded the gateway's pod IP instead of the real client IP (wrong header read downstream of ApiGateway) - #28 TOTP QR issuer showed the API URL instead of a product name - #38 Wrong OTP/password on pre-login and 2FA flows returned 401, which the FE's axios interceptor treats as session-expired and silently logs out mid-flow; switched these business errors to 400 - #39 Failed 2FA attempts never appeared in the user's own login history (only in the admin audit log) - #46 FileAuditLog infrastructure existed end-to-end but no handler ever wrote to it; wired real audit writes into upload/download/delete/ presigned-url flows - #48 Battery admin audit log showed the actor's raw account GUID with no display name - #50 No safeguard against deleting/merging/demoting the last remaining Admin account, which would permanently lock the system out of admin access Verified against current dev (18 commits landed since the QA sweep) rather than assuming the report's file:line references still applied. Added regression tests for #30, #39, #46, and #50. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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
1 participant
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.
Updated RestSharp from 112.1.0 to 114.0.0.
Release notes
Sourced from RestSharp's releases.
114.0.0
What's Changed
Full Changelog: restsharp/RestSharp@113.1.0...114.0.0
113.0
What's Changed
404response code means succes by @jnoordsij in Remove note that404response code means succes restsharp/RestSharp#2281New Contributors
404response code means succes restsharp/RestSharp#2281Full Changelog: restsharp/RestSharp@112.1.0...113.0.0
Commits viewable in compare view.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)