rht
As stated earlier, that solution requires 2FA to be disabled. The additional factor for the authentication is for PyPI to recognize that the push comes from a GH Actions enabled...
Raised https://github.com/pypi/warehouse/issues/12406.
It's the usual reason why 2FA is needed. Having the API token compromised without the 2FA enabled would allow an attacker to slip in some minor versions (they could be...
You could argue that: - Poetry is used by a lot more projects than Mesa - It has a more fatal consequence if compromised, affecting all the projects that deploy...
Moving everything sounds good to me. It will make it easier for me to implement #1406, where I can just download the tarball of the GH repo from a URL,...
There are 6 PRs which will have merge conflicts: - https://github.com/projectmesa/mesa/pull/815/files - https://github.com/projectmesa/mesa/pull/955/files - https://github.com/projectmesa/mesa/pull/1057 - https://github.com/projectmesa/mesa/pull/1223/files - https://github.com/projectmesa/mesa/pull/1290 - https://github.com/projectmesa/mesa/pull/1344/files I have checked all of them. Resolving the conflicts...
> @rht do you think that is feasible? Drafts: - https://github.com/projectmesa/mesa/pull/815/files ongoing - https://github.com/projectmesa/mesa/pull/1223/files this is more of a reminder that we need to think more to design directed network...
Note that #1228 is no longer feasible with all the examples being moved to a separate repo. It's still feasible, but either with code duplication, or we leave a few...