bump openedx-core 1.4.0 → 1.10.0

[ufedaseyeuconsultant]

Description

Bumps the openedx-core dependency from 1.4.0 to 1.6.0, to unblock QA on the
Competency-Based Education (CBE) and tagging work this release carries.

Regenerated with the project's own make upgrade-package package=openedx-core, which re-locks
uv.lock and regenerates the two affected compatibility exports
(requirements/edx/base.txt, requirements/edx/development.txt). No application code in this
repository changes; this is a dependency-version bump only.

One new transitive dependency is pulled in as a result: django-simple-history, already a
direct dependency of openedx-platform itself, now also listed as coming in via openedx-core
(no version change to it, just an added "via" entry). uv's resolver also dropped a now-stale
platform_python_implementation != 'PyPy' marker on grpcio/grpcio-status while re-resolving;
neither package's version changed.

This change impacts the Developer and Operator roles (a backend library version bump);
it has no user-facing or UI effect on its own.

Supporting information

• Unblocks QA verification of the openedx-core 1.6.0 release.

Testing instructions

1. make upgrade-package package=openedx-core reproduces this diff from a clean checkout of the
   base branch.
2. uv lock --check confirms uv.lock is internally consistent with pyproject.toml after the
   bump (already run locally; this repo's own check_python_dependencies.yml /
   check-consistent-dependencies.yml CI workflows re-verify this on the PR).
3. uv sync --no-default-groups --group bundled --frozen installs cleanly against the new lock.

Deadline

Requested to unblock QA.

Other information

• Does this change depend on other changes elsewhere? Yes: openedx-core 1.6.0 is the release
  this PR consumes; it is not produced by this repository.
• No database migrations, no deprecations, no security-relevant changes: this PR only moves a
  pinned dependency version forward and regenerates its generated lock/export files.

🤖 Generated with help of Claude Code

[openedx-webhooks]

Thanks for the pull request, @ufedaseyeuconsultant!

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

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.

[mgwozdz-unicon]

@ufedaseyeuconsultant Status note for anyone looking at the failing checks here: two of them (the test_migrations_are_in_sync failure in shared-with-lms-1, and Lint Python Imports) need fixes in openedx-core, which are going into openedx/openedx-core#853. Once that merges and the new openedx-core patch release is out, this PR should bump to that version instead of 1.6.0 and rerun make upgrade-package package=openedx-core, which should also clear the Compile requirements check.

[ormsbee]

FWIW, we're up to 1.9 already, and we'll likely have another bump when openedx/openedx-core#846 lands.

[mgwozdz-unicon]

Thank you!