chore: bump openedx-authz 1.21.1 → 1.23.0

[wgu-taylor-payne]

Description

Bumps openedx-authz from 1.21.1 to 1.23.0 across all requirement files (base, testing, doc, development).

This picks up changes from two minor releases:

1.22.0:

• Role assignment now succeeds for a course/library scope key before its CourseOverview/ContentLibrary exists, and links up automatically once the object is created. (Unskip Acceptance Tests #369)

1.23.0:

• Added courses.view_advanced_settings permission for read-only access to advanced settings.
• Added courses.view_certificates permission for read-only access to certificates.
• Added courses.view_group_configurations permission for read-only access to group configurations.
• Added courses.view_library_updates permission for read-only access to library updates.
• All four view permissions are granted to all four course roles (Admin, Staff, Editor, Auditor).

User roles impacted: Course Editor, Course Auditor. These roles will gain the ability to view pages that were previously fully blocked (advanced settings, certificates, group configurations, library updates) once the corresponding enforcement changes land in follow-up PRs.

This PR is purely additive — the new permission constants exist in the library but are not yet consumed by any enforcement point in this repo. No behavior change until follow-up PRs land.

Supporting information

• openedx-authz CHANGELOG
• openedx-authz PR #385: add view permissions

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 (existing tests should pass unchanged since no enforcement points use the new constants yet)

Deadline

None — but this unblocks four follow-up PRs that split read/write permission enforcement.

Other information

• Depends on: openedx-authz 1.23.0 being published to PyPI.
• No migrations — purely a library version bump.
• No deprecations — all changes in 1.22.0 and 1.23.0 are backwards-compatible additions.
• Follow-up PRs (depend on this): enforcement changes for view_advanced_settings, view_certificates, view_group_configurations, and view_library_updates.

[openedx-webhooks]

Thanks for the pull request, @wgu-taylor-payne!

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.