Fix issue 609

[elracing]

Description
This pull request removes all remaining references to Redux from the repository. Redux is not being actively utilized within the project codebase and only remains as unused references inside configuration JSON files.

• User Role Impacts: None. This is a dependency cleanup and does not affect the user experience for Learners, Course Authors, or Developers.
• Accessibility / UI Changes: None. No visual elements or interfaces are altered.

Supporting Information

• Closes Remove redux as it is not being used anywhere in the repo #609

Testing Instructions

1. Clone or update your local repository to this branch.
2. Run your local dependency installer (e.g., npm install or pip install depending on the exact project scope) to ensure clean installation without Redux.
3. Run the full test suite to verify that no components break due to the missing package:

   npm test

4. Perform a global search across the codebase to confirm no active Redux imports or packages remain:

   grep -ri "redux" .

Deadline

None.

[openedx-webhooks]

Thanks for the pull request, @elracing!

This repository is currently maintained by @jajjibhai008.

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.

[elracing]

Hi @jajjibhai008 — this is my first contribution to this project. I've fixed issue #609 by removing redux references. Would appreciate a review when you have time!

[mphilbrick211]

Hi @elracing! Welcome, and thank you for this contribution! In order for your CLA check to turn green, you'll need to submit a CLA form. If you are contributing as an individual, please fill out the individual CLA form here.

If you are contributing on behalf of an organization, please have your manager reach out to [email protected] so you may be added to your org's existing entity agreement.

Please let me know if you have any questions. Thanks!

[e0d]

@elracing
I notice there are some commit-lint failures. Please note that we use conventional commits across Open edX projects. You can read about the details here. Can you please amend your commit messages to follow our standard?

[mphilbrick211]

@elracing I notice there are some commit-lint failures. Please note that we use conventional commits across Open edX projects. You can read about the details here. Can you please amend your commit messages to follow our standard?

Hi @elracing! Just checking in here - do you plan to pursue this pull request?

[elracing]

Hello Sorry for the delays, I intend to pursue this PR.

…

On Wed, Aug 19, 2026, 4:55 PM Michelle Philbrick ***@***.***> wrote: *mphilbrick211* left a comment (openedx/frontend-app-learner-record#684) <#684 (comment)> @elracing <https://github.com/elracing> I notice there are some commit-lint failures. Please note that we use conventional commits across Open edX projects. You can read about the details here <https://open-edx-proposals.readthedocs.io/en/latest/best-practices/oep-0051-bp-conventional-commits.html#type>. Can you please amend your commit messages to follow our standard? Hi @elracing <https://github.com/elracing>! Just checking in here - do you plan to pursue this pull request? — Reply to this email directly, view it on GitHub <#684?email_source=notifications&email_token=ANIQG5TMYNAAZNADWIT7TCT5KYH3XA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMZUG44DQNJTGI3KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-5347885326>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANIQG5WHIRCP4PUEL6MTBHL5KYH3XAVCNFSNUABFKJSXA33TNF2G64TZHMZTQNZVG4ZTKMBUHNEXG43VMU5TINZWGU3DQMZVGA32C5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/ANIQG5VBJCFRM4BLCNFHYGD5KYH3XA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMZUG44DQNJTGI3KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/ANIQG5WJ5M73VLUWMZDN5RL5KYH3XA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMZUG44DQNJTGI3KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>