Skip to content
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

Received a... few "...using the access_token query parameter is deprecated." emails today #463

Closed
jpartain89 opened this issue Feb 4, 2020 · 10 comments · Fixed by #464
Closed

Comments

@jpartain89
Copy link

I had received a few emails from Github today, all saying the same thing, pointing to my syncing gist file...

Hi @jpartain89,

On February 4th, 2020 at 03:26 (UTC) your personal access token (Atom Syncing) using NodeJS HTTP Client was used as part of a query parameter to access an endpoint through the GitHub API:

api.github.com/gists/###hidden_because_i_said_so###

Please use the Authorization HTTP header instead, as using the access_token query parameter is deprecated.

Depending on your API usage, we'll be sending you this email reminder once every 3 days for each token and User-Agent used in API calls made on your behalf.
Just one URL that was accessed with a token and User-Agent combination will be listed in the email reminder, not all.

Visit developer.github.com/changes/2019-11-05-deprecated-passwords-and-authorizations-api/#authenticating-using-query-parameters for more information.

Thanks,
The GitHub Team

Any plan/word on updating this?

Thanks.

@enginpost
Copy link

Is there an update available that will resolve this? I just got this error message today and Atom doesn't say there is an update for Sync Settings available for download.

@jfletcher-nuxeo
Copy link

There's a pull request (#464) that supposedly resolves this but there's apparently no one maintaining the package to accept it.

@maurice-schleussinger
Copy link

@BinaryMuse @50Wliu @basarat
Could we get a statement or decision about the future of this package/repo?

@pauljherring
Copy link

There's a pull request (#464) that supposedly resolves this

And a few other things judging by the line count...

@UziTech
Copy link
Member

UziTech commented Feb 6, 2020

The release that fixes this should be available 🎉

@pauljherring
Copy link

The release that fixes this should be available

Doesn't appear to be; at the time of writing https://atom.io/releases shows the most recent release as v1.43.0 (2020-01-14)

@gilbertohasnofb
Copy link

@pauljherring Those are the releases of Atom itself, not of this package. You can see that version 2.0.0 has been released here. You can update it directly in Atom by going to settings and looking for available updates for your installed packages.

@UziTech I just tested it and the issue has been resolved on my side. Thank you so much for the fix and for stepping up to become a maintainer of this package, that's really appreciated.

@pauljherring
Copy link

Those are the releases of Atom itself, not of this package.

Doh! I'm sorry.

@al-yakubovich
Copy link

I am still receiving emails from GitHub with this notice.

@UziTech
Copy link
Member

UziTech commented Feb 14, 2020

@al-yakubovich have you installed the latest version?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants