Update Readme

mromaszewicz · mromaszewicz · commit b29f140137e4 · 2026-07-07T12:02:34.000-07:00
diff --git a/README.md b/README.md
@@ -3348,22 +3348,12 @@ If you're using a specification with [Security Schemes](https://spec.openapis.or
 > Out-of-the-box, the server-side code generated by `oapi-codegen` does not provide security validation.
 >
 > To perform authentication, you will need to use the [validation middleware](#requestresponse-validation-middleware).
->
-> In the future, we plan to [implement server-side validation in the generated code](https://github.com/oapi-codegen/oapi-codegen/issues/1524)
 
 To see how this can work, check out the [authenticated API example](examples/authenticated-api/echo).
 
 If an operation includes an empty `{}` security alternative, generated server
-middleware treats that operation as allowing anonymous requests and does not set
-scope context for that operation.
-
-> [!WARNING]
-> This is a behavior change for specs that already list an anonymous `{}` alternative
-> alongside named schemes, in any position (e.g. `security: [{bearerAuth: []}, {}]`).
-> Previously, the generated middleware still set the scheme's scopes context key (such as
-> `BearerAuthScopes`); after regenerating, that key is no longer set for such operations,
-> so authentication middleware that enforces auth based on its presence will treat those
-> requests as anonymous.
+middleware treats that operation as allowing anonymous requests and doesn't embed required
+security scopes in the request context.
 
 ### On the client
 
