Release 0.23.1

[odlbot]

renovate[bot]

• Update dependency urllib3 to v2 (Update dependency urllib3 to v2 #1741) (dbf69840)
• Update dependency @faker-js/faker to v9 (Update dependency @faker-js/faker to v9 #1735) (69f48937)
• Update dependency faker to v30 (Update dependency faker to v30 #1732) (e9799f55)
• Update dependency toolz to v1 (Update dependency toolz to v1 #1733) (3519a74d)
• Update Yarn to v4.5.1 (Update Yarn to v4.5.1 #1716) (5bd52bd7)
• Update actions/checkout digest to eef6144 (Update actions/checkout digest to eef6144 #1686) (8c3357ba)

Anastasia Beglova

• ol-template is not used (remove frontends/ol-template #1738) (86723a88)

Nathan Levesque

• Fixes to make learn work with scim-for-keycloak (Fixes to make learn work with scim-for-keycloak #1727) (b225c973)

Chris Chudzicki

• Navigation Accessibility (Navigation Accessibility #1726) (a066cc51)
• Search count inside label (Search count inside label #1730) (47ee91e6)
• Announce search count for screen readers (Announce search count for screen readers #1713) (f620c3a6)

Jon Kafton

• Middleware for SSL redirect (Middleware for SSL redirect #1729) (739b5bdf)
• Clean out the static frontend (Clean out the static frontend #1731) (c0ac29b1)

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
9430286	Triggered	Generic Password	c0ac29b	docker-compose-e2e-tests.yml	View secret
9430286	Triggered	Generic Password	c0ac29b	docker-compose-e2e-tests.yml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}