Release 2.2.1 - Oauth scopes review - #204 - #205
Conversation
🟡 Risk Classification: MINORApproval route: AI Review + Human Approval Classification reasons
Operational gates
Files analysed: 1 wall-e 2026.06.19-02 · policy |
🔬 Debug — why this classification?Each reason code emitted by the classifier, its source clause in the AI in SDLC Control Framework, and what it means.
Kinds:
See issue #3 for the proposal to formalise this map as Appendix A of the standards doc. wall-e 2026.06.19-02 · debug |
🔵 Advisory review: Sound, but needs your judgementThis PR needs a human approval. The code itself reads as correct; whether it should land depends on context I don't have. This diff only shows the version bump from 2.2.0 to 2.2.1 in version.rb; the substantial OAuth scopes changes described in the PR body are not visible in the provided diff. For you to decide
This is not an approval. wall-e cannot auto-approve this PR — it is an opinion to help whoever does. Advisory review · us.anthropic.claude-sonnet-4-6 · wall-e 2026.06.19-02 |
|



This release updates the
OAuthScopesconstants in the SDK to match the latest Checkout.com API specification. It adds missing scopes, removes deprecated ones, and ensures naming consistency with the API and other SDKs. The integration and test code is updated to use the correct, current scope constants, and new tests are added to verify completeness, uniqueness, and ordering of the scope constants.OAuth Scopes synchronization and improvements:
OAuthScopes, including entire scope families (e.g., card management, issuing, vault, compliance requests, payment sessions, and more), and ensured all constants are declared in alphabetical order. Deprecated scopes are removed, and comments clarify distinctions between similar scopes and document any specification oddities.MARKETPLACEwithACCOUNTS, andCARD_METADATAwithVAULT_CARD_METADATA, and removing deprecated issuing scopes in favor of the newISSUING_CARD_MANAGEMENT_*constants. [1] [2] [3]Testing and validation enhancements: