unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Josh Marshall <Josh.Marshall@jax.org>
To: help-guix <help-guix@gnu.org>
Subject: Re: Is this on the list of things to change?  Fw: [EXTERNAL][GitHub API] Deprecation notice for authentication via URL query parameters
Date: Wed, 19 Feb 2020 15:14:07 +0000	[thread overview]
Message-ID: <BL0PR06MB4673D4EEB249CA01DC95AD41E9100@BL0PR06MB4673.namprd06.prod.outlook.com> (raw)
In-Reply-To: <BL0PR06MB46731450B202004F0748F8AAE9100@BL0PR06MB4673.namprd06.prod.outlook.com>

After adding it, it still fails with the following:
```
Backtrace:
           1 (primitive-load "/gnu/store/44xzqrhqa8d6135vr0x7c5lg43l…")
In guix/ui.scm:
  1824:12  0 (run-guix-command _ . _)

guix/ui.scm:1824:12: In procedure run-guix-command:
Error downloading release information through the GitHub
API when using a GitHub token
```

________________________________________
From: Josh Marshall <Josh.Marshall@jax.org>
Sent: Wednesday, February 19, 2020 8:56 AM
To: help-guix
Subject: Fw: Is this on the list of things to change?  Fw: [EXTERNAL][GitHub API] Deprecation notice for authentication via URL query parameters

Hello,

Getting guix setup on a machine and ran into the following when running `refresh` after adding a github API key.

________________________________________
From: GitHub <noreply@github.com>
Sent: Wednesday, February 19, 2020 8:49 AM
To: Josh Marshall
Subject: [EXTERNAL][GitHub API] Deprecation notice for authentication via URL query parameters

Hi @josh-marshall-jax,

On February 19th, 2020 at 13:49 (UTC) your personal access token (for work desktop guix) using GNU Guile was used as part of a query parameter to access an endpoint through the GitHub API:

https://api.github.com/repositories/32202720/releases

Please use the Authorization HTTP header instead, as using the `access_token` query parameter is deprecated. If this token is being used by an app you don't have control over, be aware that it may stop working as a result of this deprecation.

Depending on your API usage, we'll be sending you this email reminder on a monthly basis 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 https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param for more information about suggested workarounds and removal dates.

Thanks,
The GitHub Team
---

The information in this email, including attachments, may be confidential and is intended solely for the addressee(s). If you believe you received this email by mistake, please notify the sender by return email as soon as possible.

  parent reply	other threads:[~2020-02-19 15:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5e4d3d00e2fc_34f93fa17eccd968121810@github-lowworker-2e54e43.va3-iad.github.net.mail>
     [not found] ` <BL0PR06MB4673327A8725D4D90B516528E9100@BL0PR06MB4673.namprd06.prod.outlook.com>
2020-02-19 13:56   ` Fw: Is this on the list of things to change? Fw: [EXTERNAL][GitHub API] Deprecation notice for authentication via URL query parameters Josh Marshall
2020-02-19 14:21     ` Tobias Geerinckx-Rice
2020-02-19 15:14     ` Josh Marshall [this message]
2020-02-19 15:18       ` Tobias Geerinckx-Rice

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BL0PR06MB4673D4EEB249CA01DC95AD41E9100@BL0PR06MB4673.namprd06.prod.outlook.com \
    --to=josh.marshall@jax.org \
    --cc=help-guix@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).