chore(docs): update of OEL images (#2404)

Author: ory-bot

docs/self-hosted/oel/keto/changelog/v25.4.12.md

@@ -0,0 +1 @@
+No changelog entries found for keto/oel in versions v25.4.12

docs/self-hosted/oel/keto/changelog/v26.1.0.md

@@ -0,0 +1 @@
+No changelog entries found for keto/oel in versions v26.1.0

docs/self-hosted/oel/keto/changelog/v26.1.1.md

@@ -0,0 +1 @@
+No changelog entries found for keto/oel in versions v26.1.1

docs/self-hosted/oel/keto/changelog/v26.1.2.md

@@ -0,0 +1 @@
+No changelog entries found for keto/oel in versions v26.1.2

docs/self-hosted/oel/kratos/changelog/v25.4.12.md

@@ -0,0 +1 @@
+No changelog entries found for kratos/oel in versions v25.4.12

docs/self-hosted/oel/kratos/changelog/v26.1.0.md

@@ -0,0 +1,13 @@
+## v26.1.0
+
+### Accept Hydra Login Challenge in Verification Flows
+
+Fixes a bug where Kratos would not accept the Hydra login challenge in verification flows, if they originated from a refresh login
+flow.
+
+This would manifest as an "unknown form state" in Ory Elements and the Ory Account Experience.
+
+### Change in Event Attributes
+
+Login and Registration Events now include `SelfServiceMethodUsed` attribute. The `SelfServiceStrategyUsed` attribute is
+deprecated, and it is advised to use newly introduced `SelfServiceFlowName` attribute.

docs/self-hosted/oel/kratos/changelog/v26.1.1.md

@@ -0,0 +1,11 @@
+## v26.1.1
+
+### Fix `null` response in OAuth2 login flow with existing session
+
+Fixed a bug where the `/self-service/login/browser` endpoint would return `null` instead of a proper error response when called
+with an existing session, a Hydra login challenge, and `Accept: application/json` header.
+
+### Requests to Admin Endpoint without `/admin` Prefix No Longer Redirect
+
+The admin endpoint now serves requests that omit the `/admin` prefix instead of redirecting them with the correct path. This
+change is not expected to affect existing clients, but instead avoids unnecessary redirects.

docs/self-hosted/oel/kratos/changelog/v26.1.2.md

@@ -0,0 +1,8 @@
+## v26.1.2
+
+### Properly accept OAuth2 login challenges in account linking flows
+
+In the account linking flows, the OAuth2 login challenge was not properly accepted and stored in the login flow. This meant that
+users going through account linking would not be redirected back to the OAuth2 client after logging in, but had to re-confirm
+their credentials a second time. This has now been fixed by properly accepting and storing the OAuth2 login challenge in the login
+flow.

docs/self-hosted/oel/oathkeeper/changelog/v25.4.12.md

@@ -0,0 +1 @@
+No changelog entries found for oathkeeper/oel in versions v25.4.12

docs/self-hosted/oel/oathkeeper/changelog/v26.1.0.md

@@ -0,0 +1 @@
+No changelog entries found for oathkeeper/oel in versions v26.1.0