autogen(docs): regenerate and update changelog

[skip ci]

CHANGELOG.md

@@ -4,7 +4,7 @@
 <!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
 **Table of Contents**
 
-- [0.0.0 (2023-10-16)](#000-2023-10-16)
+- [0.0.0 (2023-10-17)](#000-2023-10-17)
     - [Bug Fixes](#bug-fixes)
     - [Features](#features)
 - [2.2.0-rc.3 (2023-08-16)](#220-rc3-2023-08-16)
@@ -702,7 +702,7 @@
 
 <!-- END doctoc generated TOC please keep comment here to allow auto update -->
 
-# [0.0.0](https://github.com/ory/hydra/compare/v2.2.0-rc.3...v0.0.0) (2023-10-16)
+# [0.0.0](https://github.com/ory/hydra/compare/v2.2.0-rc.3...v0.0.0) (2023-10-17)
 
 
 ### Bug Fixes
@@ -729,6 +729,7 @@
     will redirect the user to the URL found under `urls.registration`
     (instead of `urls.login`).
 
+* Allow injecting extra fosite strategies ([#3646](https://github.com/ory/hydra/issues/3646)) ([88b0b7c](https://github.com/ory/hydra/commit/88b0b7cfdf1a1968bf3a720cb2e6640451e2956b))
 * Re-enable legacy client IDs ([#3628](https://github.com/ory/hydra/issues/3628)) ([5dd7d30](https://github.com/ory/hydra/commit/5dd7d306ba8181b1fff1225d056a2ee69183392e)):
 
     This patch changes the primary key of the `hydra_client` table. We do not expect issues, as that table is probably not overly huge in any deployment. We do however highly recommend to test the migration performance on a staging environment with a similar database setup.