Skip to content

upgrade to jq 1.8.0 #283

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

Merged
merged 4 commits into from
Jun 3, 2025
Merged

upgrade to jq 1.8.0 #283

merged 4 commits into from
Jun 3, 2025

Conversation

glennj
Copy link
Contributor

@glennj glennj commented Jun 2, 2025

Summary

To align with #jq-test-runner/47 that updates the test runner to jq 1.8.0, let's do the same here.

Exercise tests running successfully with the new jq version on my machine.

Checklist

  • If docs where changed, run ./bin/fetch-configlet && ./bin/configlet generate to ensure all documents are properly generated.
  • CI is green

@glennj glennj requested a review from IsaacG June 2, 2025 12:23
@glennj
Copy link
Contributor Author

glennj commented Jun 2, 2025

@IsaacG I had neglected to update docs.

This is the version used in the online jq test runner.

Most Linux package managers will install the previous release, version 1.6.
Many Linux package managers will install an older release, version 1.6.
It's worth installing the newer version: there were [substantial changes in the 1.7 release][release-notes-1.7].
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this line need updating, too?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I kept that because that's when the source code was transferred to the jqlang org, so big changes did happen then.

I suppose I don't need to keep it: people can go find the release notes if they are curious.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You could also drop the version in the prior line. Something like this?

Many Linux package managers will install an older release.
You may want to consider using a version newer than what your package manager installs by default.
In particular, there were [substantial changes in the 1.7 release][release-notes-1.7].

Copy link
Member

@IsaacG IsaacG left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it make sense to have a single "version" doc and have the other docs reference that, only hard coding versions in one place?

It would be nice if there was a way to use a template/variables in these docs 😁

@glennj
Copy link
Contributor Author

glennj commented Jun 2, 2025

I take another round, to see if I can reduce the number of occurrences.

@glennj
Copy link
Contributor Author

glennj commented Jun 2, 2025

This latest commit removes the version number from all but the Installation and Tests docs.

A later effort will be to revisit the concepts, to see if there's any relevant breaking changes.

@glennj glennj merged commit fa0ef11 into exercism:main Jun 3, 2025
2 checks passed
@glennj glennj deleted the jq-1.8 branch August 6, 2025 12:39
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