Skip to content

chore: bump openedx-core 1.23.0 → 1.26.0 - #39399

Merged
mgwozdz-unicon merged 1 commit into
openedx:masterfrom
ufedaseyeuconsultant:ufedaseyeu/bump-openedx-core-1.26.0
Nov 18, 2026
Merged

mgwozdz-unicon merged 1 commit into
openedx:masterfrom
ufedaseyeuconsultant:ufedaseyeu/bump-openedx-core-1.26.0

Conversation

@ufedaseyeuconsultant

Copy link
Copy Markdown
Contributor

Description

Bumps openedx-core from 1.23.0 to 1.26.0, regenerated via make upgrade-package package=openedx-core (requirements/edx/base.txt, requirements/edx/development.txt and uv.lock).

The releases in between carry the next slice of the Competency-Based Education (CBE) work, so it can go to QA on a devstack:

Who is affected: Course Authors get the new CBE delete/archive and create behaviors through the existing cbe/v1 endpoints this platform already mounts. Learners see no change. Operators get one new migration.

Supporting information

Testing instructions

  1. CI is the main check: the pinned version installs and the platform test suite passes against it.
  2. On a devstack with this branch, migrations apply cleanly. The range adds one migration, oel_tagging 0023 (the archived and deletion_locked columns). pip show openedx-core reports 1.26.0.
  3. Smoke-check the new behavior end to end: DELETE /api/cbe/v1/competencies/<tag_id>/criteria-groups/<group_id>/ removes an unused group outright and reports archived: true for one a learner was measured under; POST to /api/cbe/v1/competencies/<tag_id>/criteria/ against an archived leaf returns 400.

Deadline

None.

Other information

Dependency-only change; no platform code is touched. The version pins move only openedx-core, nothing else in the lockfiles changes.

🤖 Generated with Claude Code

Regenerated via `make upgrade-package package=openedx-core`. Picks up
openedx/openedx-core#856 (archived and deletion_locked flags on the
tagging models), released in 1.24.0; openedx/openedx-core#936 (the
delete-or-archive endpoint for a CompetencyCriteriaGroup,
openedx/openedx-core#675), released in 1.25.0; and
openedx/openedx-core#899 (archived state enforced when creating a
competency criterion, openedx/openedx-core#717), released in 1.26.0,
so the Competency-Based Education (CBE) removal flows can go to QA.

Related to openedx/openedx-core#675 and openedx/openedx-core#717

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@openedx-webhooks openedx-webhooks added the open-source-contribution PR author is not from Axim or 2U label Nov 18, 2026
@openedx-webhooks

Copy link
Copy Markdown

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:

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 mgwozdz-unicon left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

@mgwozdz-unicon
mgwozdz-unicon merged commit 8524015 into openedx:master Nov 18, 2026
42 checks passed
@github-project-automation github-project-automation Bot moved this from Needs Triage to Done in Contributions Nov 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

open-source-contribution PR author is not from Axim or 2U

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

3 participants