build!: drop automated PyPI/npm release workflows; document release policy - #71
Open
farhan wants to merge 1 commit into
Open
build!: drop automated PyPI/npm release workflows; document release policy#71farhan wants to merge 1 commit into
farhan wants to merge 1 commit into
Conversation
This was referenced Aug 21, 2026
Closed
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #71 +/- ##
======================================
Coverage 0.00% 0.00%
======================================
Files 7 7
Lines 331 331
======================================
Misses 331 331
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
farhan
marked this pull request as draft
August 21, 2026 08:45
farhan
marked this pull request as ready for review
August 24, 2026 11:32
…olicy mockprock is a development- and testing-only tool with no PyPI or npm consumers, so the release automation added maintenance overhead and secrets exposure for no benefit. - Remove the npm semantic-release workflow (.github/workflows/release.yml) - Drop npm publish-only metadata (publishConfig) from package.json - Document in README.rst that mockprock is not released and is consumed from source, linking to the edx-proctoring developing guide as the single source of truth for setup Closes openedx#70 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
farhan
force-pushed
the
farhan/drop-release-workflows-docs
branch
from
August 24, 2026 13:22
0b6829d to
3623ae7
Compare
salman2013
approved these changes
Aug 24, 2026
farhan
changed the title
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
2 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.
Important
PR implemented with the assistance of Claude Code, human-reviewed before pushing to code review.
Summary
Drop the automated npm release workflow from
mockprockand document its release policy.mockprockis a mock proctoring backend used only for local development and testing ofedx-proctoring. Nothing installs it from PyPI or npm, so release automation added maintenance and secrets exposure for no benefit.Closes #70
Changes
.github/workflows/release.yml— the semantic-release npm pipeline that ran on every push tomaster.publishConfigfrompackage.json— npm-publish-only metadata that no longer applies.README.rstthatmockprockis not published to PyPI/npm and is consumed from a local checkout, linking to the edx-proctoring developing guide for setup.🤖 Generated with Claude Code