Repository navigation
Pin verifier-server to main after the review fixes - #68
Merged
Merged
Conversation
Verifier-server #4 to #8 merged: requests that fail no longer close the listener, trailing-slash paths route, verify.json is written atomically and refused when corrupt, records are validated and ckeys normalised before storage, .env loads on every platform, and OAuth2 sessions are keyed by cookie with asynchronous provider calls. The bot's call pattern is unchanged; tests/verifier-integration.php passes on the new pin. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016WTP2S4qKEFT8a6a6yFEL4
Member
Author
|
2026-11-06: head 5420d89 bumps the verifier-server pin to 05ddbc1 (Verifier-server #4 to #8 merged). Local: Generated by Claude Code |
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.
Requested by Val · project thread
Summary
Bumps the
vzgcoders/verifier-servercomposer pin from838750dto05ddbc1ae91cc28215fd682f045353c3f51ff6a7, the Verifier-servermainhead after the review PRs Valgorithms/Verifier-server#4 to #8 were merged.composer.lockis updated to match.What the bot gets from the new pin:
/verified/with a trailing slash routes like/verified, so the remote cURL path inVerifier::verify()works.HostedVerificationSource::validateso the desktop instances never reject the whole list.verify.jsonis reported instead of silently loading as empty, DB storage mode works past the first insert./dwa,/ss14wa) now use averifier_sessioncookie and async provider calls;getSessions()[endpoint][key]['user']is still read the same way.No bot code changes. The in-process contract (
handleEndpoint,arrayToRequestString,getState()->getVerifyList(),getEndpoint('/ss14verified')) is unchanged and covered bytests/verifier-integration.php.Test plan
composer validate --no-check-publish: OK (pre-existing warnings only)php tests/verifier-integration.php: pass on the new pinphp tests/http-dependency.php,php tests/windows/hosted-verifier.php: passphp -loversrc/: no syntax errorsverifier-integration.ymlon this headChangelog:
Generated by Claude Code
Summary by CodeRabbit