Release 0.19.0

[odlbot]

Nathan Levesque

• Update docker-compose config to support OS cluster (Update docker-compose config to support OS cluster #1540) (3bff3818)
• Fix data migration erroring if a record exists (Fix data migration erroring if a record exists #1543) (dcf6b4e0)

renovate[bot]

• Update dependency faker to v28 (Update dependency faker to v28 #1550) (af0d5239)
• Update actions/upload-artifact digest to 5076954 (Update actions/upload-artifact digest to 5076954 #1528) (4ec17e35)
• Update dependency attrs to v24 (Update dependency attrs to v24 #1535) (f70fb991)
• Update dependency @faker-js/faker to v9 (Update dependency @faker-js/faker to v9 #1533) (383886ea)
• Update dependency pytest-cov to v5 (Update dependency pytest-cov to v5 #1549) (abd4d0f7)
• Update docker.elastic.co/elasticsearch/elasticsearch Docker tag to v8 (Update docker.elastic.co/elasticsearch/elasticsearch Docker tag to v8 #1260) (3eb1bf30)
• Update mcr.microsoft.com/playwright Docker tag to v1.47.0 (Update mcr.microsoft.com/playwright Docker tag to v1.47.0 #1531) (1c290a86)
• Update dependency ruff to v0.6.4 (Update dependency ruff to v0.6.4 #1530) (dfd769a1)
• Update dependency Django to v4.2.16 (Update dependency Django to v4.2.16 #1529) (64a59e8f)

Matt Bertrand

• ETL pipeline for MIT edX programs (ETL pipeline for MIT edX programs #1536) (61c64413)
• license_cc and continuing_ed_credits fields (license_cc and continuing_ed_credits fields #1544) (6afa145a)
• Add LearningResource.delivery field (eventually to replace learning_format) (Add LearningResource.delivery field (eventually to replace learning_format) #1510) (a2ddda63)
• Sort news items by publish_date (Sort news by publish date #1522) (55320c52)

Carey P Gumaer

• learning resource drawer list buttons (learning resource drawer list buttons #1537) (b64bcb88)
• display sub topics on topic channels (display sub topics on topic channels #1511) (df12493d)

[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	3bff381	docker-compose.yml	View secret
9430286	Triggered	Generic Password	3bff381	docker-compose.services.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.}