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

Latest version reports it is an old version #4226

Open
DominicCronin opened this issue Jan 10, 2025 · 1 comment
Open

Latest version reports it is an old version #4226

DominicCronin opened this issue Jan 10, 2025 · 1 comment

Comments

@DominicCronin
Copy link

Version

4.0.6610

Description

Immediately after having installed version 4.0.6610 using the x64 MSI on my Windows 11 system, when I run "func" without arguments it runs "func help" and at the bottom of the output, you see:

"You are using an old Core Tools version. Please upgrade to the latest version."

I can confirm the version by running
func --version
which reports 4.0.6610

Note that this looks similar to #3776 which is about the similar symptoms after a chocolatey install. At least I assume it's not the same issue, because that one is Closed, and I'm experiencing the issue on the latest.

Steps to reproduce

Install version 4.0.6610 using the x64 MSI on a Windows 11 system

run "func" and page to the bottom of the output.

Observe the following text.

"You are using an old Core Tools version. Please upgrade to the latest version."

@DominicCronin
Copy link
Author

DominicCronin commented Jan 10, 2025

I just looked at the code and it's pulling data from https://functionscdn.azureedge.net/public/cli-feed-v4.json, looking up the v4 release from the tags and then finding the release and fishing the release number out of the download URL (which is different, or more specific I guess)

Image

Anyway it looks like the version you get by doing this with the json doesn't match the version that Constants.CliVersion gets from the assembly version.

One other thing to note is that even though I'm on windows, it's parsing the download link for linux. It just grabs the first one.

So given that this is quite a complex mechanism, it will presumably need to be fixed by someone who understands why it's done like that.

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

No branches or pull requests

1 participant