However, the above is failing; I’m not even getting console logs from the implementation. I still have email@example.com installed as a package, so am curious if anyone has had luck upgrading GitHub authentication ever since GitHub announced the deprecation of auth through query params.
You could copy this package to your local packages folder so it would take precedence if you really can’t update Meteor.
Thanks, that’s helpful to know!
BTW, what is preventing you from running latest Meteor? Thanks.
Only the assumption that the migration would break a lot of code in the project that I don’t have time to maintain but the truth is I haven’t tried – so will look into it!
Are you running which version of Meteor?
I am currently running Meteor 18.104.22.168 (I know, somewhat old) and I thought meteor update --release 2.5 would upgrade it, but I am seeing
Unable to update package catalog (are you offline?)
If you are using Meteor behind a proxy, set HTTP_PROXY and HTTPS_PROXY environment variables or see this page
for more details: https://github.com/meteor/meteor/wiki/Using-Meteor-behind-a-proxy
Meteor 2.5: unknown release.