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.

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

au failing to push package updates with PowerShell Core 7.3 #24

Open
flcdrg opened this issue Mar 3, 2023 · 5 comments
Open

au failing to push package updates with PowerShell Core 7.3 #24

flcdrg opened this issue Mar 3, 2023 · 5 comments

Comments

@flcdrg
Copy link
Contributor

flcdrg commented Mar 3, 2023

There seems to be a breaking change between PS 7.2 and 7.3 that is causing AU to fail when trying to push new package versions.

I can see Appveyor seems to have upgraded their images from 7.2 to 7.3 a few days ago and since then all my updates are failing. eg.

[54/55] sqltoolbelt ERROR:
Chocolatey v1.3.0 File specified is either not found or not a .nupkg file. 'sqltoolbelt.2023.03.01.nupkg ' (50.30s)
[55/55] vt-cli ERROR:
Chocolatey v1.3.0 File specified is either not found or not a .nupkg file. 'vt-cli.0.12.0.nupkg ' (19.76s)

The extra trailing space does look suspicious

@flcdrg
Copy link
Contributor Author

flcdrg commented Mar 3, 2023

@flcdrg
Copy link
Contributor Author

flcdrg commented Mar 5, 2023

Spent a few hours trying to figure out what's going on, and I'm stumped. Not easy to debug as the codebase uses PowerShell Jobs, and as far as I can tell, you can't set breakpoints/step through Jobs. Also weird, I get different behaviour running in VS Code vs from PowerShell in Terminal. Very weird.

@tunisiano187
Copy link

tunisiano187 commented Jun 8, 2023

Same for me with Chocolatey 2.0

@flcdrg
Copy link
Contributor Author

flcdrg commented Jun 8, 2023

FWIW I have a branch on my fork that is working - https://github.com/flcdrg/chocolatey-au/tree/fix-warnings

@flcdrg
Copy link
Contributor Author

flcdrg commented Feb 15, 2024

And now my branch stopped working (mostly because I think GitHub Actions upgraded the version of PowerShell they use from 7.2 to 7.3)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants