Paver Removal 2.5/3 #36046
Merged
Paver Removal 2.5/3 #36046
Conversation
This file contains 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
This is technically a breaking change, but these commands were added a week ago and were not yet documented, so I'm not worried about breaking anyone's workflow with this commit.
Draft
feanil
approved these changes
Dec 18, 2024
Closed
This was referenced Dec 18, 2024
Open
|
2U Release Notice: This PR has been deployed to the edX staging environment in preparation for a release to production. |
|
2U Release Notice: This PR has been deployed to the edX production environment. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
There's some insanity in how edx-proctoring provides worker scripts (writeup to come later) that is blocking the full "Paver Removal 3/3" PR. It's still TBD how long we will let that issue block the Paver removal. But, in the meantime, I'd like to merge that PR's non-breaking doc updates and
npm run test*improvements.For description, supporting info, and test instructions, see #34832 , but just ignore all the "breaking changes".