You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The release process for azanium currently depends on python package github3.py (version 1.0.0a4) and the github3.authorize function to authenticate to Github using password authentication. This form of authentication is officially deprecated by Github (see here and here) and will be removed from the Github APIs on November 13, 2020. Hence there is a need to update this step in the release flow, as it would fail from November 13 onwards.
The text was updated successfully, but these errors were encountered:
I've implemented a potential fix in 02bf1db, but am unsure whether this will cover the upcoming Github API deprecation (or what parts of Github3.py will be affected by it). As I don't know of a way to test this upfront (I've missed the brown-out periods), I will wait with creating a new db-migration (azanium) release until after November 13, at which point the Github OAuth Authorization API is being deprecated and the release process will fail if my code update would not cover the required changes.
The release process for azanium currently depends on python package
github3.py
(version1.0.0a4
) and thegithub3.authorize
function to authenticate to Github using password authentication. This form of authentication is officially deprecated by Github (see here and here) and will be removed from the Github APIs on November 13, 2020. Hence there is a need to update this step in the release flow, as it would fail from November 13 onwards.The text was updated successfully, but these errors were encountered: