-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
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
Release 1.0.0 #66
Release 1.0.0 #66
Conversation
Thanks for this! I'm not super comfortable using my PyPI password for this--could we do something like what Flask-SeaSurf is doing instead? |
you don't need to use your real password for PYPI, you need to generate auth token:
https://pypi.org/help/#apitoken you can limit scope for each token so it has access only to the selected repo I think you're confused with I can rename it for your convenience if you'd like |
@maxcountryman hey! still waiting your action here
this will take like 5-7m max |
Thanks @mahenzon--do you mind updating this so it mirrors the configuration in Flask-SeaSurf? That'll help limit the mental overhead required to maintain these repos. |
you mean changing |
I think you could just copy the workflow from Flask-SeaSurf and update accordingly for this repo, if that's helpful. That way it's reusing the same Action, etc. |
…ypa/gh-action-pypi-publish@v1.4.1 (as flask-seasurf)
ok, upgraded the action now steps are:
|
hey @maxcountryman , it's the final push and this issue will be resolved. three steps to do, doable even from mobile 🙏 |
🤔 |
🧐 |
Max, at first I wanna say that I hope you're doing well Flask-Bcrypt at pypi was Released: Oct 6, 2015. This repo got some updates from users, but there were no releases for more than 5 years. The only thing stopping this repo from being updated now is you adding secret key for pypi releases and merging this branch. |
@mahenzon would you kindly stop pinging me about this? I'll get to it when I have the time and your many messages aren't encouraging me to prioritize this. |
Hey! So could you please grant me access to this repo and at pypi so I can finally release what's already been here for years in the master branch? |
Thank you I appreciate your concerns but there's nothing stopping you from using mainline (as others do). I'm going to close this because I already mentioned that your multiple messages were sufficient and it's not okay to continue to demand anyone's time, however little you perceive the cost. If you'd like to arrange to pay me to do this work for you then I'd be happy to share my daily rate with you. |
Closes #65
To match source code and release I suggest using automatic releases
pls add
PYPI_PASSWORD
to repo'ssecrets
and create a new release, package be automatically deployed to pypiI suggest updating version to 1.0.0