Release 0.138.5

[odlbot]

annagav

• Update certificate to show issue date (Update certificate to show issue date #3271) (b9c2458c)

renovate[bot]

• chore(deps): update redis docker tag to v8.6.0 (chore(deps): update redis docker tag to v8.6.0 #3320) (ca0df93f)
• chore(deps): update postgres docker tag to v15.16 (chore(deps): update postgres docker tag to v15.16 #3319) (2af2649f)
• chore(deps): update dependency ruff to ^0.15 (chore(deps): update dependency ruff to ^0.15 #3318) (07d7702f)
• chore(deps): update dependency responses to ^0.26.0 (chore(deps): update dependency responses to ^0.26.0 #3317) (edddda5e)

Rachel Lougee

• Update migrate_edx_data command to set edx_enrolled and edx_emails_subscription (Update migrate_edx_data command to set edx_enrolled and edx_emails_subscription #3310) (fda1b2ee)

Tobias Macey

• chore: Created an AGENTS.md file to help give context to agentic tools (chore: Created an AGENTS.md file to help give context to agentic tools #3288) (6f1193ae)

[github-actions]

OpenAPI Changes

Show/hide ## Changes for v0.yaml:

## Changes for v0.yaml:


## Changes for v1.yaml:


## Changes for v2.yaml:

Unexpected changes? Ensure your branch is up-to-date with main (consider rebasing).

[sentry]

Bug: The save() method on BaseCertificate incorrectly sets issue_date to None for new objects, which will cause a database IntegrityError because the field is non-nullable.
_{Severity: HIGH}

Suggested Fix

Modify the save() method to avoid setting issue_date to None. Instead of reading from created_on (which is None on new instances pre-save), the logic should be removed to allow the field's default=timezone.now to function correctly. Alternatively, check if the object is new (e.g., self.pk is None) and handle the logic accordingly without assigning None.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: courses/models.py#L1360-L1363

Potential issue: When a new `BaseCertificate` instance is created without an
`issue_date` being explicitly set, the custom `save()` method is triggered. Inside this
method, the condition `if not self.issue_date:` evaluates to true. The code then
attempts to set `self.issue_date` from `self.created_on`. However, for a new object that
has not yet been saved to the database, `created_on` is `None`. This results in
`self.issue_date` being explicitly set to `None`, which overrides the field's
`default=timezone.now`. When `super().save()` is called, this `None` value violates the
`null=False` database constraint, causing an `IntegrityError` and preventing new
certificates from being created.

_{Did we get this right? 👍 / 👎 to inform future reviews.}