Skip to content

ci: disable auto dependency upgrades - #483

Closed
samuelallan72 wants to merge 1 commit into
masterfrom
samuel/remove-deps
Closed

samuelallan72 wants to merge 1 commit into
masterfrom
samuel/remove-deps

Conversation

@samuelallan72

Copy link
Copy Markdown
Member

Description

We're no longer maintaining this, so we don't want to deal with the automated dependency upgrade PRs.

Supporting information

Ref: #482 (comment)

Private-ref: https://tasks.opencraft.com/browse/SE-6622

Testing instructions

  • verify this is what we want
  • verify this correctly removes all references to the auto dep updates

Author concerns

Do we want to just archive this repo completely, rather than removing this? If we're not maintaining this any more, archiving is probably the way to go. cc @bradenmacdonald

We're no longer maintaining this, so we don't want to deal with the
automated dependency upgrade PRs.

Ref: #482 (comment)

Private-ref: https://tasks.opencraft.com/browse/SE-6622
@samuelallan72 samuelallan72 self-assigned this Jul 28, 2026
@codecov

codecov Bot commented Jul 28, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 45.04%. Comparing base (b89d041) to head (2308863).

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #483   +/-   ##
=======================================
  Coverage   45.04%   45.04%           
=======================================
  Files          40       40           
  Lines        3303     3303           
  Branches      401      401           
=======================================
  Hits         1488     1488           
  Misses       1768     1768           
  Partials       47       47           
Flag Coverage Δ
unittests 45.04% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@Agrendalath

Copy link
Copy Markdown
Member

@xitij2000, can we archive this repo? If yes, we can probably close this PR.

cc: @samuelallan72

@xitij2000

Copy link
Copy Markdown
Member

@Agrendalath Not yet, we are still trying to work on a replacement.

@samuelallan72

Copy link
Copy Markdown
Member Author

@xitij2000 does the readme warning need updating? :

Problem Builder is no longer being developed by OpenCraft. It will be supported with compatibility and security fixes till the Ulmo release, after which this repository will be stop receiving further updates and eventually be archived.

Are we planning to maintain this until we find a replacement? Did I hear that this will stop working altogether in a future openedx-platform release?

@xitij2000

Copy link
Copy Markdown
Member

@samuelallan72 Yes, till we properly deprecate this and have a replacement, we need to maintain it.

@samuelallan72

Copy link
Copy Markdown
Member Author

@xitij2000 @bradenmacdonald checking back on the status of this - do we have a replacement yet? If not, can we update the readme to say we're still maintaining this? We may also need to test and do some updates for Verawood.

@bradenmacdonald

bradenmacdonald commented Nov 2, 2026 •

Copy link
Copy Markdown
Member

@samuelallan72 I think the replacement work is defined in BB-10800/BB-10798/BB-10799 so no we don't have a replacement yet. But we announced that:

we have not seen sufficient interest in sponsoring continued development. As such, we’ve decided to deprecate the XBlock without a replacement.

Problem Builder is still used in our active "Contributing to Free/Libre and Open Source Software" course on courses.opencraft.com, although only 3 learners used it (Problem Builder activities in that course) this year, and none since March.

We do want to keep that course working, so it's a question of what is the least effort. Personally I would suggest we refactor this repo to remove all python dependency specifications whatsoever other than listing what's currently in base.in as unversioned dependencies in setup.py (or better, pyproject.yaml) so that it can at least be installed on Verawood and our course will continue to work, but make sure the project README clearly says it's now unmaintained and may or may not work at all.

I've always thought it's dumb that XBlocks pin exact versions of random dependencies, when they're going to be installed into the platform's virtualenv anyways, and it has the final say over what version of each thing gets installed. (Except in the extremely rare case that your XBlock has a unique dependency that the platform doesn't yet have.)

@samuelallan72

Copy link
Copy Markdown
Member Author

@bradenmacdonald thanks!

We do want to keep that course working, so it's a question of what is the least effort.

How extensively is the problem-builder block used in that course? I'm wondering if it would be feasible to refactor that course instead, especially if problem-builder might stop working at some point.

Personally I would suggest we refactor this repo to remove all python dependency specifications whatsoever other than listing what's currently in base.in as unversioned dependencies in setup.py (or better, pyproject.yaml) so that it can at least be installed on Verawood and our course will continue to work, but make sure the project README clearly says it's now unmaintained and may or may not work at all.

This sounds good to me 👍

@samuelallan72
samuelallan72 deleted the samuel/remove-deps branch November 3, 2026 02:19
samuelallan72 added a commit that referenced this pull request Nov 3, 2026
We're no longer maintaining this, so we don't want to deal with the
automated dependency upgrade PRs.

Also simplify the dependencies in setup.py, so it will be installable in
newer Open edX platform releases without version conflicts. However,
note that things could stop working at some point due to
incompatibilities anyway.

Also pin setuptools to < 82 to retain `pkg_resources`.
Ref. https://setuptools.pypa.io/en/stable/history.html#v82-0-0

This should keep it installable at least for Verawood for now.

Ref: #483

Private-ref: https://tasks.opencraft.com/browse/SE-6622
@samuelallan72

Copy link
Copy Markdown
Member Author

@bradenmacdonald I created #484 to make the updates. Please take a look when you can. :)

@bradenmacdonald

Copy link
Copy Markdown
Member

@samuelallan72

How extensively is the problem-builder block used in that course?

The use case is pretty simple: after an activity unit, the XBlock provides a text field where you can describe what you did, and then it gets posted to the instructor and also gets displayed back to the same learner later on in the course when it's recapping their previous activities.

Unfortunately, I don't think there is any other XBlock with this capability at the moment, although one has been proposed

samuelallan72 added a commit that referenced this pull request Nov 9, 2026
We're no longer maintaining this, so we don't want to deal with the
automated dependency upgrade PRs.

Also simplify the dependencies in setup.py, so it will be installable in
newer Open edX platform releases without version conflicts. However,
note that things could stop working at some point due to
incompatibilities anyway.

Also pin setuptools to < 82 to retain `pkg_resources`.
Ref. https://setuptools.pypa.io/en/stable/history.html#v82-0-0

This should keep it installable at least for Verawood for now.

Ref: #483

Private-ref: https://tasks.opencraft.com/browse/SE-6622
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants