fix: bump django-autocomplete-light 4.0.1 -> 4.0.3 (yanked from PyPI)

[taimoor-ahmed-1]

Summary

`django-autocomplete-light==4.0.1` was removed from PyPI sometime between 2026-06-19 and 2026-06-22, breaking the `install requirements` step on every CI run against `feat/axim-api_improvements` since then. The pin fails before any test code runs.

Evidence

$ curl -sI https://pypi.org/pypi/django-autocomplete-light/4.0.1/json
HTTP/2 404
$ curl -s https://pypi.org/simple/django-autocomplete-light/ | grep -oE '4\.0\.[0-9]+'
4.0.0
4.0.3   ← next stable

ERROR: Could not find a version that satisfies the requirement django-autocomplete-light==4.0.1
ERROR: No matching distribution found for django-autocomplete-light==4.0.1

Master is already on 4.0.3

$ git show origin/master:requirements/edx/base.txt | grep autocomplete
django-autocomplete-light==4.0.3

Upstream has already bumped to `4.0.3` on master. This commit brings `feat/axim-api_improvements` into line so the dozens of open PRs targeting it can install requirements again.

Diff

 requirements/edx/base.txt        | 2 +-
 requirements/edx/development.txt | 2 +-
 requirements/edx/doc.txt         | 2 +-
 requirements/edx/testing.txt     | 2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)

Each is a one-line version bump. No other dependencies changed.

Test plan

• CI's `install requirements` step succeeds (no `No matching distribution found` error)
• `cms-1`, `cms-2`, `lms-1..5`, and the `coverage` jobs all proceed past install
• No behavioural changes — `django-autocomplete-light` is used only in Django admin autocomplete UI, and 4.0.0 → 4.0.3 is a patch-level move with no migration / API impact

Related

Came up while investigating CI failures on #38773. Same dependency yank also blocks every other open PR against `feat/axim-api_improvements`.

🤖 Generated with Claude Code

[openedx-webhooks]

Thanks for the pull request, @taimoor-ahmed-1!

This repository is currently maintained by @openedx/wg-maintenance-openedx-platform.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

Details

---

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.