Skip to content

Fix readme to indicate jq is 1.7.1 #12465

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

Closed
wants to merge 1 commit into from
Closed

Conversation

jsoref
Copy link
Contributor

@jsoref jsoref commented Jun 24, 2025

Description

Update readme to match shipping version and other readmes

Other readmes show the triple (https://github.com/search?q=repo%3Aactions%2Frunner-images+jq+language%3AMarkdown&type=code&l=Markdown):



And this readme says elsewhere that it's actually 1.7.1:

| jq | 1.7.1-3build1 |

Related issue:

Check list

  • Related issue / work item is attached
  • Tests are written (if applicable)
  • Documentation is updated (if applicable)
  • Changes are tested and related VM images are successfully generated

@subir0071
Copy link
Contributor

In ubuntu-2404 we have correct version displayed in its readme.
Please follow this workflow to test the same.
https://github.com/subir0071/hello-world/actions/runs/15979019487/job/45068799307

Closing this PR.

@subir0071 subir0071 closed this Jun 30, 2025
@jsoref
Copy link
Contributor Author

jsoref commented Jun 30, 2025

@subir0071: That's because the debian packager messed up and the ubuntu package pulled in that mistake. You can clearly see from the package that it claims to be 1.7.1:

| jq | 1.7.1-3build1 |

You can see the 1.7.1 base package here:
https://launchpad.net/ubuntu/+source/jq/1.7.1-1
And the corresponding changes here:
https://launchpadlibrarian.net/703105813/jq_1.7-1_1.7.1-1.diff.gz

They aren't intentionally reverting to an older version. Unfortunately the debian package failed to bump the version field and the ubuntu packager also failed to bump the version field.

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

Successfully merging this pull request may close these issues.

2 participants