Replies: 3 comments 2 replies
-
Do that part. |
Beta Was this translation helpful? Give feedback.
-
Thank you for your reply Until now, it has never asked for GitHub token. Could you please let me know why it asks for a token now? |
Beta Was this translation helpful? Give feedback.
-
Hi there - We haven't heard back in a bit, so I'm going to close this ticket for now, but will re-open it if you're still having issues. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
We have a Snipe-IT running in version v7.1.16. Until now, I could update Snipe-IT. Today I tried to update it (php upgrade.php), but it asked for Composer Token, which I don't what to enter. It has never asked for it before. We have never created a repository in GitHub.
Could you please help me how to solve it? Thanks.
Cloning failed using an ssh key for authentication, enter your GitHub credentials to access private repos When working with _public_ GitHub repositories only, head here to retrieve a token: https://github.com/settings/tokens/new?scopes=&description=Composer+on+vasset+2025-05-14+0927 This token will have read-only permission for public information only. When you need to access _private_ GitHub repositories as well, go to: https://github.com/settings/tokens/new?scopes=repo&description=Composer+on+vasset+2025-05-14+0927 Note that such tokens have broad read/write permissions on your behalf, even if not needed by Composer. Tokens will be stored in plain text in "/home/snipeitapp/.config/composer/auth.json" for future use by Composer. For additional information, check https://getcomposer.org/doc/articles/authentication-for-private-packages.md#github-oauth Token (hidden):
Beta Was this translation helpful? Give feedback.
All reactions