Fwd: [GitHub] Deprecation Notice
what will be the implication?
Begin forwarded message:
From: GitHub <noreply@github.com> Subject: [GitHub] Deprecation Notice Date: 21 January 2020 at 21:03:28 CET To: StéphaneDucasse <stephane.ducasse@inria.fr>
Hi @Ducasse,
You recently used a password to access an endpoint through the GitHub API using Zinc HTTP Components 1.0 (Pharo/9.0). We will deprecate basic authentication using password to this endpoint soon:
https://api.github.com/repositories/169849137 <https://api.github.com/repositories/169849137>
We recommend using a personal access token (PAT) with the appropriate scope to access this endpoint instead. Visit https://github.com/settings/tokens <https://github.com/settings/tokens> for more information.
Thanks, The GitHub Team
You can create a personal access token and use it instead of the password. For example when setting the iceberg credentials. So, I think there's no problem per se. On Tue, Jan 21, 2020, 17:06 ducasse <stepharo@netcourrier.com> wrote:
what will be the implication?
Begin forwarded message:
*From: *GitHub <noreply@github.com> *Subject: **[GitHub] Deprecation Notice* *Date: *21 January 2020 at 21:03:28 CET *To: *StéphaneDucasse <stephane.ducasse@inria.fr>
Hi @Ducasse,
You recently used a password to access an endpoint through the GitHub API using Zinc HTTP Components 1.0 (Pharo/9.0). We will deprecate basic authentication using password to this endpoint soon:
https://api.github.com/repositories/169849137
We recommend using a personal access token (PAT) with the appropriate scope to access this endpoint instead. Visit https://github.com/settings/tokens for more information.
Thanks, The GitHub Team
We probably have to change something. Do you know which operation (GitHub API access from Pharo code) is responsible for this ?
On 21 Jan 2020, at 21:05, ducasse <stepharo@netcourrier.com> wrote:
what will be the implication?
Begin forwarded message:
From: GitHub <noreply@github.com> Subject: [GitHub] Deprecation Notice Date: 21 January 2020 at 21:03:28 CET To: StéphaneDucasse <stephane.ducasse@inria.fr>
Hi @Ducasse,
You recently used a password to access an endpoint through the GitHub API using Zinc HTTP Components 1.0 (Pharo/9.0). We will deprecate basic authentication using password to this endpoint soon:
https://api.github.com/repositories/169849137
We recommend using a personal access token (PAT) with the appropriate scope to access this endpoint instead. Visit https://github.com/settings/tokens for more information.
Thanks, The GitHub Team
Hi, I believe that when cloning a repository using the Github tab from iceberg, iceberg makes a request to ask github for that projectâs meta-data. This query identifies if the cloned repository is a fork of another repository or not, and in case it is a fork, correctly pre-configure the repository remotes to simplify further operations (such as fetching from upstream, or creating pull requests in-image). If user credentials are not available, such request is anonymous. However, if user credentials **are** available, they are used => this is required for private projects to work. One possible solution would be to add a new kind of credentials Token-based, to existing ones (passwords also used for https, ssh key pairs).
El 22 ene 2020, a las 7:34, Sven Van Caekenberghe <sven@stfx.eu> escribió:
We probably have to change something.
Do you know which operation (GitHub API access from Pharo code) is responsible for this ?
On 21 Jan 2020, at 21:05, ducasse <stepharo@netcourrier.com> wrote:
what will be the implication?
Begin forwarded message:
From: GitHub <noreply@github.com> Subject: [GitHub] Deprecation Notice Date: 21 January 2020 at 21:03:28 CET To: StéphaneDucasse <stephane.ducasse@inria.fr>
Hi @Ducasse,
You recently used a password to access an endpoint through the GitHub API using Zinc HTTP Components 1.0 (Pharo/9.0). We will deprecate basic authentication using password to this endpoint soon:
https://api.github.com/repositories/169849137
We recommend using a personal access token (PAT) with the appropriate scope to access this endpoint instead. Visit https://github.com/settings/tokens for more information.
Thanks, The GitHub Team
I was just committing to my pharo fork ââ¦.using Zinc HTTP Components 1.0 (Pharo/9.0) ...â so I do not get fully get it. If Iâm the only one to receive this mail then this is ok Guille apparently I used password else it would have failed? Can it be that my password is not well set? I have hte impression that they mean something else. "We will deprecate basic authentication using passwordâ S
On 22 Jan 2020, at 07:47, Guillermo Polito <guillermopolito@gmail.com> wrote:
Hi,
I believe that when cloning a repository using the Github tab from iceberg, iceberg makes a request to ask github for that projectâs meta-data. This query identifies if the cloned repository is a fork of another repository or not, and in case it is a fork, correctly pre-configure the repository remotes to simplify further operations (such as fetching from upstream, or creating pull requests in-image).
If user credentials are not available, such request is anonymous. However, if user credentials **are** available, they are used => this is required for private projects to work.
One possible solution would be to add a new kind of credentials Token-based, to existing ones (passwords also used for https, ssh key pairs).
El 22 ene 2020, a las 7:34, Sven Van Caekenberghe <sven@stfx.eu> escribió:
We probably have to change something.
Do you know which operation (GitHub API access from Pharo code) is responsible for this ?
On 21 Jan 2020, at 21:05, ducasse <stepharo@netcourrier.com> wrote:
what will be the implication?
Begin forwarded message:
From: GitHub <noreply@github.com> Subject: [GitHub] Deprecation Notice Date: 21 January 2020 at 21:03:28 CET To: StéphaneDucasse <stephane.ducasse@inria.fr>
Hi @Ducasse,
You recently used a password to access an endpoint through the GitHub API using Zinc HTTP Components 1.0 (Pharo/9.0). We will deprecate basic authentication using password to this endpoint soon:
https://api.github.com/repositories/169849137
We recommend using a personal access token (PAT) with the appropriate scope to access this endpoint instead. Visit https://github.com/settings/tokens for more information.
Thanks, The GitHub Team
Did you re-clone your repository? I donât think so⦠Did you create a PR using Pharoâs github integration? Those are the only points we use Githubâs API :/
El 22 ene 2020, a las 9:13, ducasse <stepharo@netcourrier.com> escribió:
I was just committing to my pharo fork ââ¦.using Zinc HTTP Components 1.0 (Pharo/9.0) ...â so I do not get fully get it. If Iâm the only one to receive this mail then this is ok
Guille apparently I used password else it would have failed? Can it be that my password is not well set?
I have hte impression that they mean something else.
"We will deprecate basic authentication using passwordâ
S
On 22 Jan 2020, at 07:47, Guillermo Polito <guillermopolito@gmail.com> wrote:
Hi,
I believe that when cloning a repository using the Github tab from iceberg, iceberg makes a request to ask github for that projectâs meta-data. This query identifies if the cloned repository is a fork of another repository or not, and in case it is a fork, correctly pre-configure the repository remotes to simplify further operations (such as fetching from upstream, or creating pull requests in-image).
If user credentials are not available, such request is anonymous. However, if user credentials **are** available, they are used => this is required for private projects to work.
One possible solution would be to add a new kind of credentials Token-based, to existing ones (passwords also used for https, ssh key pairs).
El 22 ene 2020, a las 7:34, Sven Van Caekenberghe <sven@stfx.eu> escribió:
We probably have to change something.
Do you know which operation (GitHub API access from Pharo code) is responsible for this ?
On 21 Jan 2020, at 21:05, ducasse <stepharo@netcourrier.com> wrote:
what will be the implication?
Begin forwarded message:
From: GitHub <noreply@github.com> Subject: [GitHub] Deprecation Notice Date: 21 January 2020 at 21:03:28 CET To: StéphaneDucasse <stephane.ducasse@inria.fr>
Hi @Ducasse,
You recently used a password to access an endpoint through the GitHub API using Zinc HTTP Components 1.0 (Pharo/9.0). We will deprecate basic authentication using password to this endpoint soon:
https://api.github.com/repositories/169849137
We recommend using a personal access token (PAT) with the appropriate scope to access this endpoint instead. Visit https://github.com/settings/tokens for more information.
Thanks, The GitHub Team
On 22 Jan 2020, at 09:48, Guillermo Polito <guillermopolito@gmail.com> wrote:
Did you re-clone your repository? I donât think soâ¦
no
Did you create a PR using Pharoâs github integration?
Yes I did this.
Those are the only points we use Githubâs API :/ Ok we found it :)
El 22 ene 2020, a las 9:13, ducasse <stepharo@netcourrier.com> escribió:
I was just committing to my pharo fork ââ¦.using Zinc HTTP Components 1.0 (Pharo/9.0) ...â so I do not get fully get it. If Iâm the only one to receive this mail then this is ok
Guille apparently I used password else it would have failed? Can it be that my password is not well set?
I have hte impression that they mean something else.
"We will deprecate basic authentication using passwordâ
S
On 22 Jan 2020, at 07:47, Guillermo Polito <guillermopolito@gmail.com> wrote:
Hi,
I believe that when cloning a repository using the Github tab from iceberg, iceberg makes a request to ask github for that projectâs meta-data. This query identifies if the cloned repository is a fork of another repository or not, and in case it is a fork, correctly pre-configure the repository remotes to simplify further operations (such as fetching from upstream, or creating pull requests in-image).
If user credentials are not available, such request is anonymous. However, if user credentials **are** available, they are used => this is required for private projects to work.
One possible solution would be to add a new kind of credentials Token-based, to existing ones (passwords also used for https, ssh key pairs).
El 22 ene 2020, a las 7:34, Sven Van Caekenberghe <sven@stfx.eu> escribió:
We probably have to change something.
Do you know which operation (GitHub API access from Pharo code) is responsible for this ?
On 21 Jan 2020, at 21:05, ducasse <stepharo@netcourrier.com> wrote:
what will be the implication?
Begin forwarded message:
From: GitHub <noreply@github.com> Subject: [GitHub] Deprecation Notice Date: 21 January 2020 at 21:03:28 CET To: StéphaneDucasse <stephane.ducasse@inria.fr>
Hi @Ducasse,
You recently used a password to access an endpoint through the GitHub API using Zinc HTTP Components 1.0 (Pharo/9.0). We will deprecate basic authentication using password to this endpoint soon:
https://api.github.com/repositories/169849137
We recommend using a personal access token (PAT) with the appropriate scope to access this endpoint instead. Visit https://github.com/settings/tokens for more information.
Thanks, The GitHub Team
Yes, it is the PR creation API. I have started to add support to tokens in a nice way. I can push it to the next version. On Wed, Jan 22, 2020 at 9:55 AM ducasse <stepharo@netcourrier.com> wrote:
On 22 Jan 2020, at 09:48, Guillermo Polito <guillermopolito@gmail.com> wrote:
Did you re-clone your repository? I donât think soâ¦
no
Did you create a PR using Pharoâs github integration?
Yes I did this.
Those are the only points we use Githubâs API :/ Ok we found it :)
El 22 ene 2020, a las 9:13, ducasse <stepharo@netcourrier.com> escribió:
I was just committing to my pharo fork ââ¦.using Zinc HTTP Components 1.0 (Pharo/9.0) ...â so I do not get fully get it. If Iâm the only one to receive this mail then this is ok
Guille apparently I used password else it would have failed? Can it be that my password is not well set?
I have hte impression that they mean something else.
"We will deprecate basic authentication using passwordâ
S
On 22 Jan 2020, at 07:47, Guillermo Polito <guillermopolito@gmail.com> wrote:
Hi,
I believe that when cloning a repository using the Github tab from iceberg, iceberg makes a request to ask github for that projectâs meta-data. This query identifies if the cloned repository is a fork of another repository or not, and in case it is a fork, correctly pre-configure the repository remotes to simplify further operations (such as fetching from upstream, or creating pull requests in-image).
If user credentials are not available, such request is anonymous. However, if user credentials **are** available, they are used => this is required for private projects to work.
One possible solution would be to add a new kind of credentials Token-based, to existing ones (passwords also used for https, ssh key pairs).
El 22 ene 2020, a las 7:34, Sven Van Caekenberghe <sven@stfx.eu> escribió:
We probably have to change something.
Do you know which operation (GitHub API access from Pharo code) is responsible for this ?
On 21 Jan 2020, at 21:05, ducasse <stepharo@netcourrier.com> wrote:
what will be the implication?
Begin forwarded message:
From: GitHub <noreply@github.com> Subject: [GitHub] Deprecation Notice Date: 21 January 2020 at 21:03:28 CET To: StéphaneDucasse <stephane.ducasse@inria.fr>
Hi @Ducasse,
You recently used a password to access an endpoint through the GitHub API using Zinc HTTP Components 1.0 (Pharo/9.0). We will deprecate basic authentication using password to this endpoint soon:
https://api.github.com/repositories/169849137
We recommend using a personal access token (PAT) with the appropriate scope to access this endpoint instead. Visit https://github.com/settings/tokens for more information.
Thanks, The GitHub Team
-- Pablo Tesone. tesonep@gmail.com
Thanks pablo. This is the typical example that even if we do not want to do things the world is pushing us. So good code always pays because change is the only constant. S
On 22 Jan 2020, at 09:59, tesonep@gmail.com wrote:
Yes, it is the PR creation API. I have started to add support to tokens in a nice way. I can push it to the next version.
On Wed, Jan 22, 2020 at 9:55 AM ducasse <stepharo@netcourrier.com> wrote:
On 22 Jan 2020, at 09:48, Guillermo Polito <guillermopolito@gmail.com> wrote:
Did you re-clone your repository? I donât think soâ¦
no
Did you create a PR using Pharoâs github integration?
Yes I did this.
Those are the only points we use Githubâs API :/ Ok we found it :)
El 22 ene 2020, a las 9:13, ducasse <stepharo@netcourrier.com> escribió:
I was just committing to my pharo fork ââ¦.using Zinc HTTP Components 1.0 (Pharo/9.0) ...â so I do not get fully get it. If Iâm the only one to receive this mail then this is ok
Guille apparently I used password else it would have failed? Can it be that my password is not well set?
I have hte impression that they mean something else.
"We will deprecate basic authentication using passwordâ
S
On 22 Jan 2020, at 07:47, Guillermo Polito <guillermopolito@gmail.com> wrote:
Hi,
I believe that when cloning a repository using the Github tab from iceberg, iceberg makes a request to ask github for that projectâs meta-data. This query identifies if the cloned repository is a fork of another repository or not, and in case it is a fork, correctly pre-configure the repository remotes to simplify further operations (such as fetching from upstream, or creating pull requests in-image).
If user credentials are not available, such request is anonymous. However, if user credentials **are** available, they are used => this is required for private projects to work.
One possible solution would be to add a new kind of credentials Token-based, to existing ones (passwords also used for https, ssh key pairs).
El 22 ene 2020, a las 7:34, Sven Van Caekenberghe <sven@stfx.eu> escribió:
We probably have to change something.
Do you know which operation (GitHub API access from Pharo code) is responsible for this ?
On 21 Jan 2020, at 21:05, ducasse <stepharo@netcourrier.com> wrote:
what will be the implication?
Begin forwarded message:
From: GitHub <noreply@github.com> Subject: [GitHub] Deprecation Notice Date: 21 January 2020 at 21:03:28 CET To: StéphaneDucasse <stephane.ducasse@inria.fr>
Hi @Ducasse,
You recently used a password to access an endpoint through the GitHub API using Zinc HTTP Components 1.0 (Pharo/9.0). We will deprecate basic authentication using password to this endpoint soon:
https://api.github.com/repositories/169849137
We recommend using a personal access token (PAT) with the appropriate scope to access this endpoint instead. Visit https://github.com/settings/tokens for more information.
Thanks, The GitHub Team
-- Pablo Tesone. tesonep@gmail.com
Hi Stef & Guille, I received the same deprecation notice as Stef on 13 December. I've also just seen an `IceGitHubError: Not Found` error: IceGitHubAPI>>responseWithValidationDo: IceGitHubAPI>>contentsWithValidationDo: IceGitHubAPI>>jsonContentsWithValidationDo: IceGitHubAPI>>get: IceGitHubAPI>>getRepository:project: [ ^ IceGitHubAPI new beAnonymous; getRepository: self userName project: self projectName ] in IceTipGitHubRepositoryPanel>>getGitHubRepository in Block: [ ^ IceGitHubAPI new... BlockClosure>>on:do: IceTipGitHubRepositoryPanel>>getGitHubRepository [ | githubRepository | githubRepository := self getGitHubRepository. ... Not sure if it is related or not. Cheers, Alistair On Wed, 22 Jan 2020 at 09:49, Guillermo Polito <guillermopolito@gmail.com> wrote:
Did you re-clone your repository? I donât think so⦠Did you create a PR using Pharoâs github integration?
Those are the only points we use Githubâs API :/
El 22 ene 2020, a las 9:13, ducasse <stepharo@netcourrier.com> escribió:
I was just committing to my pharo fork ââ¦.using Zinc HTTP Components 1.0 (Pharo/9.0) ...â so I do not get fully get it. If Iâm the only one to receive this mail then this is ok
Guille apparently I used password else it would have failed? Can it be that my password is not well set?
I have hte impression that they mean something else.
"We will deprecate basic authentication using passwordâ
S
On 22 Jan 2020, at 07:47, Guillermo Polito <guillermopolito@gmail.com> wrote:
Hi,
I believe that when cloning a repository using the Github tab from iceberg, iceberg makes a request to ask github for that projectâs meta-data. This query identifies if the cloned repository is a fork of another repository or not, and in case it is a fork, correctly pre-configure the repository remotes to simplify further operations (such as fetching from upstream, or creating pull requests in-image).
If user credentials are not available, such request is anonymous. However, if user credentials **are** available, they are used => this is required for private projects to work.
One possible solution would be to add a new kind of credentials Token-based, to existing ones (passwords also used for https, ssh key pairs).
El 22 ene 2020, a las 7:34, Sven Van Caekenberghe <sven@stfx.eu> escribió:
We probably have to change something.
Do you know which operation (GitHub API access from Pharo code) is responsible for this ?
On 21 Jan 2020, at 21:05, ducasse <stepharo@netcourrier.com> wrote:
what will be the implication?
Begin forwarded message:
From: GitHub <noreply@github.com> Subject: [GitHub] Deprecation Notice Date: 21 January 2020 at 21:03:28 CET To: StéphaneDucasse <stephane.ducasse@inria.fr>
Hi @Ducasse,
You recently used a password to access an endpoint through the GitHub API using Zinc HTTP Components 1.0 (Pharo/9.0). We will deprecate basic authentication using password to this endpoint soon:
https://api.github.com/repositories/169849137
We recommend using a personal access token (PAT) with the appropriate scope to access this endpoint instead. Visit https://github.com/settings/tokens for more information.
Thanks, The GitHub Team
participants (6)
-
Alistair Grant -
ducasse -
Gabriel Cotelli -
Guillermo Polito -
Sven Van Caekenberghe -
tesonep＠gmail.com