Conversation
Adds an ENV_SAVED Action hook that allows hooking into the save mechanism and running custom code after saving an environemnt.
42 tasks
* feat: upgrade Python version support to 3.13 and 3.14, drop EOL 3.9 - Update requires-python to >= 3.10 (drop EOL Python 3.9) - Add Python 3.13 and 3.14 classifiers to pyproject.toml - Update CI matrix from ['3.9', '3.12'] to ['3.10', '3.14'] - Update requirements/base.txt pip-compile header to Python 3.10 - Add changelog entry Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Fixed sphinx issues with python 3.14 * Updated Changelog * ci: replace python 3.9 with 3.10 in release workflow --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
…from account API (#1366)
This commands now schdules a celery task to populate the index on launch and upgrade. Signed-off-by: Farhaan Bukhsh <farhaan@opencraft.com>
The security patch added in #1366 fails when building against main/master edx-platform because the upstream commit is already present in master, so git am fails with "patch already applied". Move the RUN command inside the non-Main (Release mode) branch of the existing TUTOR_BRANCH_IS_MAIN conditional so it only applies when building from a release branch of edx-platform. Follow-up to #1366. Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Collaborator
|
Hey @ahmed-arb , I pushed a commit to fix the |
On Python 3.14, sphinx autodoc emits TypeVar references as py:obj with the typing.~T short-name form, which has no resolvable target. The existing nitpick_ignore only covered py:class. Add the missing py:obj entries so 'make docs' passes on 3.14.
Latest patch on the 7.0 line, pulling in upstream security fixes. Open edX Verawood tests against MongoDB 7.0 and pins pymongo==4.4.0 (which predates 8.0 server support), so we remain on 7.0. A future 7.0 -> 8.0 jump is tracked separately as it needs FCV-stepping logic. Refs #1400 Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
* chore: upgrade Caddy, Redis, Python, and Node Routine bumps to the latest stable patch on each current line: - Caddy 2.7.4 -> 2.11.4 - Redis 7.4.5 -> 7.4.9 (latest 7.4 patch; security fixes) - Python 3.12.12 -> 3.12.13 - Node.js 24.12.0 -> 24.16.0 Refs #1400 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * chore: drop Meilisearch from the bundle and fix the pyenv pin - Revert Meilisearch to v1.8.4; the v1.36 upgrade changes the on-disk index format and needs its own migration, handled in a separate PR - Bump pyenv to v2.7.2 so Python 3.12.13 has a build definition (v2.6.18 lacks it, breaking `tutor images build openedx`) - Remove Meilisearch from the changelog entry - Document Caddy v2.11.4 and Redis v7.4.9 in the configuration reference --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Co-authored-by: HammadYousaf01 <hammad.yousaf@arbisoft.com>
kdmccormick
reviewed
Jun 30, 2026
The setuptools build constraint added in #1411 pins 69.1.1, which is forward-ported from the release branch to main. On main we build against edx-platform's master branch, where mysqlclient==2.2.8 declares its license using the PEP 639 `project.license` format. setuptools only understands that format from 77.0.0 onwards, so building the openedx image with setuptools 69.1.1 fails: configuration error: `project.license` must be valid exactly by one Bump the pinned version to 80.9.0 on main. It is new enough to build the master requirements (mysqlclient 2.2.8 and friends) and still ships pkg_resources, which setuptools 82.0.0 removes but which is still required at runtime by dependencies such as fs (pyfilesystem2) -- matching edx-platform's own `setuptools<82` constraint. The release branch intentionally stays on 69.1.1: Ulmo's requirements build fine with it, and this avoids changing the setuptools version shipped by the current stable release.
Generated by Claude Code on behalf of @ahmed-arb
Co-authored-by: Kyle McCormick <kyle@axim.org>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
12 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
v22.0.0 verawood release
Epic: Verawood Sandbox and Release Preparation
Todos before merge
Merge Option
Generated by Claude Code on behalf of @ahmed-arb