feat: Upgrade Python dependency enterprise-integrated-channels - #453
feat: Upgrade Python dependency enterprise-integrated-channels#453vshaikismail-sonata wants to merge 1 commit into
Conversation
There was a problem hiding this comment.
🟢 Approval recommended
The change is a straightforward dependency pin bump applied consistently across the relevant compiled requirements files.
Pull request overview
This PR updates the pinned version of the enterprise-integrated-channels Python dependency across the edx-platform compiled requirements sets, ensuring consistent dependency resolution in base, development, testing, and documentation environments.
Changes:
- Bump
enterprise-integrated-channelsfrom0.1.66to0.1.68in the base requirements lock. - Propagate the same version bump to the derived development, testing, and doc requirements locks.
File summaries
| File | Description |
|---|---|
| requirements/edx/base.txt | Updates the pinned enterprise-integrated-channels version used as the foundation for other requirement sets. |
| requirements/edx/development.txt | Aligns dev requirements with the updated base pin. |
| requirements/edx/testing.txt | Aligns test requirements with the updated base pin. |
| requirements/edx/doc.txt | Aligns doc-build requirements with the updated base pin. |
Review details
- Files reviewed: 4/4 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
2b0f49d to
759f7f3
Compare
There was a problem hiding this comment.
🔵 Needs a closer look
Upgrading an external dependency can introduce runtime/test regressions that require human validation (e.g., CI results and/or targeted smoke testing) beyond what can be confirmed from the diff alone.
Review details
- Files reviewed: 4/4 changed files
- Comments generated: 0 new
- Review effort level: Lite
Description
Describe what this pull request changes, and why. Include implications for people using this change.
Design decisions and their rationales should be documented in the repo (docstring / ADR), per
OEP-19, and can be
linked here.
Useful information to include:
"Developer", and "Operator".
changes.
Supporting information
Link to other information about the change, such as Jira issues, GitHub issues, or Discourse discussions.
Be sure to check they are publicly readable, or if not, repeat the information here.
Testing instructions
Please provide detailed step-by-step instructions for testing this change.
Deadline
"None" if there's no rush, or provide a specific date or event (and reason) if there is one.
Other information
Include anything else that will help reviewers and consumers understand the change.