flex icon indicating copy to clipboard operation
flex copied to clipboard

composer recipes:update fails with curl error

Open lazka opened this issue 1 year ago • 3 comments

Using symfony/flex v1.19.5, when using the "recipes:update" command I get the following for every package:

$composer recipes:update
Which outdated recipe would you like to update? (default: 0)
  [0] symfony/apache-pack
  [1] symfony/flex
  [2] symfony/lock
  [3] symfony/messenger
  [4] symfony/phpunit-bridge
 > 1
  Updating recipe for symfony/flex...

                        
   Yes! Recipe updated! 
                        

  Run git status or git diff --cached to see the changes.
  When you're ready, commit these changes like normal.

  Calculating CHANGELOG...
In CurlDownloader.php line 623:
                                                                                                                       
  The "https://api.github.com/search/issues?q=fcda4f8f67e48ff06163debe049416c698e4f2ae" file could not be downloaded   
  (HTTP/2 422 ):                                                                                                       
  {"message":"Query must include 'is:issue' or 'is:pull-request'","documentation_url":"https://docs.github.com/rest/r  
  eference/search#search-issues-and-pull-requests"}

lazka avatar May 03 '23 13:05 lazka

Hi!

I'm guessing this was some weird, temporary issue. It shows the URL, and that loads just fine for me right now.

Cheers!

weaverryan avatar May 29 '23 01:05 weaverryan

I experienced the same issue when updating a flex recipe. I think it might have something to do with the new fine grained access tokens (github_pat_ prefixed). I had one in my ~/.composer/auth.json file and replaced it with a classic token (ghp_ prefixed). That seemed to solve the issue. Might be a false positive, or perhaps the new fine grained tokens require a specific permission in order for them to work when using with Flex?

leonboot avatar Jun 13 '23 13:06 leonboot

According to the documentation, it is required to either add is:issue or is:pull-request to the ?q= parameter when using the new fine grained access token. This seems to be a new restriction of the access token and not related to the permissions itself, as even a fine grained access token with all permissions requires the query parameter to be set.

micheh avatar Nov 19 '23 12:11 micheh