We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug jq --version reports "jq 1.7 dirty" when I download using the AMD64 link https://github.com/jqlang/jq/releases/download/jq-1.7/jq-windows-amd64.exe. I have switched to using the jq 1.6 --version, which reports "jq 1.6". I have not tested the other direct download versions on jq 1.7.
To Reproduce From Windows 11 - Download jq 1.7 from this link "https://github.com/jqlang/jq/releases/download/jq-1.7/jq-windows-amd64.exe". Then run jq --version.
Expected behavior I expect that the jq --version would report "jq 1.7."
Environment (please complete the following information):
Additional context Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Related to #2886
Sorry, something went wrong.
duplicate even
Successfully merging a pull request may close this issue.
Describe the bug
jq --version reports "jq 1.7 dirty" when I download using the AMD64 link https://github.com/jqlang/jq/releases/download/jq-1.7/jq-windows-amd64.exe. I have switched to using the jq 1.6 --version, which reports "jq 1.6". I have not tested the other direct download versions on jq 1.7.
To Reproduce
From Windows 11 - Download jq 1.7 from this link "https://github.com/jqlang/jq/releases/download/jq-1.7/jq-windows-amd64.exe". Then run jq --version.
Expected behavior
I expect that the jq --version would report "jq 1.7."
Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: