chore: bump openedx-authz 1.23.0 → 1.24.0

[BryanttV]

Description

Bumps openedx-authz from 1.23.0 to 1.24.0 in the requirement files (base, development).

1.24.0:

• Added an assignments array to the response of GET /api/authz/v1/users/.
• Added an assignments_limit query parameter (default 3, max 10) to control the number of inline assignments per user.
• Renamed assignation_count to assignment_count for consistency with the rest of the codebase.
• Added roles query parameter passthrough to the underlying API call.
• Added the get_scope_display_name_map batch helper to api/utils.py.
• full_name is now taken from UserProfile.name instead of get_full_name(), for consistency across serializers.

User roles impacted: Admins using the Admin Console users list, which now receives inline role assignments per user.

The only breaking-looking change is the assignation_count → assignment_count rename in the users endpoint response. Nothing in this repo consumes that field.

Supporting information

• openedx-authz Release

Testing instructions

1. Verify the platform boots successfully with the new version (tutor dev start).
2. Run the authz test suite: pytest openedx/core/djangoapps/authz/ --no-migrations
3. Run the contentstore test suite: pytest cms/djangoapps/contentstore/ --no-migrations
4. Optionally, call GET /api/authz/v1/users/?assignments_limit=5 and check that each user includes an assignments array and assignment_count.

Deadline

None.

[openedx-webhooks]

Thanks for the pull request, @BryanttV!

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.

[wgu-taylor-payne]

Thanks!