Update deposit-service OpenAPI spec#109
Conversation
greg-rhinestone
left a comment
There was a problem hiding this comment.
🤖 Greg · ✅ LGTM
Regenerates the deposit-service spec from rhinestonewtf/deposit-service-processor@690e44e, adding deposits-scope 403 responses across the affected account/deposit endpoints. This matches the upstream key-scope enforcement surface.
Risk: Low — generated spec-only change documenting additive auth errors
019bee9 to
a7cbe81
Compare
a7cbe81 to
410e99f
Compare
greg-rhinestone
left a comment
There was a problem hiding this comment.
🤖 Greg · 🔄 Re-review · ✅ LGTM
No effective deposit-service.json change since the last Greg review; the current generated spec still contains the already-reviewed deposits-scope 403 response coverage.
410e99f to
6337692
Compare
greg-rhinestone
left a comment
There was a problem hiding this comment.
🤖 Greg · 🔄 Re-review · ✅ LGTM
Generated deposit-service spec now includes the deposits-scope 403 response on the remaining account, deposit, withdrawal, and webhook endpoints from rhinestonewtf/deposit-service-processor@6f83c1a. No new compatibility issue surfaced.
a2189ba to
10c746c
Compare
…t-service-processor@a5b8605223b23e08b9858a423ec4f12c4fd2ce1a
10c746c to
b4ebe5b
Compare
This PR updates the OpenAPI spec generated from rhinestonewtf/deposit-service-processor@a5b8605223b23e08b9858a423ec4f12c4fd2ce1a.