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.

Sign up for GitHub

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

Jump to bottom

CI step broken on master #171

Closed
dixler opened this issue Jan 3, 2023 · 1 comment
Closed

CI step broken on master #171

dixler opened this issue Jan 3, 2023 · 1 comment
Assignees
@dixler
Labels
kind/bug Some behavior is incorrect or out of spec resolution/fixed This issue was fixed
Milestone
0.83

Comments

@dixler
Copy link
Contributor

dixler commented Jan 3, 2023

What happened?

GHA run broke

25hINFO     Response from https://upload.pypi.org/legacy/:                         
         400 '0.7.1a1672299748+334686c5' is an invalid value for Version. Error:
         Can't use PEP 440 local versions. See                                  
         https://packaging.python.org/specifications/core-metadata for more     
         information.                                                           
INFO     <html>                                                                 
          <head>                                                                
           <title>400 '0.7.1a1672299748+334686c5' is an invalid value for       
         Version. Error: Can't use PEP 440 local versions. See                  
         https://packaging.python.org/specifications/core-metadata for more     
         information.</title>                                                   
          </head>                                                               
          <body>                                                                
           <h1>400 '0.7.1a1672299748+334686c5' is an invalid value for Version. 
         Error: Can't use PEP 440 local versions. See                           
         https://packaging.python.org/specifications/core-metadata for more     
         information.</h1>                                                      
           The server could not comply with the request since it is either      
         malformed or otherwise incorrect.<br/><br/>                            
         &#x27;0.7.1a1672299748+334686c5&#x27; is an invalid value for Version. 
         Error: Can&#x27;t use PEP 440 local versions. See                      
         https://packaging.python.org/specifications/core-metadata for more     
         information.                                                           
                                                                                
                                                                                
          </body>                                                               
         </html>                                                                
ERROR    HTTPError: 400 Bad Request from https://upload.pypi.org/legacy/        
         '0.7.1a1672299748+334686c5' is an invalid value for Version. Error:    
         Can't use PEP 440 local versions. See                                  
         https://packaging.python.org/specifications/core-metadata for more     
         information.

Steps to reproduce

n/a

Expected Behavior

run successfully

Actual Behavior

fail

Output of pulumi about

No response

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
@dixler dixler added kind/bug Some behavior is incorrect or out of spec needs-triage Needs attention from the triage team labels Jan 3, 2023
@dixler dixler self-assigned this Jan 3, 2023
@dixler dixler changed the title CI step broken on main CI step broken on master Jan 3, 2023
@t0yv0
Copy link
Member

t0yv0 commented Jan 3, 2023

Might be fixed by pulumi/pulumictl#60 that fixes a regression in pulumictl.

@dixler dixler removed the needs-triage Needs attention from the triage team label Jan 4, 2023
@dixler dixler mentioned this issue Jan 5, 2023
Merged
@dixler dixler added this to the 0.83 milestone Jan 5, 2023
@dixler dixler added the resolution/fixed This issue was fixed label Jan 5, 2023
@dixler dixler closed this as completed Jan 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dixler dixler

Labels
kind/bug Some behavior is incorrect or out of spec resolution/fixed This issue was fixed
Projects
None yet
Milestone
0.83
Development

No branches or pull requests
2 participants
@t0yv0 @dixler