[javoconsultant]

Description

Bumps openedx-core from 1.17.0 to 1.18.0. The change is limited to the pinned version in uv.lock, requirements/edx/base.txt and requirements/edx/development.txt, regenerated with make upgrade-package package=openedx-core. The set of openedx-core dependencies is unchanged, so no other package moves.

The new release brings two changes in openedx-core:

• openedx/openedx-core#913 (closes [BE] Update/Edit Competency Criteria Group openedx-core#760): adds PATCH /api/cbe/v1/competencies/<tag_id>/criteria-groups/<group_id>/. A Course Author can use it to change a competency criteria group's logic_operator between AND and OR without rebuilding the branch beneath it. Studio already mounts openedx_learning.urls under api/, so the endpoint is available in Studio with no change here. Access goes through oel_tagging.view_taxonomy and oel_tagging.can_tag_object, which openedx-platform overrides with its own org-aware and course-aware checks.
• openedx/openedx-core#848: adds an ADR for Catalog Pathway deletion and visibility. This is documentation only, with no code change.

User roles affected: Course Author (competency criteria authoring).

Supporting information

• openedx-core release: https://github.com/openedx/openedx-core/releases/tag/v1.18.0
• Ticket: [BE] Update/Edit Competency Criteria Group openedx-core#760

Testing instructions

1. Check out this branch and install the requirements (uv sync, or pip install -r requirements/edx/development.txt).
2. In Studio, as a user with write access to a course and view access to a competency taxonomy, find a non-root criteria group for that course with GET /api/cbe/v1/competencies/<tag_id>/criteria-groups/.
3. Send PATCH /api/cbe/v1/competencies/<tag_id>/criteria-groups/<group_id>/ with {"logic_operator": "OR"} (or "AND", whichever the group does not have). The response is a 200 that reports the new logic_operator, and a repeat GET of the tree shows the change.
4. Send the same request with "logic_operator": "XOR". The response is a 400 and the group is unchanged.

Deadline

None.

Other information

• No migrations. 1.18.0 adds no model or field.
• This change does not depend on any other open PR.

🤖 Generated with Claude Code

[openedx-webhooks]

Thanks for the pull request, @javoconsultant!

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.