We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The secrets used in the automated release process seem to have been lost when the repo was migrated :(
see https://github.com/cytoscape/ipycytoscape/runs/4339062992?check_suite_focus=true
Uploading distributions to https://upload.pypi.org/legacy/ Uploading ipycytoscape-1.3.0-py2.py3-none-any.whl 0%| | 0.00/3.45M [00:00<?, ?B/s] 0%| | 8.00k/3.45M [00:00<01:46, 33.8kB/s] 4%|▍ | 144k/3.45M [00:00<00:07, 463kB/s] 13%|█▎ | 464k/3.45M [00:00<00:02, 1.29MB/s] 32%|███▏ | 1.10M/3.45M [00:00<00:00, 2.93MB/s] 100%|██████████| 3.45M/3.45M [00:00<00:00, 3.71MB/s] Error during upload. Retry with the --verbose option for more details. HTTPError: 403 Forbidden from https://upload.pypi.org/legacy/ Invalid or non-existent authentication information. See https://pypi.org/help/#invalid-auth for more information. Error: Process completed with exit code 1.
Could I be given enough permissions to add a PYPI api key to this repos secrets?
Not really sure who to ask about that at this point but surely one of @SylvainCorlay @marimeireles @kozo2 @maxkfranz
will have the power to do that, or to add their own pypi api key?
The text was updated successfully, but these errors were encountered:
1.3.0
1.3.1
@ianhi Thank you for reporting. One moment please. I am asking about this to the Cytoscape team.
Sorry, something went wrong.
Bump - looks as though it's time to make another release to fix both #294 and #293
No branches or pull requests
Problem
The secrets used in the automated release process seem to have been lost when the repo was migrated :(
see https://github.com/cytoscape/ipycytoscape/runs/4339062992?check_suite_focus=true
Proposed Solution
Could I be given enough permissions to add a PYPI api key to this repos secrets?
Not really sure who to ask about that at this point but surely one of
@SylvainCorlay @marimeireles @kozo2 @maxkfranz
will have the power to do that, or to add their own pypi api key?
The text was updated successfully, but these errors were encountered: