Remove broken PyPI publish workflow and stale README badges - #168
Open
lbougan wants to merge 2 commits into
Open
Remove broken PyPI publish workflow and stale README badges#168lbougan wants to merge 2 commits into
lbougan wants to merge 2 commits into
Conversation
The workflow failed on every release since the PyPI token went dead, and deploys install from the release zipball, not PyPI, so publishing is not needed. Also drop the stale PyPI badges (package is not maintained on PyPI) and point the tests badge at sentier-dev instead of the old gchazot fork.
…ADME dev_server.sh no longer exists and releases are deployed from the GitHub release zipball, not PyPI.
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
1 participant
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.
Summary
The
publish_pypi.ymlworkflow has failed on every release since the PyPI token went dead (latest: run 32703235791 on release 1.4.4, "token value does not start with pypi-"). Deploys install from the GitHub release zipball, not PyPI, so the publish step serves no purpose. This removes the workflow so releases stop producing red CI.Also cleans up stale docs that contradicted this:
django-dds_registrationpackage on PyPI is not maintained) and points the tests badge atsentier-dev/dds_registrationinstead of the oldgchazotfork.dev_server.sh, which no longer exists; replaced with the actual pip/pytest/runserver commands.Test plan
run_tests.ymluntouched and green on this branch